A SHARED SHELTER / SEASON 00ROBINHOOD CHAIN · ETH

Your ETH. Your horizon.A shared shelter.

Lock ETH. Hold sBOND. Share in protocol revenue that has actually arrived, with a long-term horizon.

LAUNCH DAPP
DESIGN PREVIEW · NO LIVE DEPOSITSSCROLL TO EXPLORE ↓
✳ BUILT AROUND REAL MECHANICS
✳ THE IDEALESS NOISE. MORE CONVICTION.

Markets move. Commitment has direction. Keep ETH as principal, hold sBOND as your receipt, and share in revenue that has actually arrived. Every reserve visible. Every unlock date clear.

[01]1:1 ETH

PROPOSED PRINCIPAL BACKING

[02]180

DAYS / 6-MONTH LOCK

[03]365

DAYS / 12-MONTH LOCK

[04]Variable

REVENUE-BASED BONUS

The mechanism(03)

READ THE RULES
PRE-LAUNCH / The contract is deployed but not audited. Deposits remain paused. Initial balances are simulated.NO LIVE YIELD
PRINCIPAL IN RESERVE. REVENUE SHARED.

Built on ETH.
Backed by ETH.

1 sBOND : 1 ETH principal in the proposed contract.
Bonuses are separate. Dollar value follows the price of ETH.

DESIGN PREVIEW / NOT A LIVE BACKING CLAIM
04 — THE RULESPROTOTYPE · TERMS DRAFT

Know the rules.
Own your decision.

01 / PRINCIPAL

sBOND is a receipt.

Depositing 1 ETH mints 1 sBOND. Principal stays in the contract. This design has no lending, staking or operator access to withdraw principal.

02 / REVENUE

Only what comes in.

Revenue enters through a dedicated funding function. There is no fixed APY or reward payment from new participant deposits. The business source, funding schedule and revenue share are not yet defined.

03 / EXIT

A date you can see.

Lock for 180 or 365 days from the deposit transaction, with no early exit. After maturity, claim bonuses or redeem principal plus bonuses. Pausing deposits does not block mature withdrawals.

Are legacy sBOND points also backed?

No. This is a new contract design. Legacy demo points carry no ETH claim and are not converted automatically. No second pETH receipt claims the same reserves.

How does deposit timing affect revenue sharing?

Only positions open when revenue is funded receive a share. New positions do not receive past revenue. The operator controls funding timing; delays may change who receives a bonus. Revenue amounts and funding schedules are not promised.

Is the protocol ready for real funds?

Not yet. The contract is deployed and its address is configured, but it is not audited. Deposits are paused and website transactions are disabled. Revenue sourcing, reporting and implementation verification are required before activation. The operator currently uses a personal wallet.

✳ THE LONG RUN STARTS WITH UNDERSTANDING.

Build through
the red.

Understand the vault, explore scenarios and find your horizon. Start with simulated funds.

OPEN THE DAPP