One reserve. Real assets. No pretending the Stockpile exists yet.
Not deployedNo contract has been deployed on Robinhood Chain, so there is no balance to read. This figure stays empty until the Stockpile holds assets.
Configured target allocation. Not current holdings — the Stockpile holds no assets until deployment.
| Asset | Target | Held | ||
|---|---|---|---|---|
Robinhood Markets | Tokenized equity | 25% | Not deployed | |
NVIDIA | Tokenized equity | 20% | Not deployed | |
Tesla | Tokenized equity | 20% | Not deployed | |
Wrapped Ether | Crypto | 20% | Not deployed | |
GameStop | Tokenized equity | 15% | Not deployed |
Volatility is the fuel. The Stockpile is the destination.
Five stages, one direction. Scroll or select a stage to follow the loop — every complete turn leaves more assets behind than it started with.
Activity is the input
The liquid token trades on open venues. Direction does not matter — buying and selling both produce protocol activity.
One token to trade. One token to own the Stockpile.
Splitting the roles keeps speculation away from the claim. The liquid token can be as volatile as the market wants; the claim token tracks what the protocol has actually accumulated.
What the market touches. It exists to be traded, listed and speculated on — and every trade it produces feeds the protocol.
- Freely tradable on external venues
- Fixed supply, no transfer tax
- Trading activity generates protocol fees
- Holds no direct claim on the Stockpile
Stockpile
Wrapping locks the liquid token and mints the claim on the Stockpile. Burn it and a proportional share of the reserve comes back out.
- Minted by wrapping the liquid token
- Represents the economic claim on the Stockpile
- Redeemable pro-rata by burning
- Future collateral for the Phase II lending market
Stockpile Claim
Wrapping is a one-way door you can walk back through: PILE in, vPILE out, minus the wrap fee. Burning vPILE releases a proportional slice of the Stockpile. Between those two actions, the claim only moves in one direction — up — because the Stockpile only ever accumulates.
Turn a trade into a claim.
Wrapping is the only way to mint vPILE. It is reversible, priced by a single configured fee, and requires no counterparty.
- 01
Hold PILE
Acquire the liquid token on an open venue. Nothing about holding it is protocol-specific.
- 02
Wrap
Send PILE to the wrapper. The configured wrap fee (0.50% proposed) is deducted and routed to the reserve engine.
- 03
Receive vPILE
The wrapper mints the claim token against the net amount. Your position is now a claim rather than a trade.
- 04
Hold the claim
Every acquisition the reserve engine makes lands behind that claim. No action is required to benefit from it.
- Robinhood MarketsNot deployed
- NVIDIANot deployed
- TeslaNot deployed
- Wrapped EtherNot deployed
- GameStopNot deployed
Quantities are computed from live reserve balances at the moment of redemption. Until the Stockpile holds assets there is nothing to divide, so each leg is shown empty rather than estimated.
Burn the claim. Take the assets.
Redemption is the floor under vPILE. Burning it releases a proportional share of everything the Stockpile holds, less the configured redemption fee.
Rules, stated before there is anything at stake.
Policy written after a reserve holds assets is marketing. Written before, it is a constraint. These are the constraints Stockpile is building against.
Parameters subject to ratification
Every fee has exactly one destination.
There is no treasury discretion in the path from fee to asset. Collected fees are forwarded to the reserve engine, which places acquisition orders against the configured target weights.
- Market activityProtocol take on routed PILE trades0.50%
- WrappingPILE to vPILE0.50%
- UnwrappingvPILE back to PILE1.00%
- RedemptionvPILE burned for assets1.00%
- Borrow interest and originationPhase II lending market
- Market activityTrades, wraps, redemptions
- Protocol feesCollected per event
- Reserve engineAllocates against target weights
- AcquisitionsAssets bought, never rotated
The engine cannot choose to hold cash, chase a different asset or time an entry. Its mandate is the configured basket.
The Stockpile grows on activity, not emissions. Nothing in the design mints new liquid supply to pay for assets.
The interface is finished. Only the chain is missing.
Enter appThese are live fragments of the app, rendered by the same components the dapp uses — not screenshots. Every control works; only the final transaction is refused.
The event terminal is wired to the indexer contract-first: swaps, wraps, redemptions, Stockpile acquisitions and fee settlements will stream in here the moment the protocol is live.
Enter the app.
Walk the whole product now — dashboard, swap, wrap, redeem, borrow and the activity terminal. Nothing is faked and nothing can be signed. When contracts land, the same screens start reading real state.
Every protocol parameter on this site is provisional and centrally configured. Nothing here is a deployed value.