Token design

SUPRX follows chain rules. wSUPRX follows reserve rules.

This is the part people love to muddy up. The native coin follows the chain's issuance schedule. The wrapped side should exist only as far as locked native SUPRX can actually back it.

1. Native issuance schedule

SUPRX follows a native proof-of-work schedule with about 2 minute blocks, a current subsidy of 25 SUPRX per block, and a halving rhythm built around roughly four years.

2. Native monetary bound

Under the current rules, the chain points to a long-run monetary bound of about 52.56 million SUPRX. Again: chain number, not wrapped-token theater.

3. How wrapped supply works

Native SUPRX is locked on the SUPRX chain.
Matching wSUPRX is minted on Base.
wSUPRX is burned on redemption back to native SUPRX.

4. Reserve-side limit

wSUPRX does not need to mirror the chain max as a fixed ERC-20 cap. The real limit is reserve backing. No reserve, no honest wrapped growth.

5. How reserve surplus can grow

Wrap fee: gross SUPRX goes in, net wSUPRX is minted.
Redeem fee: gross wSUPRX is burned, net native SUPRX is released.
Manual top-ups: native SUPRX can be added to treasury directly.

6. What that does not guarantee

Reserve growth improves solvency. It does not magically create a USD floor, deep liquidity, or a painless exit at the printed pool quote.

7. Scanner notes

Some scanners will flag wSUPRX as mintable or pausable. That is normal in a wrapped-token setup with explicit mint authority and emergency pause roles.

8. Real trust question

The real question is not whether those controls exist. It is who holds them, whether minting stays inside reserve limits, and whether the backing stays public and fresh.

9. Conversion rule

The intended conversion relationship remains 1 SUPRX to 1 wSUPRX before fees. The wrap fee and redeem fee are 0.25% each.

10. What not to confuse

Reserve is not liquidity.
Liquidity is not market cap.
Wrapped supply is not the native max supply.
Coverage ratio is not a bonus redemption ratio.