MiCA Whitepaper Inline XBRL

N	Field	Content
00	Table of contents	General Information Part A: Information about the offeror or the person seeking admission to trading Part B: Information about the issuer, if different from the offeror or person seeking admission to trading Part C: Information about the operator of the trading platform in cases where it draws up the crypto-asset white paper and information about other persons drawing the crypto-asset white paper pursuant to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 Part D: Information about the crypto-asset project Part E: Information about the offer to the public of crypto-assets or their admission to trading Part F: Information about the crypto-assets Part G: Information on the rights and obligations attached to the crypto-assets Part H: Information on the underlying technology Part I: Information on the risks Part J: Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts
01	Date of notification	2026-09-09
02	Statement in accordance with Article 6(3) of Regulation (EU) 2023/1114	This crypto-asset white paper has not been approved by any competent authority in any Member State of the European Union. The person seeking admission to trading of the crypto-asset is solely responsible for the content of this crypto-asset white paper.
03	Compliance statement in accordance with Article 6(6) of Regulation (EU) 2023/1114	This crypto-asset white paper complies with Title II of Regulation (EU) 2023/1114 of the European Parliament and of the Council and, to the best of the knowledge of the management body, the information presented in the crypto-asset white paper is fair, clear and not misleading and the crypto-asset white paper makes no omission likely to affect its import.
04	Statement in accordance with Article 6(5), points (a), (b), (c), of Regulation (EU) 2023/1114	The crypto-asset referred to in this crypto-asset white paper may lose its value in part or in full, may not always be transferable and may not be liquid.
05	Statement in accordance with Article 6(5), point (d), of Regulation (EU) 2023/1114	FALSE
06	Statement in accordance with Article 6(5), points (e) and (f), of Regulation (EU) 2023/1114	The crypto-asset referred to in this white paper is not covered by the investor compensation schemes under Directive 97/9/EC of the European Parliament and of the Council or the deposit guarantee schemes under Directive 2014/49/EU of the European Parliament and of the Council.
07	Warning in accordance with Article 6(7), second subparagraph, of Regulation (EU) 2023/1114	Warning This summary should be read as an introduction to the crypto-asset white paper. The prospective holder should base any decision to purchase this crypto-asset on the content of the crypto-asset white paper as a whole and not on the summary alone. The offer to the public of this crypto-asset does not constitute an offer or solicitation to purchase financial instruments and any such offer or solicitation can be made only by means of a prospectus or other documents pursuant to the applicable national law. This crypto-asset white paper does not constitute a prospectus as referred to in Regulation (EU) 2017/1129 of the European Parliament and of the Council or any other offer document pursuant to Union or national law.
08	Characteristics of the crypto-asset	STONKBROKER is a transferable crypto-asset deployed on Robinhood Chain and used within the StonkBrokers ecosystem. It is used to acquire StonkBrokers non-fungible tokens (NFTs) through the Anvil automated market maker (AMM), and to pay activation and upgrading fees for StonkBrokers NFTs in connection with participation in the StonkBrokers rewards programme. STONKBROKER may also be borrowed through a collateralised, protocol-level borrowing mechanism available within the StonkBrokers protocol and implemented through smart contracts on Robinhood Chain. A user may provide an eligible StonkBroker NFT as collateral and borrow a principal amount of 666,666 STONKBROKER. This mechanism does not, by virtue of holding STONKBROKER, confer or any claims of repayment of principal or interest. STONKBROKER does not confer upon its holders equity, ownership, corporate voting, dividend, liquidation, profit-sharing or other rights in the issuer or its assets. Furthermore, consistent with ESMA’s Guidelines on the conditions and criteria for the qualification of crypto-assets as financial instruments (ESMA75453128700-1323), in particular paragraphs 16 and 17, STONKBROKER performs a medium-of-exchange function within the StonkBrokers ecosystem. Accordingly, and having regard to the criteria set out in ESMA Guideline 2, STONKBROKER does not appear to qualify as a transferable security under Article 4(1)(44) of Directive 2014/65/EU (MiFID II), as it does not appear to satisfy the cumulative criteria applicable to transferable securities. In our understanding, STONKBROKER is not intended to embody any other rights or characteristics that would cause it to qualify as another category of financial instrument under MiFID II. References elsewhere in this white paper to STONKBROKER's prospective role as a 'governance token' (see F.2) concern solely protocol-level, technical or operational functions, specifically, directing liquidity flow within the Stonk Exchange, and do not constitute or imply any corporate voting right, dividend right, or other right of the kind excluded above.
09		Not applicable
10	Key information about the offer to the public or admission to trading	MiCA Crypto Alliance is now seeking its admission to trading of Stonkbroker assets within the EU so as to enable secondary market liquidity. This admission would allow existing holders to trade Stonkbroker on a regulated EU crypto-asset trading platform with a view to improving price discovery and stronger market depth. It is also intended to support broader asset distribution, which is an important factor in decentralised governance and wider stakeholder participation in ecosystem decisions.

N	Field	Content
C.1	Name	N/A
C.2	Legal form	N/A
C.3	Registered address	N/A
C.4	Head office	N/A
C.5	Registration date	N/A
C.6	Legal entity identifier	N/A
C.7	Another identifier required pursuant to applicable national law	N/A
C.8	Parent company	N/A
C.9	Reason for crypto-asset white paper Preparation	N/A
C.10	Members of the management body	N/A
C.11	Operator business activity	N/A
C.12	Parent company business activity	N/A
C.13	Other persons drawing up the crypto-asset white paper according to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114	N/A
C.14	Reason for drawing the white paper by persons referred to in Article 6(1), second subparagraph, of Regulation (EU) 2023/1114	N/A

