Index baskets · ERC-20 · non-custodial — Robinhood Chain, the tokenized-assets L2
Cut the market. Hold the whole index.
Lapidex compiles weighted, leveraged baskets of stocks, ETFs and crypto into a single ERC-20 share. You hold one token; the books keep themselves — every leg marked to market on a 300-second heartbeat, drift rebalanced for a bounty, fees settled per second.
The tape, read live.
RPC · public · no wallet neededEvery basket on the floor — leverage against target, NAV per share, state and oracle freshness — read straight from the vault contracts. Pick a row and operate it in the Terminal.
| Basket | Leverage act / tgt | NAV / share | State | Oracles | |
|---|---|---|---|---|---|
| Reading chain… | |||||
minted at NAV · redeemed at NAV · states are deterministic health() outcomes, never an operator's call
ETH in. Exposure out.
four commands · no discretion in betweenNo managers, no signature chains — weights, bands and NAV do all the work. Each step below is one command against the contracts.
-
01
$ compose --Σw 100%
Compose
Pick 2–8 legs from the price registry, set weights that sum to 100% (no single leg above 50%), choose a leverage target from 1.0× to 3.0×. The factory refuses anything outside the bands — checked on-chain, not in the frontend.
-
02
$ mint --deposit WNT
Mint
The basket compiles to a vault contract. Wrap native ETH, deposit, and the vault strikes shares at the current NAV per share. No lockup, no whitelist — two transactions on first mint: approve, then deposit.
-
03
$ keep --drift 0.25x
Keep
Keepers watch the drift. When actual leverage strays 0.25× from target, anyone may rebalance for a fixed bounty. Oracles mark every leg on a 300-second heartbeat; one stale leg halts the whole floor — failure is loud, never quiet.
-
04
$ redeem --at NAV
Redeem
Burn any amount of shares at NAV, any time. Exit terms are declared at minting and can only improve. Selling the share is exiting the strategy — nothing settles off the record.
Draft a basket in the console.
interactive · runs locally · nothing signedThis is the exact shape the on-chain composer accepts. Step the weights in 5% increments, pick a leverage target, and read the verdict — every rule here is enforced by the factory, not by a frontend promise.
rules: 2–8 legs · single leg ≤ 50% · target 1.0×–3.0×
The arithmetic, before you cut.
a worked example · not a forecastTen 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.
fees accrue per second, performance by the dilution method over a high-water mark · each bound hard-capped on-chain (≤ 50 / ≤ 50 / ≤ 2% / ≤ 20%)
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 |
Who stands under the leverage?
the floor · three answers- UnderwritingThe counterparty pool
- Liquidity providers deposit WNT and underwrite the synthetic exposure every basket runs on. Leverage never comes from borrowed assets or an off-book desk — it comes from the pool, priced by utilization, visible on the board in real time.
- Bad seasonsThe backstop
- When a basket lands badly, losses absorb in a published order — fees first, then the pool's buffer — never at an operator's discretion. The order is declared in the contracts and cannot be rearranged after the fact.
- BookkeepingAnyone, for a bounty
- Rebalances and emergency deleverages are permissionless calls with fixed bounties. There is no privileged keeper to bribe or wait for — the floor keeps itself, one bounty at a time.
Asked. Answered.
six questions · straight answersQ·01What exactly do I hold?+
Q·02Where does the leverage come from?+
Q·03What if an oracle goes stale?+
Q·04Can the terms change after I mint?+
Q·05What does it cost?+
Q·06Is this audited? Is there a mainnet?+
Three seasons, on the record.
roadmap · v0.2Testnet MVP
Six non-upgradeable contracts on Robinhood Chain 46630, two demo baskets, seven mock feeds on a 300 s heartbeat, permissionless rebalances with bounties.
Depth
Short weights, liquidation incentives, fuzz and simulation reports published with the blueprint, Chainlink stock and ETF feeds mapped to the registry.
Mainnet review
Compliance assessment, audited contracts, position limits ramp, and the $LAPI utility evaluated against the checklist before anything ships.
The record is set on Robinhood Chain.
deployment ledger · chain 46630- Network
- Robinhood Chain Testnet — Arbitrum Orbit L2 · chain 46630 · gas in native ETH
- Contracts
- 15 deployments — 6 core contracts, 7 mock feeds, 2 demo baskets · non-upgradeable
- Price feeds
- 7 mock feeds (BTC, ETH, NVDA, TSLA, AAPL, SPY, QQQ) · 300 s heartbeat · Chainlink path mapped
- Baskets
- MIX2X (BTC 50 / ETH 50, 2×) and TECH3X (NVDA 40 / TSLA 30 / SPY 30, 3×) live · backstop pool seeded with WNT
- Next season
- Short weights, liquidation incentives, fuzz & simulation reports
Lapidex is experimental software on a public testnet. Contracts are unaudited. Leveraged baskets can lose all deposited capital. Nothing here is investment advice.