Protocol

Contracts and powers

The contracts behind POO.MEME, what its powers reach, and what every token keeps.

Addresses

Every address here is verified on its chain's explorer, so the source behind it can be read there — except the two PooBlueprint holders (the one above, and the Fixed Presale blueprint below). A holder's runtime IS another contract's code rather than compiled output, so no bytecode match can verify it; what a reader checks instead is the factory, which pins the blueprint's codehash and answers it from blueprint().

Both registries are proxies, so each has an implementation behind it and an admin that can replace it. What those powers reach is below; the addresses are here so a reader can check them.

POO.MEME's own modules

Published to the same registry as anyone else's, and held to the same checks. Each has its own page under Modules.

What POO.MEME can do

Over things that already exist, POO.MEME has one power:

Handles

Drop a handle; restore a dropped one to the wallet that held it, replacing any handle that wallet took since; or reopen a dropped handle nobody held. Modules published under a dropped handle keep working.

No power reaches an existing token’s tax table or modules, and none writes a profile or a label.

Every other setting reaches only what is created later:

The token factory and the module registry can be upgraded. An upgrade reaches later creations and publications, never a token or module that already exists.

What every token keeps

• Its tax table and POO.MEME’s share, as created.
• Its supply. Nobody can mint more.
• Its modules, running the exact code checked at creation.
• Its launch money, inside the launch module. No POO.MEME contract can set a deadline on a claim or refund.
• Its scheduled opening.

How modules are held in check

Every module is treated as untrusted, POO.MEME’s own included.

Being listed as a module gives no power over anyone’s balance. A module moves its own tokens, or tokens a wallet approved to it directly, exactly as any other address would — the list changes nothing about that.

Checks cannot prove a module behaves as it says: how a launch module holds contributions, whether it locks its liquidity, and when it opens trading are its own code. Nobody reviews that code — not POO.MEME, not anyone. What publishing fixes is identity, not conduct: a module’s code, its hooks and its gas caps are set when it is published and can never change, so the module a creator chose is the module the token runs, and a newer version is a separate entry a creator picks for a new token. Inside those bounds a module does whatever its code does, and what holds it there is the table above — limits the token applies to every module on every call, POO.MEME’s own included, and that nobody can waive. A module’s description is its developer’s own account of what it does, pinned with the entry; read it as that, and read it before you pick a module or buy a token that uses one.

Hooks

A run is armed by one trade and delivered inside the next of its kind: a taxed sell arms the sell side, a taxed buy arms the buy side, and an exempt trade or a wallet transfer arms neither. A module can also ask for a sell-side run without a trade; nothing can reach the buy side except a buy. A run is told the trader and amount that triggered it. The guard watches this token’s own pool. If an Operate run leaves that pool worse for that seller — less quote, a lower price with more quote, or tokens left unsynced — the run is undone and the sell goes on. A run that only adds tokens to the pool passes, so leave room for it in your slippage.

A route around the tax

Modules trade with their token tax-free. If a module can pass on tokens bought into it, a buyer could use it to skip the tax. The standard requires its description to say whether it can — a statement its developer writes and nothing behind it proves, so read it.