N	Field	Content
E.1	Public offering or admission to trading	ATTR
E.2	Reasons for public offer or admission to trading	By admitting the asset to trading, holders of the token are expected to gain more transparent price discovery and improved liquidity. This is intended to enable the project’s community and ecosystem participants to more easily enter and exit positions, supporting a dynamic and efficient market.
E.3	Fundraising target	N/A
E.4	Minimum subscription goals	N/A
E.5	Maximum subscription goals	N/A
E.6	Oversubscription acceptance	N/A
E.7	Oversubscription allocation	N/A
E.8	Issue price	N/A
E.9	Official currency or any other crypto-assets determining the issue price	N/A
E.10	Subscription fee	N/A
E.11	Offer price determination method	N/A
E.12	Total number of offered/traded crypto-assets	1223243158 Under the current activation mechanism, 50% of STONKBROKER paid as activation fees is burned, while the remaining 50% is allocated to the protocol by default. The circulating supply stated above excludes STONKBROKER held in the designated Escrow Reserve and reflects the amount in circulation as at the date of this crypto-asset white paper.
E.13	Targeted holders	ALL
E.14	Holder restrictions	N/A
E.15	Reimbursement notice	N/A
E.16	Refund mechanism	N/A
E.17	Refund timeline	N/A
E.18	Offer phases	N/A
E.19	Early purchase discount	N/A
E.20	Time-limited offer	N/A
E.21	Subscription period beginning	N/A
E.22	Subscription period end	N/A
E.23	Safeguarding arrangements for offered funds/crypto-Assets	N/A
E.24	Payment methods for crypto-asset purchase	N/A
E.25	Value transfer methods for reimbursement	N/A
E.26	Right of withdrawal	N/A
E.27	Transfer of purchased crypto-assets	N/A
E.28	Transfer time schedule	N/A
E.29	Purchaser's technical requirements	N/A
E.30	Crypto-asset service provider (CASP) name	N/A
E.31	CASP identifier	N/A
E.32	Placement form	NTAV
E.33	Trading platforms name	Bitvavo B.V., Bitstamp Europe S.A., Payward Europe Solutions Limited (“Kraken”)
E.34	Trading platforms Market identifier code (MIC)	VAVO, BESA, PGSL
E.35	Trading platforms access	Admission to trading of the STONKBROKER crypto-asset is sought on Bitvavo, Bitstamp and Kraken. Access to trading, if admission is granted, will be provided through these trading platforms, including websites and mobile applications, in accordance with the trading platforms’ terms of use and applicable regulatory requirements.
E.36	Involved costs	Access to trading of the Stonkbroker crypto-asset on Bitvavo, Bitstamp and Kraken, if admission is granted, may involve costs charged by the trading platform. Such costs may include trading fees, deposit or withdrawal fees, custody-related fees, or other charges applied in accordance with trading platforms’ fee schedule and terms of use.
E.37	Offer expenses	Not applicable
E.38	Conflicts of interest	We have not identified any conflicts of interest arising at the moment of writing the white paper in relation to the offer or admission to trading.
E.39	Applicable law	Malta
E.40	Competent court	Malta

N	Field	Content
F.1	Crypto-asset type	Crypto-assets other than asset-referenced tokens or e-money tokens
F.2	Crypto-asset functionality	STONKBROKER is an ERC-20 crypto-asset deployed on Robinhood Chain and used across the StonkBrokers ecosystem. It can be transferred between compatible addresses and traded through supported markets. Within the Anvil NFT AMM, STONKBROKER is used to acquire StonkBrokers NFTs. It is also used to pay the applicable fees to activate or upgrade StonkBrokers NFTs for participation in the StonkBrokers rewards programme. Under the current activation mechanism, 50% of the STONKBROKER activation fee is burned and 50% is allocated to the protocol by default. STONKBROKER also functions as an ecosystem asset in other StonkBrokers applications. The Stonk Launcher permits launched crypto-assets to be paired with STONKBROKER, while Special Projects tokens may have liquidity paired with STONKBROKER at launch. The Stonk Exchange is live and provides decentralised trading, liquidity provision and gauge staking functionality of eligible liquidity positions within the wider StonkBrokers ecosystem. STONKBROKER may be borrowed through a collateralised borrowing mechanism available within the StonkBrokers protocol. A user may provide an eligible StonkBroker NFT as collateral and borrow a principal amount of 666,666 STONKBROKER. The borrowing fee is payable upfront in ETH and is calculated at an annualised rate of 15% by reference to the market value of the borrowed STONKBROKER expressed in ETH and the duration of the loan. A minimum loan term applies when calculating the fee. Any excess ETH provided by the borrower is refunded. Of the fees collected through the borrowing mechanism, 70% is allocated to the StockBooster mechanism and 30% to the protocol. To recover the NFT provided as collateral, the borrower must repay the principal amount of 666,666 STONKBROKER. Where repayment is overdue, an additional late fee is payable in ETH at the same annualised rate. The borrowing arrangement is a separate functionality of the StonkBrokers protocol. STONKBROKER is the crypto-asset borrowed and repaid under that arrangement. Holding STONKBROKER does not, in itself, create a right to receive interest, repayment or other payments from a borrower. STONKBROKER will be also designated as the governance token of the Stonk Exchange. The StonkBrokers documentation states that holders are to direct which pools, routes and ecosystem programmes receive directed flow.
F.3	Planned application of functionalities	Governance functionalities are planned to be implemented in future phases of the project development.
F.4	Type of crypto-asset white paper	OTHR
F.5	The type of submission	NEWT
F.6	Crypto-asset characteristics	STONKBROKER is a fungible and transferable ERC-20 crypto-asset deployed on Robinhood Chain at contract address 0xe934e36A439C94017B64a3FecE66AF12099aBF50. The total supply is 2,391,908,656.722 STONKBROKER, and the crypto-asset uses 18 decimal places. It is the ecosystem token of the StonkBrokers ecosystem and can be held and transferred using compatible blockchain wallets.
F.7	Commercial name or trading name	Stonkbroker
F.8	Website of the issuer	https://www.stonkbrokers.cash
F.9	Starting date of offer to the public or admission to trading	2026-10-09
F.10	Publication date	2026-10-08
F.11	Any other services provided by the issuer	Not applicable
F.12	Language or languages of the crypto-asset white paper	English
F.13	Digital token identifier code used to uniquely identify the crypto-asset or each of the several crypto assets to which the white paper relates, where available	PS4V5L9XQ
F.14	Functionally fungible group digital token identifier, where available	WJ4T4F79V
F.15	Voluntary data flag	FALSE
F.16	Personal data flag	TRUE
F.17	LEI eligibility	TRUE
F.18	Home Member State	Malta
F.19	Host Member States	Austria, Belgium, Bulgaria, Croatia, Cyprus, Czechia, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Liechtenstein, Lithuania, Luxembourg, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden

