REFERENCES

Which numbers are real

A launchpad that quotes coins in other coins has one obvious failure mode: a price nobody can check. This page says exactly where every figure on the site comes from, including the ones that are invented.

01 There is one oracle in the whole system

CROWN is an ETH wrapper at a fixed 1 CROWN = 0.01 ETH, mint and redeem both directions. It tracks nothing, publishes nothing and cannot depeg, because it is a receipt rather than a claim on an index.

That leaves exactly one external number anywhere in SCION: ETH/USD, and it only ever affects the label. The pair math, the royalty math and the succession test all run in CROWN terms, so if the ETH price feed died tomorrow every mechanism in the protocol would keep working and only the dollar column would go dark.

This is a deliberate contrast with reference-asset launchpads that quote against published index levels. An index-backed quote asset needs somebody to keep publishing, and the pad has to trust them. A wrapper needs nobody.

02 How a dollar figure is built

No USD value is ever stored. Each is assembled at read time by walking the path:

price_in_crown = p₁ × p₂ × … × pₙ for the n hops between the coin and CROWN
usd_price = price_in_crown × 0.01 × eth_usd
market_cap = usd_price × total_supply

A generation 5 coin's dollar price is therefore the product of five independent markets. Five sources of noise, five sources of manipulation surface, one number. The pair page shows both the pair change and the dollar change side by side so the difference is never hidden.

FigureSourceStatus in this build
Pair priceThe pool's own reservesSimulated random walk, 48 hourly points
Price in CROWNProduct along the pathComputed live, real arithmetic
USD price and market capPath product × 0.01 × ETH/USDComputed live, ETH/USD held at 3,000
24h vs parentPair series, t−24h to tComputed live from the seeded series
24h in USDCompounded change of every hopComputed live
Royalty scheduleFixed protocol constantReal rule, contract enforced, 50 bps halving per generation
Succession ratioHeir cap ÷ parent cap, in CROWNComputed live in the browser; the contract gates on a real 24h TWAP, which the front end does not simulate
Coup slippageReserve size vs parent book depthFront end shows a constant-product estimate; the contract routes the trade for real
Coins, symbols, holders, creatorsNothingInvented for the prototype

03 What the fee schedule actually is

Total taker fee 100 bps on every swap, split as follows. The lineage column is what a coin at that depth pays upward in total.

RecipientBpsNotes
Pool30.00Retained in reserves
Protocol20.00Also funds gas refunds for succession callers
Parent25.00Generation 1
Grandparent12.50Generation 2
Great-grandparent6.25Generation 3
4th ancestor3.125The deepest named ancestor a depth cap of 5 permits
CROWNremainderAbsorbs whatever the chain is too short to take, and the share of any extinct ancestor

There is no fifth ancestor row, because the depth cap is 5 and the fifth hop up is CROWN itself. Note what this does to shallow coins: a generation 1 coin sends its full 50 bps to CROWN and keeps no ancestor on payroll, which is why the six slots directly under CROWN are the most valuable real estate on the pad and why nobody who holds one gives it up voluntarily.

04 The three honest weaknesses

05 What is not built yet

The contracts are written and tested but not deployed. There is no pad address, no live factory and no CROWN token on any chain, including 4663. Nothing on this site reads chain state and there is no wallet connection. Prices animating in the browser are a simulation running at one trade every 2.3 seconds so the royalty pulses are legible, not a feed. Holder counts, creator addresses and launch dates are fabricated.

What is real and reviewable right now: the mechanism, in Solidity, under 36 passing tests. Every claim on the Docs page has a named test behind it, including the unflattering ones. The coup is asserted to be lossy for the attacker. The reserve floor is asserted to be nearly unreachable by trading. Treat the site as a specification you can click and the test suite as the part you should actually audit, not as a market.