Manual · technical

How BITORY TRADE works, in detail

This page is for readers who want the moving parts: which contracts are involved, what each one can and cannot do, and how the desk turns raw chain state into the figures it shows. For the short version, read the manual on the home page.

1. The pieces on Robinhood Chain

2. Launch, curve and graduation

The token is created by the Pons factory with COIN as its pair asset. Its bonding curve quotes buys on a constant-product formula against virtual reserves; the trade fee comes off the COIN paid in. When the curve has sold its sellable allocation, its real COIN reserve equals the graduation target Pons stores for COIN pairs, and the curve closes. Pons then opens a Uniswap v4 pool keyed by the two tokens (sorted by address), the launch's fee and tick spacing, and the meme hook, and mints one full-range position with the curve's reserves.

3. BitoryStockKeep

A one-way keep for the creator fees of the $BITORY launch. It is named as the launch's creator fee recipient. Constructor: (stock, factory); the escrow is read from the factory once. No owner, no admin, no setter, no upgrade, no payable entry, and no function that transfers anything out.

Limits it cannot change: the stock issuer can pause, block or burn the keep's balance, and the Pons owner can reassign a launch's fee recipient after a timelock.

4. BitoryPoolMeter

A read-only contract. Constructor: (factory); the pool manager and hook are read from the factory once. read(launchToken) returns the launch phase, the curve's tradeable COIN reserve and waiting fees, and after graduation the pool id, sqrt price, tick, active liquidity and the COIN and token amounts behind it. Pool amounts treat the active liquidity as full range, which is how Pons seeds the pool; narrower positions added later would make the figure an estimate. The desk computes the same numbers in its own code and marks when the deployed meter agrees.

5. Where the desk's figures come from

Browser reads go through a read-only relay on this site that only serves the contracts above, prices every request and caps log ranges, then fall back to the public RPC. The relay never forwards signed transactions; trades are sent by your wallet.

6. Verifying a deployment

The source repository includes a verify-deployment script. Given an address and its creation transaction, it checks that the runtime bytecode matches the build byte for byte, decodes every immutable (stock token, factory, escrow, pool manager, hook) against the expected addresses, and confirms the creation input carries exactly the expected constructor arguments. Source verification on the explorer at robinhoodchain.blockscout.com follows the same build settings.

7. Risks in one list