N	Field	Content
G.1	Purchaser rights and obligations	Not applicable. Holders of STONKBROKER do not, solely by acquiring or holding STONKBROKER, acquire any ownership, equity, profit participation, repayment, redemption or compensation rights against SB (BVI) Ltd or any other natural or legal person. Holding STONKBROKER does not give rise to contractual claims or entitlements against SB (BVI) Ltd or any other natural or legal person. Accordingly, the functionalities associated with STONKBROKER are functional and protocol-based. These include the ability to hold, transfer and trade STONKBROKER on Robinhood Chain, use STONKBROKER to acquire StonkBrokers NFTs through the AMM, and use STONKBROKER in connection with activation and other ecosystem functions. These functionalities are further described in F.2.
G.2	Exercise of rights and obligations	Not applicable as the asset confers no ownership or financial claims and does not impose any legal obligations.
G.3	Conditions for modifications of rights and obligations	Not applicable as the asset confers no ownership or financial claims and does not impose any legal obligations.
G.4	Future public offers	Not applicable
G.5	Issuer retained crypto-assets	N/A
G.6	Utility Token Classification	FALSE
G.7	Key features of goods/services of utility tokens	N/A
G.8	Utility tokens redemption	Not applicable
G.9	Non-trading request	TRUE
G.10	Crypto-assets purchase or sale modalities	Not applicable
G.11	Crypto-assets transfer restrictions	Not applicable
G.12	Supply adjustment protocols	FALSE
G.13	Supply adjustment mechanisms	STONKBROKER has a fixed initial supply, and the STONKBROKER token contract does not contain a minting function. No mechanism is provided at the token-contract level for increasing the token supply following deployment. The supply may, however, decrease where STONKBROKER tokens are burned. A protocol-level mechanism resulting in a reduction of the STONKBROKER supply is associated with the activation of StonkBroker NFTs. This mechanism is driven by demand for NFT activation and is not dependent on demand for the STONKBROKER token itself. When a StonkBroker NFT is activated, a discretionary action taken by the broker's owner, at one of five tiers (66,666 / 166,666 / 366,666 / 666,666 / 1,666,666 STONKBROKER). Activation fees are routed by the Activation Manager contract according to a configurable split (in basis points, summing to 10,000) across up to three destinations: a burn share (currently 5,000 bps / 50%, executed via the STONKBROKER contract's own burn function), a protocol-treasury share (currently 5,000 bps / 50%), and an optional third share (currently 0 bps) reserved for a future STONKBROKER redistribution mechanism. This split is not fixed: the Activation Manager contract's owner may change it at any time, and may also pause new activations entirely, suspending the burn mechanism until unpaused. The fee payable at each of the five activation tiers (66,666 to 1,666,666 STONKBROKER) is fixed at deployment and has no corresponding update function. The CollectionToken contract itself contains no minting function, so there is no corresponding supply-increase protocol.
G.14	Token value protection schemes	FALSE
G.15	Token value protection schemes description	Not applicable
G.16	Compensation schemes	FALSE
G.17	Compensation schemes description	Not applicable
G.18	Applicable law	There is no written legal agreement between the issuer and the crypto asset-holder that sets out the laws that govern the legal relationship between those two parties. In the absence of such an agreement, the laws that govern that relationship will depend on the location of the issuer and the given crypto asset-holder and characteristic performance of the legal relationship, and any agreed intention of the issuer and crypto asset-holder.
G.19	Competent court	There is no written legal agreement between the issuer and the crypto asset-holder that sets out which jurisdiction's courts will have authority to deal with a dispute between the crypto asset-holder and the issuer. In the absence of such an agreement, the laws of the competent court will depend on the location of the issuer and the given crypto asset-holder and characteristic performance of the legal relationship, and any agreed intention of the issuer and crypto asset-holder.

