How ORDEO launches and in what order the contracts go out

Status

The token on Pons

ORDEO is an ordinary ERC-20 paired with ETH; the Pons V2 launch factory creates it. It can be held, sent and traded in public by anyone. The launch parameters include the creator fee recipient, an optional creator tax and the buyback setting; the fee rates that apply are the ones Pons fixes at launch. Ordeo adds no code to the token itself.

The splitter as creator fee recipient

At launch the creator fee recipient is set to OrdeoYieldSplit. For each fee-paying trade, Pons books the creator share to it inside the Pons fee escrow. Anyone can then call:

• sweepPons(token) to ask Pons to move pending curve and pool fees into the escrow. It only works for a launch whose creator fee recipient is the splitter, and skips without reverting any sweep Pons reserves for its own operator.
• collect() to claim the splitter’s escrow balance, and distribute() to collect, split and pay in one call.

The splitter has no function that hands the creator fee role to anyone else.

The Pons owner path and its 3-day timelock

Using setCreatorFeeRecipient, the owner of Pons may point a token’s creator fee recipient elsewhere, though only once a public 3-day timelock has run (CREATOR_FEE_RECIPIENT_TIMELOCK). While a change is pending it is visible on chain as pendingCreatorFeeRecipient(token), and it can be executed within a window after the delay. A redirect would stop new yield. It can never touch notes or the vault, which the pool holds with no owner at all.

Deploy order

1. 01

   Libraries

   OrdeoSponge2, OrdeoSponge3, OrdeoChallengeLog, OrdeoConstraintSum.

2. 02

   Verifier

   OrdeoAttestor, linked to the two verifier libraries.

3. 03

   Key registry

   OrdeoKeyLedger. No constructor arguments.

4. 04

   Splitter

   OrdeoYieldSplit(team, holders, ponsFactory). It must exist before the token, because it is the creator fee recipient named at launch.

5. 05

   Launch the token

   Launch ORDEO on Pons with the splitter as creator fee recipient. This gives the contract address.

6. 06

   Pool

   OrdeoShroud(verifier, token, feeSink = splitter, fees…), linked to the Poseidon libraries. Its constructor requires the token to exist.

7. 07

   Router

   OrdeoTradeDesk(ponsFactory, poolManager, pool). It reads the token from the pool.

What buyers see

• On Pons: an ordinary launch page. Buying there puts public ORDEO into your wallet; shielding it can come later. The launch record shows the splitter as creator fee recipient.
• In the app, once the pool and router exist: a buy that lands directly in a note. Until then the app stays in practice mode with practice balances and no real funds.
• On this site: the contract address on every token link, and each deployed address on Deployments, where npm run verify-deployment can check it against this build.