/blueprintbaskade.xyz/docsstatus: testnet MVP · unaudited

Every rule, every
number, every address.

The blueprint is the protocol's paper trail: what each contract may do, which parameters bound it, and exactly what lives on Robinhood Chain Testnet today. Addresses first — verify before you interact — then the five facts, then the numbers, then the answers.

A · Core contracts

6 non-upgradeable

B · Mock price feeds

7 300 s heartbeat

C · Deployed

09·17 2026

D · Admin keys over funds

§01 — Deployment

Live on Robinhood
Chain Testnet.

2026-09-17 · chain 46630

Contract	Address	Verify

deployed 2026-09-17 · non-upgradeable · gas in native ETH · deployer holds no admin keys over funds

§02 — Primer

Five facts that
frame the rest.

primer · read this, then the sources

Fact 01What it is: A protocol for issuing tokenized index baskets on Robinhood Chain — the tokenized-assets L2: a weighted, leveraged set of synthetic exposures (stocks, ETFs, crypto) packaged into one ERC-20. Mint the share, run the strategy.
Fact 02Six contracts: WNATIVE, OracleRegistry, IndexOracle, FeeVault, BackstopPool, BasketFactory. No owner withdraw keys anywhere — governance can only narrow parameters within hard caps.
Fact 03Four states: A basket moves Seeded → Active → Frozen → Settled. Transitions are deterministic health() outcomes, never an operator's judgment call. A frozen basket redeems at NAV and nothing else.
Fact 04Leverage, synthetically: Exposure comes from a counterparty pool, not borrowed assets. Actual leverage is measured from NAV and margin; a 0.25× drift triggers permissionless rebalances, 3.25× triggers emergency deleverage — anyone may call either for a bounty.
Fact 05Native-asset collateral: The chain's gas token is native ETH; Baskade wraps it as 18-decimal WNT — the protocol's unit of account. Entry/exit 10 bps each, management 1%/yr, performance 10% over high-water — declared at minting, only ever reducible.

§03 — Numbers

The arithmetic,
before you mint.

a worked example · not a forecast

Ten wrapped ETH walk the full path — deposit, entry fee, shares struck at NAV, target exposure. Every number below is a declared parameter, not a projection; nothing depends on an operator behaving well.

01 · Deposit

10.0000WNT — wrapped native ETH

02 · Entry fee

10 bps0.0010 WNT → FeeVault

03 · Minted

9.9990shares struck at NAV 1.0000

04 · Target exposure

2.00×on a BTC·ETH-style basket

Entry10 bps

Exit10 bps

Management1% / yr

Performance10% over HWM

fees accrue per second, performance by the dilution method over a high-water mark · each bound hard-capped on-chain (≤ 50 / ≤ 50 / ≤ 2% / ≤ 20%)

§03·A — Specification

Every bound.
One sheet.

specification · full table

Parameter	Default	Bound
Weight constraint	Σ\|wᵢ\| = 100%	single leg ≤ 50% · long-only in Phase 1
Legs per basket	2 – 5	hard cap 8
Target leverage	1.0× – 3.0×	creation refused above 3.0×
Rebalance trigger	\|L_actual − L_target\| ≥ 0.25×	permissionless · keeper-bountied
Emergency deleverage	L_actual ≥ 3.25×	anyone may call
Soft liquidation	NAV ≤ 15% of entry	—
Entry / exit fee	10 bps / 10 bps	each ≤ 50 bps
Management fee	1% / year	≤ 2% · accrues per second
Performance fee	10% over high-water mark	≤ 20% · dilution method
Oracle heartbeat	300 s (testnet)	any stale leg → protocol halt
Deposit asset	WNT — wrapped native ETH	18 decimals · protocol unit of account
Gas token	ETH (native)	~0.01 gwei typical

§04 — FAQ

Asked.
Answered.

six questions · straight answers

Q·01What exactly do I hold?+

An ordinary ERC-20 — the share token of one basket vault. Minting strikes it at NAV, redeeming burns it at NAV, and in between it is transferable, listable and composable like any token. The weighted, leveraged strategy is the token; there is no separate claim to sign.

Q·02Where does the leverage come from?+

From the counterparty pool, not from borrowed assets. Exposure is synthetic: the pool underwrites it against margin, and actual leverage is measured from NAV and margin on every health check. A 0.25× drift from target triggers a permissionless rebalance; 3.25× triggers emergency deleverage — anyone may call either, for a bounty.

Q·03What if an oracle goes stale?+

Every feed must beat a 300-second heartbeat (testnet value). The moment any leg goes stale, the whole floor halts — mints, redeems and rebalances included — until freshness returns. Failure is designed to be loud and total, never partial or quiet.

Q·04Can the terms change after I mint?+

Weights, bands and exit terms are declared at minting and immutable afterwards. Governance can only narrow parameters within hard caps — it can never widen fees, raise leverage past the ceiling, or touch your redemption at NAV.

Q·05What does it cost?+

Entry 10 bps, exit 10 bps, management 1% per year accruing per second, performance 10% over a high-water mark by dilution. Each is bounded on-chain — 50 / 50 / 200 / 200 bps-equivalent ceilings — and the schedule is identical for every basket.

Q·06Is this audited? Is there a mainnet?+

No and no. Baskade today is an experimental, unaudited testnet MVP on Robinhood Chain 46630 with mock price feeds. Treat every number on this site as a demonstration; leveraged baskets can lose all deposited capital, and nothing here is investment advice.

§05 — Roadmap

Three seasons,
on the record.

roadmap · v0.2

LIVE
Phase 01

Testnet MVP

Six non-upgradeable contracts on Robinhood Chain 46630, eight demo baskets, twelve mock feeds on a 300 s heartbeat, permissionless rebalances with bounties.

Phase 02

Depth

Short weights, liquidation incentives, fuzz and simulation reports published with the blueprint, Chainlink stock and ETF feeds mapped to the registry.

Phase 03

Mainnet review

Compliance assessment, audited contracts, position limits ramp, and the $BASK utility evaluated against the checklist before anything ships.

Baskade is experimental software on a public testnet. Contracts are unaudited. Leveraged baskets can lose all deposited capital. Nothing here is investment advice.