N	Field	Content
H.1	Distributed ledger technology	N/A as DTI is provided in F.13
H.2	Protocols and technical standards	Networking, transport and session STONKBROKER transaction submission uses Robinhood Chain's network interfaces rather than a token-specific networking layer. Public mainnet endpoints include a JSON-RPC address, a WebSocket sequencer feed and a direct sequencer endpoint. These are rate-limited and Robinhood recommends managed providers such as Alchemy, QuickNode, Blockdaemon, dRPC and Validation Cloud for production use. A wallet or application submits a signed transaction through an RPC service, and the sequencer receives and orders it for Layer 2 execution. Independently operated full nodes which are computers that download and independently verify the chain's complete transaction history, rather than relying on Robinhood's own infrastructure, run Offchain Labs' Nitro software, the client Robinhood Chain is built on. Running one requires two separate connections to the Ethereum network: an execution endpoint, which supplies ordinary account and transaction data, and a beacon endpoint, which supplies consensus data and is also needed to retrieve blob data — a lower-cost, temporary data-storage format that Ethereum provides specifically to support Layer 2 networks like Robinhood Chain. Ledger Robinhood Chain's ledger state is account-based and Ethereum-derived: token balances, contract storage and other state are processed by the sequencer and ultimately settle against Ethereum. The chain posts transaction data to Ethereum and uses Ethereum blobs for data availability, so a full node depends on both an Ethereum execution endpoint and a beacon endpoint capable of retrieving blob data to reconstruct and verify state. STONKBROKER's own balances exist as entries in the CollectionToken contract's storage within this ledger, rather than in an issuer-maintained off-chain register. Execution The deployed CollectionToken contract was written in Solidity, the programming language used for most Ethereum-style smart contracts, using version 0.8.26 and compiled for the Cancun upgrade of the Ethereum Virtual Machine (EVM), the shared rulebook that determines what a smart contract can do and how much it costs to run. It was compiled with an optimisation setting of 200 runs, a standard trade-off that increases contract size slightly in exchange for lower gas costs on functions used often. Robinhood Chain also allows larger contracts than Ethereum mainnet and provides Arbitrum-specific precompiles, built-in, ready-made functions any contract can call, comparable to a shared code library, for Layer 2-specific tasks such as reading the current Layer 2 block number or gas price. Execution and finality occur in stages. The sequencer first accepts, orders and executes a transaction, returning a soft confirmation, typically within under a second. Robinhood Chain orders transactions on a first-come, first-served basis by sequencer arrival time rather than through the priority-fee auctions used on Ethereum mainnet, so increasing a transaction's fee does not move it ahead of transactions already queued. Transactions are then batched and posted to the Ethereum Layer 1 inbox, which fixes their ordering subject only to an Ethereum reorganisation, and reach full finality once the Ethereum block containing the batch itself finalises. Robinhood Chain also applies sequencer-level compliance screening: a transaction associated with a sanctioned address is excluded from inclusion, and Robinhood may restrict specific wallet addresses from participating on the network. Read operations such as balance and log queries remain unaffected by this screening. Token standards STONKBROKER implements the ERC-20 fungible-token interface through CollectionToken, together with the ERC20Burnable extension for supported token burning and the ERC20Permit extension for gasless, signature-based approvals. Token precision is fixed at 18 decimals, and the total supply is fixed at deployment with no further minting function. The deployment deliberately omits an owner or administrator role, a post-deployment mint path, a transfer fee, a blacklist and a pause facility. These properties describe the STONKBROKER token contract itself and are distinct from the governance and upgrade arrangements that apply to Robinhood Chain's own Layer 2 protocol contracts, which are addressed in H.5. External APIs Applications interact with STONKBROKER through Robinhood Chain's standard JSON-RPC and WebSocket interfaces, which support reading data and broadcasting transactions, together with a sequencer feed for real-time updates. Archive endpoints for historical reads and indexing are available through infrastructure providers rather than the public endpoints. The deployment is additionally exposed through the Robinhood Chain Blockscout explorer, which provides contract-level read and write access; this is an inspection and interaction layer rather than a separate consensus component, and the canonical token state remains the state produced by Robinhood Chain execution. Robinhood Chain does not maintain a dedicated software development kit for STONKBROKER specifically; integrators building on the chain generally use Alchemy's published Robinhood Chain API tooling.
H.3	Technology used	Implementation and architecture STONKBROKER is implemented as a smart-contract token rather than as a separate node or consensus client. Its direct implementation is the CollectionToken contract described in H.1. The underlying chain runs Arbitrum Nitro. Robinhood operates the chain's sequencer, while other operators can run full Nitro nodes using Robinhood's published chain-information and genesis configuration. The architecture also relies on a set of contracts deployed on Ethereum itself, rather than on Robinhood Chain: a Rollup contract, which records and settles Robinhood Chain's state on Ethereum; a Sequencer Inbox, where batches of transactions are posted; a Delayed Inbox, the backup submission route described in I.5; a Bridge, which holds and manages assets moving between the two chains; and an Outbox, which finalises withdrawals back to Ethereum. Runtime and build parameters Robinhood Chain's published full-node instructions reference Nitro node version 3.11.2-3599aca and confirm that the network currently runs ArbOS 61. Mainnet nodes load Robinhood's chain-information file and custom genesis configuration and connect to Ethereum execution and beacon endpoints. These build parameters describe the deployed token code rather than the Nitro client run by Robinhood Chain nodes. Dependencies The verified CollectionToken source imports the OpenZeppelin ERC-20 implementation together with its ERC20Burnable and ERC20Permit extensions, and a project-specific zero-address error definition used to reject a null initial holder. No further token-level modules for pausing, blacklisting, transfer taxation or administrator-controlled minting appear in the verified source. At the network level, Robinhood Chain depends operationally on access to Ethereum execution and beacon data, since full nodes require both to synchronise Layer 1 state, including blob data. Data availability and dispute resolution Robinhood Chain posts transaction data to Ethereum and uses Ethereum blobs for data availability, and settlement proceeds in the stages set out in H.4. Robinhood Chain uses Bounded Liquidity Delay, referred to as BoLD, for dispute resolution, secured by a permissioned validator set that monitors on-chain assertions and can submit fraud-proof challenges against an invalid state assertion. The network currently has two validators, operated by Offchain Labs and Alchemy; running a validator requires inclusion in an allowlist and a bond of 1 WETH. The canonical bridge between Ethereum and Robinhood Chain uses the Arbitrum bridging architecture and does not rely on third-party bridge validators, so its security is tied directly to Ethereum. Deposits from Ethereum typically confirm within around ten minutes. Withdrawals from Robinhood Chain to Ethereum are subject to a seven-day challenge period required by the fraud-proof system before a final claim transaction can be submitted on Ethereum.
H.4	Consensus Mechanism	STONKBROKER does not participate in consensus through a token-specific validator or block-production mechanism; transactions involving the token execute within, and inherit the settlement guarantees of, Robinhood Chain. Robinhood Chain's sequencer initially orders transactions, returning a soft confirmation typically within under a second. The sequencer then batches transactions and posts the batch to the Ethereum Layer 1 inbox, which fixes ordering subject only to an Ethereum reorganisation; this stage typically takes minutes. Full finality is reached once the Ethereum block containing the batch itself finalises on Ethereum, typically around thirteen minutes after posting, at which point the transaction inherits Ethereum's security and is irreversible. Robinhood Chain additionally uses BoLD for dispute resolution, under which its permissioned validator set can challenge an invalid state assertion, as described in H.3. Ethereum's own consensus is proof-of-stake. Time is divided into twelve-second slots and epochs of thirty-two slots, and one validator is randomly selected to propose a block in each slot. A validator joins by depositing 32 ETH into the network's deposit contract, and validator committees vote on proposed blocks through attestations. Checkpoint finality, governed by the Gasper mechanism, requires votes representing at least two-thirds of total staked ETH across two successive checkpoints before the earlier of the two becomes finalised; Gasper combines Casper-FFG finality with the LMD-GHOST fork-choice rule, which favours the fork with the gre=atest accumulated weight of attestations. Validators who equivocate, submit contradictory attestations or contradict earlier checkpoint votes can be slashed, losing part or all of their staked ETH and being removed from the active validator set; reverting a finalised Ethereum block would require destroying at least one-third of total staked ETH. This layered arrangement gives STONKBROKER transactions distinct confirmation levels: the sequencer provides a soft confirmation for everyday use, posting to Ethereum establishes ordering against an Ethereum reorganisation, and Ethereum finality provides the settlement finality. Canonical withdrawals from Robinhood Chain back to Ethereum are additionally subject to the seven-day fraud-proof challenge period described in H.3.
H.5	Incentive Mechanisms and Applicable Fees	Network-level fees STONKBROKER transactions pay Robinhood Chain network fees denominated in ETH. A transaction fee has two components: a Layer 2 execution component, reflecting gas used multiplied by the Layer 2 gas price, and a Layer 1 data component, reflecting the cost of posting the transaction's calldata to Ethereum, which varies with Ethereum network congestion and calldata size. Both components are bundled into the gas paid by the transaction, and standard gas estimation accounts for both automatically. The Robinhood Chain sequencer collects these fees as part of its transaction-processing role. CollectionToken itself contains no transfer-fee mechanism, so an ordinary STONKBROKER transfer carries no additional levy beyond this network gas. Application-level fees STONKBROKER is also used as a unit of account within the StonkBrokers application layer, independently of Robinhood Chain's ETH-denominated gas. Activating a Stonk Broker non-fungible token for tier-weighted reward distributions costs STONKBROKER, split by default 50% to token burning and 50% to the protocol. Acquiring the next available broker through the Anvil non-fungible token automated market maker costs a flat 666,666 STONKBROKER plus an ETH fee, with a further native ETH trade fee of 10% on swaps and 15% on targeted purchases of a specific token. A broker can also be used to borrow the same 666,666 STONKBROKER principal against it as collateral, with the borrowing fee paid upfront in ETH at an annualised rate of 15% on the loan's market ETH value and split 70% to the reward pool and 30% to the protocol. These application-level charges arise from separate StonkBrokers protocol contracts rather than from any levy built into the CollectionToken transfer function itself. Validator and sequencer incentives Ethereum validators receive ETH rewards for honestly proposing and attesting to blocks and can lose rewards for non-participation or have staked ETH destroyed for slashable behaviour, securing the settlement layer on which Robinhood Chain ultimately relies. At the Robinhood Chain dispute layer, a BoLD validator must be included in an allowlist and stake a bond of 1 WETH; the network's two current validators are operated by Offchain Labs and Alchemy. The Robinhood Chain sequencer separately collects the applicable gas fees described above. Official documentation does not set out a separate validator reward schedule or the allocation of sequencer revenue beyond the collection of gas fees. Governance of parameters Robinhood Chain's protocol governance is exercised through an eight-signer Security Council. Robinhood holds two seats, and the remaining six are held individually by BitGo, Chainlink Labs, Fireblocks Trust Company, Offchain Labs, Paxos and Talos. Routine actions require approval from six of the eight signers and pass through a seven-day on-chain timelock; emergency actions bypass the timelock but require seven of the eight signers. This governance structure, together with the chain's proxy-administration contracts, governs Robinhood Chain's own protocol parameters. It has no bearing on CollectionToken, whose verified source contains no owner, administrator or fee-setting function of its own.
H.6	Use of distributed ledger technology	FALSE
H.7	DLT functionality description	Not applicable
H.8	Audit	TRUE
H.9	Audit outcome	Independent security assessments have been undertaken in respect of technology supporting the STONKBROKER operating environment, with the STONKBROKER CollectionToken contract falling outside the scope of these assessments. The Stonk Brokers Safety Deposit Box liquidity-locker and token-vesting system underwent a Hashlock-certified audit signed off on 15 July 2026. The underlying BoLD technology that Robinhood Chain runs has also undergone independent review by Trail of Bits. The CollectionToken contract's absence of an owner, administrator or post-deployment mint function is instead evidenced directly by its verified source, as set out in H.1. Hashlock (0xSimpleFarmer) \| 15 July 2026 – Stonk Brokers Safety Deposit Box Object: Security review of the Stonk Brokers liquidity-locker and vesting system, covering the locker core, the lock-ownership ERC-721, the vesting contract, an extended Uniswap V3 position-manager interface and a minor addition to the launcher factory. The review combined line-by-line static analysis, threat modelling, property-based analysis and live verification on Robinhood Chain testnet. Uniswap V3's own core and periphery contracts, the frontend, off-chain infrastructure and Robinhood Chain's chain-level security were outside its scope, as was the STONKBROKER token contract itself. Results: No critical findings were identified. Two high-severity issues were identified during the review, both concerning fee accounting (one when liquidity was decreased, one when the upfront locker fee was charged); both were fixed prior to publication of the audit report, so no high-severity finding remains open. One medium-severity issue, concerning cancellation of a vesting schedule after tokens had already vested, was fixed. Two further medium findings, an owner-controlled reference to the launcher factory and the absence of a pause mechanism, were accepted rather than remediated. Six low-severity and three informational findings were also recorded. Actions: Regression tests were added for the fixed findings, and the patched contracts were redeployed to Robinhood Chain testnet, where Hashlock re-executed the full lock, decrease-liquidity, collect and release lifecycle and confirmed bytecode integrity against the audited source. Current official documentation shows only two fee modes offered on new locker deposits, an upfront charge and a share of collected swap fees; the audited withdrawal-fee mode remains in effect solely for pre-existing locks that selected it and is no longer offered for new deposits, a status this white paper records as deprecated rather than current. Trail of Bits \| 2 August 2023 – Arbitrum Chains Challenge Protocol v2 (initial BoLD audit) Object: Independent review of the version of Arbitrum's challenge protocol subsequently adopted as BoLD, Robinhood Chain's dispute-resolution mechanism, covering the Solidity and Go implementations of proof utilities, challenge edges, the off-chain edge tracker and challenge watcher, and the assertion-chain contracts. Two consultants conducted twenty engineer-weeks of static and dynamic testing between March and June 2023. Results: Thirty-four findings, comprising eight High, six Medium, five Low, thirteen Informational and two Undetermined in severity. The High findings included challenge-state and proof-processing defects, a validator front-running condition capable of triggering denial of service, stale honest-edge snapshots that were not refreshed from the chain, and errors in the calculation of the path timers used to determine when an edge may be confirmed. Actions: Trail of Bits recommended formal documentation of the protocol's incentive assumptions, an incident-response plan and expanded off-chain testing, and the report's own fix-review appendix records the resolution status of the identified findings as at delivery. Arbitrum's public audit register separately lists a further review, completed in May 2024, of BoLD contract fixes arising from this audit together with changes to the sequencer inbox's delay buffer.

