Launch app

Parameters

Locked values

These are fixed unless a phase change moves them. Anything still undecided is called out at the bottom.

ParameterValueNote
Backing tokenUSDGStable denomination; backing is a price commitment
UnderlyingPlain ERC-721No token-bound accounts
Collection eligibilityCurated whitelistOwner-controlled, not open
Minimum backing5 USDGSecondary floor; curation is the primary defence
Backing mutabilityFixed at depositEscape hatch is withdrawal, not adjustment
WithdrawalFree, any timeRequired — makes fixed backing survivable
Selection weight1e36 ÷ backingInversely proportional
Pool priceHarmonic mean + 3%Surcharge splits 1% protocol / 2% depositors
Cold rebate0–100% of surchargeRamps linearly from a 60s to a 3600s gap
Crown tithe0.25% of priceFrom the protocol share only; disabled in Phase 1
Sell-back rate95% of backingPhase 1 value
Settlement discount5%To the protocol, toggleable to depositors
Keep-NFT fee1% of position valueFrom the depositor's backing return
Fee distributionEqual per active positionNot proportional to backing
Seed inventory20–40 positionsOwner-deposited; below 30 the draw stops feeling random

Why the minimum is not the defence

A flood of minimum-backed positions collapses both the price and the draw distribution. With 40 positions at 80 USDG, adding 100 positions at 5 USDG drags the harmonic mean from 80 to roughly 6.83 and hands the dust about 97.6% of draw probability.

A flat minimum cannot stop that, because an attacker simply scales the count. Curated collection whitelisting is what actually bounds it — the cost of the attack becomes the cost of acquiring NFTs from a curated collection, not the cost of the minimum.

Still open

  • Which collections make the initial whitelist
  • Whether whitelist administration gets a timelock
  • The Crown tithe rate
  • The Phase 2 trigger metric

Without a timelock, adding a collection is a trust assumption users will price in. That decision is not made yet and is not presented as if it were.