The market is a universe.

The mechanic in one breath

1. $ORBIT is launched on Pons V2 with the Sun as its creator-fee recipient. Every trade pays the Sun in ETH.
2. Anyone lights a planet for an asset: 0.01 ETH to the Sun, the token's address and its Pyth feed. The planet takes the next orbit out.
3. Holders park $ORBIT around a planet — as a satellite (×1 gravity, leave after a day) or as one of its twelve orbits (×2 gravity, locked one revolution).
4. The Sun allots its ETH to the planets in proportion to their mass (gravity-weighted $ORBIT). A planet with a third of the mass gets a third of the flow.
5. The solar wind turns each planet's ETH into its asset: anyone may deliver NVDA (say) and take the pending ETH at the Pyth price plus a discount that ramps from 0 to 5% over six hours, resetting after each fill.
6. The delivered asset is owed to the planet's bodies pro rata to gravity. Harvest whenever you like.

Because the flow follows mass and the payout follows mass, every planet yields the same per unit of gravity (in ETH terms, before the wind's discount). Piling into a planet does not raise its yield; it raises its share of the flow and dilutes it by the same amount. The only thing you choose is what you are paid in. That is the point.

Lighting a planet

deployPlanet(asset, priceId), from any wallet, with 0.01 ETH. The fee joins the Sun's corona and is allotted to the planets already shining. The contract checks what a contract can check: the asset is a contract with 18 decimals (the wind's arithmetic assumes it), no planet pays in it yet, it is not $ORBIT, the feed id is not zero. It reads the token's symbol() and name() itself — nobody types a name. The k-th planet lit takes the k-th orbit and locks its orbits for (k + 1) × 7 days, at most 91: the farther out, the slower. The sky holds at most 48 planets, because every interaction walks them all. A planet is permanent.

What the contract cannot check is whether the asset is what its name says, and whether the feed prices it. A copy of a Robinhood token with the same name is a valid ERC-20; the Sun would light it. So the site keeps a catalog of assets it has verified on chain (below) and marks planets outside it unverified, with the raw address to inspect. A mismatched feed hurts only that planet: the wind would pay its fillers the wrong price from that planet's own ETH — the ETH its bodies were owed. Orbit a planet you understand.

The catalog

Robinhood's own stock tokens found on Robinhood Chain and read on 2026-09-18 (name() ends in “• Robinhood Token”, 18 decimals), with the Pyth feed the site proposes for each: the 24/7 Equity.Index feed where one exists, else the market-hours Equity.US feed (the wind then only blows while the stock trades). The brief's six come first; they appear in the sky as unlit candidates until someone lights them. HOOD has no token: Robinhood has not tokenized its own stock on its own chain (the two “HOOD” contracts there are memecoins). It stays dark until an issuance exists — then anyone lights it like any other.

★ named by the brief. Any other 18-decimal token with a Pyth feed can be lit from the deploy page; it just will not carry the verified mark.

Bodies

Satellite

Any amount ≥ 1,000 ORBIT. Gravity ×1. You can leave a day after your last deposit (each deposit restarts the day). What stays must be ≥ 1,000 or nothing.

Orbit

Total ≥ 500,000 ORBIT (0.05% of the launch supply). Gravity ×2. You take the lowest free of the planet's twelve rings; a full planet accepts no thirteenth orbit, only satellites. Locked for one orbital period from your deposit — every further deposit renews the lock for the whole position. A partial leave must keep ≥ 500,000; leaving entirely releases the ring to the next claimant. A satellite that deposits again as an orbit becomes one; an orbit cannot take satellite deposits.

Harvest

Your share of every delivery since your last touch, in the planet's asset — plus ETH, if a wind was vented. Entering, leaving and harvesting all settle first, so nothing is ever lost between actions.

The Sun

The Sun receives ETH from anywhere, but is built for two sources: the creator fees of $ORBIT, and planet fees. Pons sweeps the former to its fee escrow; collect() claims them (anyone may call it, it happens on its own at every interaction). ignite() then allots the Sun's unallotted ETH — the corona — to the planets by mass. A planet nobody orbits gets nothing; a planet everybody left hands its pending ETH back to the corona. Remainders of integer division stay in the corona for the next round.

The Sun holds no $ORBIT of its own, takes no cut, has no operator. There is no function that moves ETH or assets anywhere other than to fillers (against their delivery) and to bodies (what they are owed).

The solar wind

There is no DEX in the loop. A planet's pending ETH is a standing offer: deliver the planet's asset, take ETH at Pyth's price × (1 + discount). The discount starts at 0 when the wind starts blowing and reaches 5% after 6 hours; every fill resets it. Fills are capped at the pending ETH (the delivery is scaled down, you never over-deliver), and you set a minimum ETH out. Prices must be at most 120 seconds old — pass a Pyth update with the fill (the update fee is 0 wei on Robinhood Chain today) or rely on one already on chain.

Why a discount and not a fixed price: the filler bears the gas, the inventory and the price risk between fetching a Pyth update and inclusion. A Dutch ramp lets the market find the smallest discount at which someone will do it, and caps the Sun's cost at 5%.

The vent

If nobody fills for 30 days, anyone may vent() the planet: its pending ETH is owed to its bodies as ETH, pro rata to gravity, harvested the same way. The oracle is not a single point of failure for the money; the worst case is being paid in ETH instead of the asset.

Deployment

The Sun is created with CREATE2 through Arachnid's deterministic-deployment proxy (present on Robinhood Chain), from the exact bytecode this site embeds plus three constructor arguments — the Pons factory, Pyth, the ETH/USD feed. Its address is therefore known before it exists and identical whoever sends the transaction: 0x39aa28222F836C1Ba2cC298b316948abDcCeC1d4. Anyone can put it on chain from /deploy, anyone can then launch() $ORBIT — once — paying Pons' launch fee and an optional first buy (only the logo and website are free parameters), and anyone lights planets, before or after the launch.

deployer proxy

0x4e59b44847b379578588920cA78FbF26c0B4956C

salt

0xc3a481cb8f603fb3dd0ec775048dc0680467fcec84f3748914e8eba06cf34786 keccak256(“orbit:sun:v1”)

pons factory

0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e

pons escrow

0xd3AFEB2a57f70eF218Aa82451c51B2fb0416Ac9e

pyth

0x8250f4aF4B972684F7b336503E2D6dFeDeB1487a

What is verified, what is not

• Verified: the catalog's stock tokens exist and answer symbol()/name() with 18 decimals; Pyth is deployed at the address above with the feeds listed; the Pons V2 factory, forwarder and escrow addresses and signatures were traced on a fork; the Sun's own logic is covered by unit tests and by checks against the real chain on a fork, including a real NVDA holder delivering real NVDA to a lit planet and a body harvesting it.
• Assumed: that Pons credits the creator tax to the fee recipient through the same escrow as the base creator fee (a fork shows the tax deducted and held on the curve until Pons sweeps), and that it keeps sweeping after graduation. Both are Pons' behaviour; if they differ, the Sun simply receives less.
• Not knowable here: who really issued a token behind a planet the site did not check, and how any of this reads to a regulator. Tokenized stocks are claims on their issuer, not shares; nothing on this site is advice.