Part I - Information on risks

N	Field	Content
I.1	Offer-related risks	Market volatility and speculative-value risk STONKBROKER's price is set entirely by public trading on decentralised and centralised exchanges rather than by any backing asset, cash flow or redemption right, and it can move sharply on limited volume. The project's own materials describe several of its core mechanics, including Broker Box and Stonk Launcher's buyback draws, in explicitly chance-based terms, with disclosed theoretical payout rates. This speculative, game-adjacent design increases the likelihood of pronounced price swings that are unrelated to any change in the underlying technology. Execution and slippage risk STONKBROKER is tradable across multiple venues, including several decentralised exchange pools on Robinhood Chain (Uniswap V3, Uniswap V4, up. and other automated market makers) and on centralised exchanges. Execution quality depends on the liquidity available in the specific venue and pool used for a trade, and a trade can execute at a less favourable rate than quoted where liquidity is thin or prices move before the transaction is confirmed.
I.2	Issuer-related risks	Dependency risk STONKBROKER's continued use within the StonkBrokers ecosystem depends on SB (BVI) Ltd and other entities associated with the project continuing to operate and develop the Anvil NFT AMM, the Stonk Exchange, and the other StonkBrokers applications through which STONKBROKER is spent. These applications are developed and maintained by a single named operator rather than by a decentralised or redundant set of parties. If any event were to cause these entities to cease operations, restructure, or discontinue development of these applications, the STONKBROKER-denominated functions they provide could become unavailable, even though the underlying ERC-20 contract described in Part H would continue to operate independently of any application built on top of it.
I.3	Crypto-assets-related risks	Transaction finality and irreversibility risk Robinhood Chain's sequencer cannot modify, reverse or cancel a transaction once it has been submitted. An erroneous STONKBROKER transfer, an approval granted to an incorrect address, or a transaction executed on the basis of mistaken instructions cannot be corrected through any protocol-level reversal. Private-key custody risk Robinhood Chain's services are non-custodial, and holding or using STONKBROKER depends on the holder's own wallet and the cryptographic credentials that control it. Loss or compromise of a private key or seed phrase results in permanent loss of control over the associated STONKBROKER holdings, with no recourse to Robinhood, SB (BVI) Ltd or any other party. Supply and contract-parameter reliance risk STONKBROKER is a fixed-supply ERC-20 token: its full supply was minted once, to the address specified at deployment, and the verified contract contains no function to mint further tokens. Holders rely on the correctness of this deployed implementation, and the burn function built into the contract can permanently and irreversibly reduce any balance and the circulating supply when exercised. Ecosystem application dependency risk STONKBROKER is used within specific StonkBrokers applications beyond simple transfer and holding: it is spent to acquire and activate brokers and to borrow against them on the Anvil NFT AMM, and it is designated as the token intended to direct liquidity flow within the Stonk Exchange. These are functions of third-party and protocol-level smart contracts, not a right to redeem STONKBROKER for a good or service supplied by SB (BVI) Ltd. Administrative-control boundary risk The verified STONKBROKER contract itself has no owner, administrator, post-deployment mint function, transfer fee, blacklist or pause function. This absence of on-chain control applies only to the CollectionToken contract; it does not extend to the separate StonkBrokers application contracts described in Part H, several of which retain owner-controlled parameters of their own, nor to Robinhood Chain's protocol-level governance described in I.5.
I.4	Project implementation-related risks	External protocol dependency risk The Stonk Exchange depends on the DEX infrastructure of up. (a third-party decentralised exchange protocol, accessible at up33.xyz, whose native token is UP), the Safety Deposit Box locker integrates Uniswap V3 position NFTs, Uniswap V4 positions held directly in Uniswap's PoolManager, and up. liquidity positions, both its Slipstream concentrated-liquidity NFTs and its v2 pool LP tokens, as external dependencies. A failure, incompatible upgrade or interruption at any of these third-party protocols can impair trading, liquidity management or related StonkBrokers functionality even where the STONKBROKER contract itself continues to operate normally. Liquidity-lock contract risk The Safety Deposit Box escrows locked liquidity positions and issues transferable ownership NFTs representing withdrawal rights. Its independent security review, detailed in H.9, found no critical or open high-severity issues at delivery: two high-severity and one medium-severity issue identified during testing were all fixed before the audit report was published. Two further medium-severity items were reviewed and knowingly accepted rather than changed: the contract owner can update the launcher-factory reference, and the deployment has no emergency pause facility. These two accepted items mean the owner retains that one configuration power, and that there is no mechanism to halt new activity in an incident, until or unless the design is revisited. Locker deployment and configuration risk The liquidity locker's Uniswap V3 position-manager address is set immutably at deployment. Current official documentation confirms no admin key can seize, withdraw or release locked liquidity, and that the owner's only remaining administrative powers are the two described above: updating the launcher-factory reference and rotating the recipient of future protocol fees. A misconfigured deployment can still affect which assets are supported or how fees are routed going forward. Permanent liquidity constraint Liquidity raised through Stonk Launcher is routed into the Safety Deposit Box and locked there permanently by design. Permanently locked liquidity cannot subsequently be withdrawn and redeployed in response to changing market conditions, a protocol migration, or a change in project requirements. Programme jurisdictional-access risk Participation in the Marketing Program operates on a whitelist basis under Appendix A of the Program Terms, which the Project may update at any time, and expressly excludes residents of several jurisdictions, including the United States, the United Kingdom, Canada and Switzerland, from Program participation. This restriction governs eligibility to earn Program compensation rather than the ability to hold or transfer STONKBROKER itself, but it can still affect which holders are able to participate in this particular distribution channel and on what terms. Promotional conduct risk The Program Terms prohibit Qualifying Posts from stating or implying STONKBROKER's price, trading volume, market value or prospective appreciation, and from describing Program compensation using the words royalty, dividend, yield or passive income. Inaccurate or non-compliant statements by individual participants, made outside these contractual constraints, could still create misleading expectations about the token's economic characteristics.
I.5	Technology-related risks	Smart-contract code risk STONKBROKER's behaviour is determined by the deployed bytecode of its ERC-20 contract, including its burn and permit extensions. A defect in that implementation could affect transfers, approvals or burns notwithstanding that the source code is publicly verified as an exact match. Sequencer availability and censorship risk Robinhood operates Robinhood Chain's sole sequencer and gives no guarantee of its uptime, expressly contemplating downtime, latency or unavailability. Arbitrum Nitro, the technology Robinhood Chain runs, provides a general backstop for this: a transaction submitted directly to the Delayed Inbox on Ethereum that the sequencer does not process within a bounded window, currently around 24 hours, can be force-included by any participant, bypassing an unresponsive or ordinarily censoring sequencer. This backstop does not extend to Robinhood Chain's own compliance-driven exclusions: Robinhood Chain's documentation confirms that it applies sequencer-level compliance screening under Arbitrum's Advanced Compliance Filtering feature, which is specifically designed so that a transaction restricted on compliance grounds is still blocked at the state-transition level even if force-included through the Delayed Inbox. Layer-2 governance concentration and emergency-powers risk Robinhood Chain's protocol governance is exercised by an eight-signer Security Council, on which Robinhood holds two seats and six independent institutions hold one seat each. Routine actions require six of the eight signers and a seven-day on-chain timelock, while emergency actions require seven of the eight signers and can bypass that timelock. This structure spreads authority across multiple institutions and enforces a delay on routine changes, but the emergency pathway still allows urgent, timelock-free changes to the chain on which STONKBROKER executes. Validator concentration and dispute-resolution risk Robinhood Chain's BoLD dispute-resolution mechanism relies on a permissioned validator set that currently comprises two validators, operated by Offchain Labs and Alchemy. Fraud-proof monitoring and challenges accordingly depend on a small, though allowlist-expandable, set of authorised operators, concentrating operational responsibility for detecting an invalid state assertion. Ethereum data-availability and settlement dependency risk Robinhood Chain posts its transaction data to Ethereum as blobs for data availability and depends on Ethereum's proof-of-stake consensus for full transaction finality, as described in Part H. A disruption to Ethereum's liveness or finality would affect Robinhood Chain's ability to synchronise, retrieve data or settle transactions, independently of whether the STONKBROKER contract itself is affected. RPC, indexing and state-visibility risk Robinhood Chain's public RPC endpoints are rate-limited and Robinhood may throttle, suspend or discontinue them without notice, and displayed blockchain data may be delayed, inaccurate or temporarily unavailable. A wallet, interface or monitoring system relying on these endpoints can show stale or incomplete state, or fail to submit a transaction, even while the underlying chain continues to operate normally. Protocol upgrade risk Robinhood Chain's protocol can be upgraded in ways that materially change chain operation, disrupt bridge or service integrations, or introduce defects. This risk applies to STONKBROKER because its execution and state reside on Robinhood Chain, even though its own verified contract holds none of the governance powers that control such upgrades. Quantum computing risk STONKBROKER transactions, including permit-based approvals under the token's ERC20Permit extension, are authorised using ECDSA signatures on the secp256k1 curve, the cryptographic method (and underlying mathematical formula) used to prove a transaction was authorised by the holder of a specific private key, without revealing that key itself. This is the same method used to secure ordinary Ethereum accounts, and Robinhood Chain's ultimate settlement finality depends on Ethereum validators' BLS-based consensus signatures. A sufficiently powerful quantum computer running Shor's algorithm could in principle derive a private key from a public key that has been exposed on-chain, which happens whenever an address sends a transaction, enabling forged signatures and theft from the affected account; this is commonly referred to as a "harvest now, decrypt later" exposure for any account that has already transacted. Current quantum hardware remains far short of the scale needed to carry out such an attack, and the U.S. National Institute of Standards and Technology anticipates deprecating ECDSA only from 2030 and disallowing it from 2035, but the underlying cryptography that secures STONKBROKER holdings, and the Ethereum consensus that Robinhood Chain ultimately settles against, would both be affected if this threat materialises before a network-wide migration is complete.
I.6	Mitigation measures	Offer-Related Risks Execution and slippage risk: The Stonk Exchange swap interface exposes selectable slippage tolerances of 0.1%, 0.5% and 1.0%, allowing a trade to fail rather than execute beyond the chosen tolerance. This control applies to trades placed through the Stonk Exchange interface specifically; a trade placed directly on another venue where STONKBROKER is listed is subject to that venue's own execution and slippage controls, which this white paper does not describe. Crypto-Assets-Related Risks Supply and contract-parameter reliance risk: STONKBROKER's contract is verified on the Robinhood Chain block explorer as an exact match to its published source, allowing the fixed-supply mechanism, the absence of a further mint function, and the other control boundaries described in Part H to be independently inspected rather than taken on trust. Ecosystem application dependency risk: The CollectionToken contract's core ERC-20, burn and permit functions operate independently of the StonkBrokers application layer, so basic transfer, holding and burning of STONKBROKER would continue to function even if the Anvil NFT AMM, Stonk Exchange or another StonkBrokers application became unavailable. Administrative-control boundary risk: The same exact-match source verification shows directly that CollectionToken has no owner, administrator, post-deployment mint function, transfer fee, blacklist or pause function, so this control boundary can be confirmed independently rather than relying on the issuer's description of it. Project Implementation-Related Risks Liquidity-lock contract risk: The Safety Deposit Box's independent security review recorded no open critical or high-severity findings after remediation, with each fix covered by a regression test and re-verified through live execution on Robinhood Chain testnet, including a bytecode-integrity check against the audited source. Locker deployment and configuration risk: The mainnet deployment process includes a pre-flight check confirming that the configured Uniswap V3 position manager resolves to a genuine Uniswap V3 factory before deployment proceeds, and current official documentation confirms the deployed locker retains no admin power beyond rotating the future fee recipient. Promotional conduct risk: The Program Terms contractually prohibit Qualifying Posts from making price, trading-volume or appreciation claims about STONKBROKER, or from describing Program compensation as a royalty, dividend, yield or passive income. Technology-Related Risks Smart-contract code risk: STONKBROKER's source code is verified on the Robinhood Chain block explorer as an exact match to the deployed contract, exposing its implementation and control boundaries to public and independent inspection. Sequencer availability and censorship risk: Arbitrum Nitro's Delayed Inbox and forceInclusion mechanism let any participant submit a transaction directly to Ethereum and have it included within a bounded window, currently around 24 hours, without the sequencer's cooperation, other than for a transaction restricted under Robinhood Chain's compliance filtering as described above. Offchain Labs additionally maintains an active bug-bounty programme for Arbitrum Nitro through Immunefi, alongside the continuing independent audit programme described in Part H. Layer-2 governance concentration and emergency-powers risk: Routine Security Council actions require six of the eight signers, held across Robinhood and six independent institutions, and are subject to a seven-day on-chain timelock; emergency actions require seven of the eight signers. This spreads authorisation across multiple independent parties and enforces a delay on routine protocol changes, though the timelock can still be bypassed for emergency actions. Ethereum data-availability and settlement dependency risk: Ethereum's proof-of-stake finality requires checkpoint votes representing at least two-thirds of total staked ETH, and a validator who equivocates or votes against a finalised checkpoint is subject to slashing, providing an economic security foundation for the settlement layer Robinhood Chain relies upon. RPC, indexing and state-visibility risk: Robinhood Chain supports several independent infrastructure providers in addition to its own public endpoints, permits independent full-node operation, and publishes a public status page covering mainnet and testnet availability, thereby providing an alternative access point for monitoring the chain's operational state. Quantum computing risk: The Ethereum Foundation has operated a dedicated Post-Quantum Security team since January 2026 and has published a structured migration roadmap, targeting completion of core post-quantum consensus and signature infrastructure by approximately 2029, built on cryptographic standards finalised by the U.S. National Institute of Standards and Technology in August 2024. The planned approach uses account abstraction to let individual accounts adopt quantum-safe signatures voluntarily as they become available, rather than requiring every account to migrate simultaneously, and an account that has never sent a transaction retains additional protection in the meantime because its public key has not yet been exposed on-chain.

