The app executed
Deposit, hold, redeem
Deploy a Core over any of the 94 assets on Robinhood Chain, deposit into it, and redeem at the price the Core computes. Real contracts, real transactions, on chain 4,663.
Your Cores
Every number here is read before you connect anything
The vault list, share prices and total assets all come straight off Robinhood Chain. A wallet is needed only to sign. There is no registry contract, so this lists the Cores you have deployed from this browser — not a global list, and the page does not pretend otherwise.
Nothing sent yet.
What you are signing
The bytecode is the one the build proved
The creation code this page deploys is emitted by the same step that compiles Core.sol and executes its 15 properties on a real EVM, then breaks it five ways to confirm the suite notices. It is not a different build and there is no proxy in front of it.
- You deploy the Core, so you are its owner. Nobody here can touch it.
- The protocol cut is 10% of harvested fees and the cap is a constant in the code — there is no function that raises it past 20% and no proxy to swap the code out.
- Deposits are halted by Stagnation; redemption cannot be, and property 12 executes that.
- This is not audited. It is compiled, executed and deliberately broken — a weaker claim than a review and a stronger one than a paragraph.
No private key is handled by this site and none can be.
The only write path is eth_sendTransaction through the wallet you chose,
which signs in its own window. Nothing here asks for a seed phrase and there is no
server to send one to.
| What was executed | Result | |
|---|---|---|
| A1 | the page's constructor arguments deploy a Core | ran |
| A2 | the string argument survived encoding (the Lamina has a symbol) | ran |
| A3 | the uint argument survived encoding (the fee is set and under the cap) | ran |
| A4 | the address argument survived encoding (the Core points at the right asset) | ran |
| A5 | the page's approve calldata is accepted by the token | ran |
| A6 | the page's deposit calldata mints Laminae | ran |
| A7 | the deposit really moved the asset out of the depositor | ran |
| A8 | Accumulation raised the share price (it rises; it does not start at one) | ran |
| A9 | the page's redeem calldata is accepted by the Core | ran |
| A10 | the redemption paid the asset back | ran |
This table is about the page, not the contract.
/core proves Core.sol is correct; that is a different claim from
“the page sends the right bytes”, and the second one is where a front end
actually breaks. Both failures that showed up here were exactly that shape and neither
reverted anything: a constructor argument pointing at a placeholder produced a Core
holding nothing, and an approve naming the caller instead of the Core made
every deposit fail with no reason string.