/blueprintlapidex.xyz/docsstatus: testnet MVP · unaudited

Every rule, number and 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 source documents in order.

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

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

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; Lapidex 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.

The source documents.

docs/ · 17 files

Functional docs answer what the product does; dev docs answer how it is built. Paths are relative to the repository root.

Product overviewPositioning, problem, users, core conceptsdocs/functional/01-product-overview.md

User journeysInvestors, strategy authors, LPs, keepersdocs/functional/02-user-journeys.md

Basket lifecycleSeeded → Active → Frozen → Settleddocs/functional/03-basket-lifecycle.md

Composer specWeights, bands, refusal rulesdocs/functional/04-composer-spec.md

Vault & share mechanicsNAV from margin, mint/redeem, attack resistancedocs/functional/05-vault-mechanics.md

Leverage engineCounterparty pool, targets, rebalancingdocs/functional/06-leverage-engine.md

Fee modelEntry/exit, management, performance (dilution)docs/functional/07-fees.md

Risk & liquidationHard caps, circuit breaker, wind-downdocs/functional/08-risk-and-liquidation.md

Token utility$LAPI — designed, not shippeddocs/functional/09-token-utility.md

System architectureContract graph, data flow, rolesdocs/dev/10-architecture.md

Contract inventoryResponsibilities + Solidity interfacesdocs/dev/11-smart-contracts.md

Oracle designIndex aggregation, testnet mocks, Chainlink pathdocs/dev/12-oracle-design.md

Arc chain noteslegacy Arc deployment eradocs/dev/13-arc-chain-notes.md

Deployment guideFoundry end-to-end, chain 46630docs/dev/14-deployment-guide.md

Testing strategyUnit / invariant / fuzz / simulationdocs/dev/15-testing-strategy.md

Security checklistThreat model, pre-mainnet gatesdocs/dev/16-security-considerations.md

RoadmapPhase 1 testnet MVP → Phase 3 mainnet reviewdocs/dev/17-roadmap.md