General information	Page 3
Part A - Information about the offeror or the person seeking admission to trading	Page 4
Part B - Information about the issuer, if different from the offeror or person seeking admission to trading	Page 5
Part C - Information about the operator of the trading platform in cases where it draws up the crypto-asset white paper and information about other persons drawing the crypto-asset white paper pursuant to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114	Page 6
Part D - Information about the crypto-asset project	Page 7
Part E - Information about the offer to the public of crypto-assets or their admission to trading	Page 8
Part F - Information about the crypto-assets	Page 9
Part G - Information on the rights and obligations attached to the crypto-assets	Page 10
Part H – Information on underlying technology	Page 11
Part I - Information on risks	Page 12
Part J - Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts	Page 13

Index

General information

Part A - Information about the offeror or the person seeking admission to trading

Part B - Information about the issuer, if different from the offeror or person seeking admission to trading

Part C - Information about the operator of the trading platform in cases where it draws up the crypto-asset white paper and information about other persons drawing the crypto-asset white paper pursuant to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114

Part D - Information about the crypto-asset project

Part E - Information about the offer to the public of crypto-assets or their admission to trading

Part F - Information about the crypto-assets

Part G - Information on the rights and obligations attached to the crypto-assets

Part H – Information on underlying technology

Part I - Information on risks

Part J - Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts