Architecture
Security & Trust Model
We believe in stating trust assumptions honestly. This page describes what secures StonkBrokerChain today, and what you are trusting when you use it.
What is trust-minimized
- Data availability — all transaction batches are posted to Robinhood Chain. The chain’s full history is reconstructable from parent-chain data; the operator cannot hide state.
- The bridge escrow — bridged $STONKBROKER is held by the canonical Arbitrum bridge contracts, not by a custodian or a multisig wallet.
- Deposits — flow through the rollup inbox with no operator discretion.
- EVM execution — deterministic Nitro execution; anyone can run a node, sync from parent-chain data, and verify state.
What is trusted today
- The sequencer orders transactions. It cannot forge or steal funds, but it could censor or go offline. Nitro’s delayed-inbox mechanism lets users force-include transactions via Robinhood Chain.
- The validator / fast confirmer posts and immediately finalizes state assertions, so exit finality currently trusts that key. The validator set is whitelisted, so no third party can post competing assertions either.
- Chain administration — an
UpgradeExecutorcontract can adjust chain parameters, as is standard for new Orbit chains.
Summary
Honest summary
StonkBrokerChain today is a fast, data-available chain whose exit finality relies on an honest operator — the same practical model as most young appchains, with the benefit of full data availability on Robinhood Chain and Ethereum underneath it.
The decentralization path
- 1More validators — expand the whitelist, then disable it; BoLD permissionless validation makes assertions fraud-provable by anyone.
- 2Retire fast confirmation — once real validators exist, withdraw the fast-confirmer role, or keep fast exits via liquidity providers.
- 3Sequencer decentralization as the Orbit ecosystem matures.
- 4Move chain admin to a multisig or to governance.