Questions

An ERC-20 that represents a claim on one Core. Accumulation adds harvested fee income to the Core's assets while the number of Laminae stays the same, so each one is worth more. Nothing is locked and there is no queue.

No Core is deployed by us, and that is deliberate. You deploy your own from the app in one transaction, which means you are its owner and nobody here can touch it. The bytecode you send is the bytecode this build compiled and executed.

Any of the tokenised equities on Robinhood Chain — the full list is here, every row read off the token contract rather than taken from a list. A Core holds exactly one asset.

No. Redemption is a call, not a request: you burn Laminae and the Core pays out in the same transaction, at the price it quotes. Stagnation can halt deposits and cannot halt redemption — that is property 12 and the build executes it.

Fees paid by people trading against the position a Core holds. You keep the position's exposure, including impermanent loss, which is why fee income and the mark on the underlying are reported separately instead of added together.

No. It has been compiled and executed: every build runs its properties on a real EVM and then breaks the contract five ways to confirm the suite notices. That is a weaker claim than an audit and a stronger one than a paragraph. What ran is on the security page.

You need the asset the Core holds. If you have none of it, the Core still reads — share price, total assets and supply all render before you connect a wallet, so you can inspect one without touching it.

No, and it cannot. The only write path is eth_sendTransaction through the wallet you chose, which signs in its own window. There is no server here, no API key and no proxy — every read goes straight from your browser to the public Robinhood Chain RPC.