One asset. Two environments. One paper.

1. Core thesis

SUPRX is supposed to act like digital gold on its own chain. wSUPRX is supposed to act like the access rail. The native side carries final settlement and reserve truth. The Base side carries easier market access and application reach.

2. What this is not

This is not two unrelated coins. It is not a trustless bridge. It is not a stablecoin. It is not a claim that thin-pool price spikes equal full market value.

3. Native chain

• SHA256d proof-of-work.
• Target block time: about 2 minutes.
• Current block subsidy era: 25 SUPRX per block.
• Native monetary bound in code: about 52.56 million SUPRX.

4. Wrapped side

• wSUPRX is the official Base ERC-20 wrapper.
• The intended relationship is 1 SUPRX = 1 wSUPRX before bridge fees.
• Reserve surplus helps solvency. It does not change the intended conversion ratio.

5. Wrap path

• User sends native SUPRX to the official treasury address first.
• User submits a wrap claim with amount, native Transaction ID, native source, and Base recipient.
• Operators confirm the native deposit, then mint net wSUPRX on Base.

6. Redeem path

• User connects the Base wallet that already holds wSUPRX.
• The bridge burns wSUPRX on Base.
• Operators release native SUPRX to the entered `sx1` destination address.

7. Fee model

• Wrap fee: 0.25%
• Redeem fee: 0.25%
• 1.00000000 SUPRX wraps to 0.99750000 wSUPRX before gas.
• 1.00000000 wSUPRX redeems to 0.99750000 SUPRX before gas.

8. Reserve rule

The public policy target is simple: wrapped supply should stay less than or equal to locked native reserve. That is the solvency rule. It is not a promise that the Base pool will always give a clean exit at the displayed quote.

9. What is public

• Reserve proof.
• Bridge audit history.
• Explorer visibility.
• Base contract addresses and pool addresses.

10. What is not trustless

The bridge is operator-relayed. It is reserve-backed and auditable, but runtime execution still depends on operator wallets and Safe control. It should be described accurately, not romanticized.

11. Liquidity and price

The Base pool is a market rail, not the definition of value. A thin pool can print a high quote and still fail to absorb real selling pressure. Liquidity is not reserve. Liquidity is not supply. Liquidity is not market cap.

12. Mining posture

Mining should stay native-first while the wrapped pool remains shallow. The current wrapped-side market should not be treated as a miner exit rail until it is materially deeper and can survive real flow.

13. Wallet and distribution

• The public wallet should show wrapped-side market reference, but label it honestly as a thin-market reference.
• Windows and Linux releases should ship together.
• Checksums and update manifests should be public and current.

14. Public stack

• Dashboard
• Reserve proof
• Bridge audit
• Project overview
• Tokenomics
• Builder bounties

15. What success looks like

• Users can verify the native chain quickly.
• Users can see reserve proof without guessing.
• Users can wrap and redeem with clear status messages.
• The wallet and website stop confusing thin market prints with deep liquidity.

16. Present limits

• Peer count is still low.
• The wrapped pool is still thin.
• Bridge operations still depend on live operators and operator gas.
• Public distribution only works well when the site, downloads, and update manifest stay in sync.