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 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

2026-08-31

This crypto-asset white paper has not been approved by any competent authority in any Member State of the European Union. The operator of the trading platform of the crypto-asset is solely responsible for the content of this crypto-asset white paper.

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.

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.

FALSE

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.

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.

PONS is a fungible and transferable crypto-asset deployed on Robinhood Chain through the pons launch protocol. Robinhood Chain has Chain ID 4663 and uses ETH as its native gas token.

PONS was launched with a fixed supply of 1,000,000,000 PONS and trades against Wrapped Ether (WETH) through a locked liquidity pool. PONS has graduated under the pons launch mechanism, meaning that its liquidity pool reached the applicable graduation threshold. Trading continues through the same liquidity pool following graduation.

Not applicable

The token has been admitted to trading to the trading platform operated by Bitstamp Europe S.A. on its own initiative

TRUE

Pons Labs, LLC

No publicly available disclosure conclusively identifies the legal entity, if any, that qualifies as the issuer of Pons token within the meaning of Regulation (EU) 2023/1114 (MiCAR).

However, Pons Labs, LLC “Pons” is identified as the entity associated with the operation of the pons platform. The official Pons website indicates that 100% of the fees associated with the PONS token go back to Pons.

Furthermore, PONS was launched on Robinhood Chain through the PONS protocol with a fixed total supply of 1,000,000,000 PONS, issued in a one-time issuance through the token contract at 0x39dBED3a2bd333467115dE45665cC57F813C4571. The token was deployed through the legacy PONS launch factory contract at 0x0c37a24F5D23A486FA692d1500881d698B1F77a4 Accordingly, the issuance appears to have been effected through a specific smart contract deployment on Robinhood Chain, with an underlying entity or natural person responsible for the deployment. However, no issuer has presently been identified with sufficient certainty. No publicly available official information conclusively links the deployer or creator address associated with PONS to Pons Labs, LLC or to any other identified legal person.

Based on our best assessment, Pons Labs, LLC may be regarded as the entity most closely associated with the development and operation of the Pons platform and the launch infrastructure through which PONS was launched. However, its role as the legal issuer, initial distributor, or continuing administrator of the PONS token has not been independently established. Furthermore, its full legal name, registration details, registered address, management body, and precise role in relation to PONS have not yet been independently confirmed.

While no conclusive or verifiable evidence was identified in Pons official public sources directly confirming the connection, we consider Pons LLC to be a Delaware legal entity. This assessment is based on the close alignment between the Delaware entity’s registration date in 2026, which coincides with the commencement of Pons activity.

CWRI

No conclusive evidence was found regarding the head office of Pons Labs, LLC. For the purpose of complying with the technical requirements of the MiCA XBRL taxonomy, the registered address of Pons Labs, LLC has been reflected as the head office address.

Delaware

US-DE

No conclusive evidence was found regarding the head office of Pons Labs, LLC. For the purpose of complying with the technical requirements of the MiCA XBRL taxonomy, the registered address of Pons Labs, LLC has been reflected as the head office address.

Delaware

US-DE

2026-07-15

No conclusive information was found confirming the existence of a parent company for Pons Labs, LLC.

Development and operation of the Pons blockchain platform and token-launch infrastructure, providing a software interface for launching and interacting with crypto-assets on Robinhood Chain.

No conclusive information was found confirming the existence of a parent company for Pons Labs, LLC.

Bitstamp Europe S.A.

5GGB

40, avenue Monterey, L-2163, Grand Duchy of Luxembourg

LU-LU

40, avenue Monterey, L-2163, Grand Duchy of Luxembourg

LU-LU

2015-05-19

549300XIBGTJ0PLIEO72

Bitstamp Europe S.A. is registered with the Luxembourg Trade and Companies Register under the number B196856.

Robinhood Markets, Inc with its registered office at 85 Willow Road, Menlo Park, California 94025, USA.

Bitstamp Europe S.A., acting in its capacity as a crypto-asset service provider (CASP) and operator of a trading platform, has prepared this crypto-asset white paper to support the admission to trading of the crypto-asset on its platform and to provide users with the information required under Regulation (EU) 2023/1114 (MiCA).

Bitstamp Europe S.A. is a Crypto-Asset Service Provider authorised with the CSSF under the number N00000003 to provide the following crypto-asset services:

• providing custody and administration of crypto-assets on behalf of clients;
• operation of a trading platform for crypto-assets;
• exchange of crypto-assets for funds;
• exchange of crypto-assets for other crypto-assets;
• execution of orders for crypto-assets on behalf of clients;
• reception and transmission of orders for crypto-assets on behalf of clients; and
• providing transfer services for crypto-assets on behalf of clients.

Bitstamp Europe S.A. is a payment institution authorised by the CSSF under number Z00000012 to provide the following payment services:

3.a) execution of direct debits, including one-off direct debits,

3.b) execution of payment transactions through a payment card or a similar device,

3.c) execution of credit transfers, including standing orders and

6.) money remittance.

Bitstamp Europe S.A. has notified the cross-border provision of payment services and of crypto-asset services in all EU and EEA member states.

Bitstamp has admitted the asset to which this white paper relates to, to trading on its own initiative on its trading platform.

Robinhood Markets, Inc. is the parent holding company of the Robinhood group.

MiCA Crypto Alliance Limited

MiCA Crypto Alliance Limited was mandated to assist in the white paper preparation by Bitstamp Europe S.A. Bitstamp Europe S.A. retains the role of person seeking admission to trading.

Pons

Pons

PONS

Pons is a crypto-asset launchpad and trading protocol deployed on Robinhood Chain. The protocol enables users to create fixed-supply crypto-assets and provides mechanisms for their initial trading and subsequent liquidity through decentralised markets.

Under the current Pons v2 protocol architecture, newly launched crypto-assets initially trade through a bonding curve and, upon reaching the applicable graduation threshold, transition to a permanently locked Uniswap v4 liquidity pool for continued decentralised trading.

The protocol incorporates mechanisms for liquidity locking, trading fees, creator fees and protocol fees. PONS is a crypto-asset associated with the pons ecosystem and was launched through the legacy pons v1 factory. Under the Pons v1 protocol revenue mechanism, protocol funds may be used to acquire PONS and send the acquired tokens to a burn address.

FALSE

Past milestones

The pons project was created as a permissionless crypto-asset launch and trading protocol on Robinhood Chain following the launch of Robinhood Chain mainnet on 1 July 2026. PONS was launched through the legacy pons factory with a fixed supply of 1,000,000,000 PONS. PONS subsequently reached the applicable graduation threshold and continues to trade through the same liquidity pool.

The pons protocol subsequently introduced an updated v2 launch architecture on Robinhood Chain. Under v2, newly launched crypto-assets initially trade through a bonding curve and, upon completion of the curve, graduate into a Uniswap v4 liquidity pool whose liquidity is permanently locked.

The protocol has also implemented a PONS buyback and burn mechanism. At present, 80% of protocol fees allocated to the protocol are used to purchase PONS through an automated time-weighted average price (TWAP) mechanism, with purchased PONS sent to a burn address, thereby permanently reducing the circulating supply. The remaining 20% are allocated to infrastructure costs and expansion of the Pons team.

Future milestones

The current PONS buyback arrangement is not yet immutable and is intended to become immutable, decentralised and automated in a future release

80% of protocol fees are currently used for PONS buybacks, while the remaining 20% are allocated to infrastructure costs and expansion of the pons team. No further quantified breakdown of the financial, human or technical resources allocated to the PONS crypto-asset or individual components of the pons project. In particular, no specific monetary amounts, personnel allocations or breakdown of the 20% operational allocation between infrastructure and team expansion are disclosed.

Not applicable

Bitstamp Europe S.A. has admitted the token to trading based on its market considerations.

When a client purchases a token on the Bitstamp Europe S.A.'s trading platform, the crypto-asset will be credited to their Bitstamp account. If a client wants to hold the token in their own wallet, they will need to (i) provide an external blockchain wallet address, where the crypto-assets will be sent if a withdrawal is initiated and (ii) satisfy all other requirements applicable to a withdrawal in line with the Regulation (EU) 2023/1113 of the European Parliament and of the Council of 31 May 2023 on information accompanying transfers of funds and certain crypto-assets.

When a client purchases a token on the Bitstamp Europe S.A.'s trading platform, the crypto-asset will be credited to their Bitstamp account and a client does not need to fulfill any other technical requirement to hold the crypto-assets on their Bitstamp account, apart from have either a computer or phone with an internet connection and appropriate software in order to interact with the Bitstamp services.

Bitstamp

BESA

Investors can access the trading platform through https://www.bitstamp.net or via the Bitstamp applications.

There are no costs involved in creating an account on the trading platform, however trading fees and other costs apply in accordance with the fee schedule available at https://www.bitstamp.net/fee-schedule.

Not applicable

Because PONS is issued on Robinhood Chain, a blockchain network developed and maintained by RHDA, LLC (Robinhood Digital Assets, LLC), an affiliate of Bitstamp within the Robinhood Group, there is potential for a conflict of interest to arise in connection with Bitstamp's admission of the token to trading.

Any potential conflict of interest arising from this is mitigated by the Bitstamp by Robinhood Group Code of Conduct and Trading Policy. In accordance with the Code of Conduct, all officers, directors, employees, agents, representatives, contractors and consultants (and other persons, regardless of job or position) are required to report any situation where there is the potential for a conflict of interest between their own interests and the interests of Bitstamp / Robinhood. The Trading Policy in place within the Group prohibits all forms of market manipulation and has been designed to prevent insider trading.

Not applicable, as this point pertains to an "offer to the public," whereas this white paper relates to admission to trading.

Not applicable, as this point pertains to an "offer to the public," whereas this white paper relates to admission to trading.

Crypto-assets other than asset-referenced tokens or e-money tokens

PONS can be held and transferred through compatible wallets and traded through decentralised trading infrastructure on Robinhood Chain.

PONS has a protocol-related function through the pons buyback and burn mechanism. Under the current mechanism, 80% of protocol fees are used to acquire PONS on the market through an automated TWAP mechanism. The acquired PONS are sent to a burn address, permanently reducing the supply in circulation.

Not applicable

PONS is a fungible and transferable ERC-20 crypto-asset deployed on Robinhood Chain at contract address 0x39dBED3a2bd333467115dE45665cC57F813C4571. The token has a total supply of 1,000,000,000 PONS and uses 18 decimal places.

Pons

https://www.ponsfamily.com/launchpad

2026-09-30

2026-09-29

Not applicable

English

HW5V1GSQ7

F5V1Z6TC2

FALSE

TRUE

TRUE

Not applicable. Holders of the PONS crypto-asset do not, solely by acquiring or holding PONS, acquire any ownership, equity, profit participation, repayment, redemption or compensation rights against Pons Labs, LLC or any other natural or legal person. Holding PONS does not give rise to contractual claims or entitlements against Pons Labs, LLC or any other natural or legal person.

Accordingly, the functionalities associated with PONS are functional and protocol-based. These include the ability to hold, transfer and trade PONS on Robinhood Chain and the token’s interaction with the pons protocol’s buyback and burn mechanism. These functionalities are further described in F.2.

Not applicable as the asset confers no ownership or financial claims and does not impose any legal obligations.

Not applicable as the asset confers no ownership or financial claims and does not impose any legal obligations.

Not applicable

FALSE

Not applicable

TRUE

Not applicable

Not applicable

FALSE

Not applicable

FALSE

Not applicable

FALSE

Not applicable

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.

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/A as DTI is provided in F.13

Networking, transport and session

Robinhood Chain exposes standard JSON-RPC and WebSocket interfaces, a public sequencer feed, and a direct sequencer endpoint, alongside managed infrastructure from providers such as Alchemy, QuickNode, Blockdaemon, dRPC, Validation Cloud and Chainstack. A transaction submitted through any of these routes reaches the Robinhood Chain sequencer, which determines ordering.

As a fallback route that limits the sequencer's ability to exclude transactions, Arbitrum Nitro chains including Robinhood Chain also accept submissions directly to the Delayed Inbox contract on Ethereum. A functioning sequencer typically incorporates a delayed-inbox transaction within about ten minutes; if it does not, any network participant can force the transaction's inclusion after a 24-hour delay.

At Ethereum, the settlement and data-availability layer beneath Robinhood Chain, execution clients communicate over the DevP2P/RLPx protocol stack.

Serialisation

Batches of ordered transactions are compressed with the Brotli algorithm, at a compression level that adjusts dynamically between 0 and 11 depending on network congestion, before being posted to Ethereum. Robinhood Chain's default posting method is a blob transaction under EIP-4844 and calldata transactions serve as a fallback if blobs are unavailable or their price rises. Ethereum's execution layer separately uses Recursive Length Prefix (RLP) encoding for its own object serialisation.

Cryptography and key formats

Ethereum's execution environment operates on 256-bit words, with Keccak-256 hashing and secp256k1 signatures as its principal cryptographic primitives, and commits state to a modified Merkle Patricia Trie. Arbitrum Nitro incorporates go-ethereum (Geth) for core execution and state handling specifically to preserve this Ethereum-compatible behaviour at Layer 2. No Robinhood Chain-specific signature scheme, wallet key-derivation standard, or address-checksum format exists independently of this EVM compatibility.

Ledger and execution model

Robinhood Chain's execution environment is fully EVM-compatible, contracts written in Solidity or Vyper deploy without modification. Its architecture separates transaction ordering (performed by the sequencer) from execution: once ordered, transactions are processed by a deterministic State Transition Function in which the Geth core executes standard EVM logic and an additional layer, ArbOS, handles Layer 2-specific functions such as fee accounting and cross-chain messaging. Determinism means that honest nodes given the same ordered input always reach the same resulting state. One material divergence from Ethereum mainnet is contract size: Robinhood Chain permits contracts up to 96 kilobytes, four times Ethereum's 24-kilobyte limit.

The deployed PONS contract exposes standard state-reading functions for balances, total supply, decimals, and its launch and liquidity parameters, alongside the transfer and approval functions described below.

Token standards

PONS exposes the conventional fungible-token interface: allowance, approve, balanceOf, transfer, transferFrom and totalSupply, together with name, symbol and decimals. Its reported name is "Pons", its symbol "PONS", and it uses 18 decimal places.

Transaction restrictions and compliance controls

PONS carried temporary anti-snipe limits at launch: a maximum transaction size of 220 basis points (2.2%) and a maximum wallet holding of 200 basis points (2%) of total supply, both expressed on-chain as maxTxBps and maxWalletBps and matched by absolute-amount equivalents (22,000,000 and 20,000,000 PONS respectively, consistent with the basis-point figures against the 1,000,000,000-token supply). These limits applied for 366 blocks from the launch block (25,526,166) and expired at block 25,526,532. Robinhood Chain has since progressed far beyond that block, so the restriction period has run its course and ordinary transfer and transferFrom behaviour now governs all holders. No permit-style off-chain approval mechanism (such as EIP-2612) is present in the exposed interface.

Separately, and at the network rather than the token level, Robinhood Chain applies sequencer-level sanctions screening: a transaction associated with a sanctioned address is excluded from sequencing and never processed, so it never appears in the resulting state, while ordinary read operations remain unaffected.

The deployed contract also exposes a write function, setInitialBuyRecipient, that remains present in its callable interface. It is not established whether this function is now restricted to a specific caller, was disabled after launch, or remains generally callable.

External APIs and client access

PONS state and transaction history can be read through Robinhood Chain's standard JSON-RPC and WebSocket endpoints, its public sequencer feed, and Ethereum-style net, web3 and eth namespaces exposed by full nodes, including eth_syncing for sync status. Public endpoints are rate-limited and production use is expected to go through a managed provider. Any EVM-compatible wallet or application tooling (Hardhat, Foundry, ethers.js, viem, Wagmi) connects to PONS the same way it would to any other Robinhood Chain contract.

Implementation and deployment

PONS is a fixed-supply ERC-20-equivalent token contract paired with a Uniswap V3 liquidity position, both created in a single transaction (0x1f54f25fec2d963dcb338ecb8b46a6eb123198a5c7a746d34cb2dbe78d074af8) that interacted with the legacy launch factory. That transaction minted the full 1,000,000,000 PONS supply, minted Uniswap V3 position NFT 109216, and seeded the position with 0.1 WETH. It reached soft confirmation on Robinhood Chain and was subsequently posted to and confirmed on Ethereum. The resulting liquidity pool sits at 0x10CC6BD38112cAc182db90B6a71d8Bb5939526bA, a verified UniswapV3Pool contract charging a 1% fee, pairing PONS against Robinhood Chain WETH (0x0Bd7D308f8E1639FAb988df18A8011f41EAcAD73). The pool was created through the Uniswap V3 factory at 0x1f7d7550B1b028f7571E69A784071F0205FD2EfA and its position is held under the Uniswap V3 Positions NFT contract at 0x73991a25C818Bf1f1128dEAaB1492D45638DE0D3, none of which are operated by Robinhood, the PONS deployer, or any party identified in the evidence reviewed.

Runtime and build parameters

Robinhood Chain currently runs Arbitrum Nitro under ArbOS 61, using an Offchain Labs Nitro node image (offchainlabs/nitro-node, version 3.11.2). Robinhood Chain's own runtime is independently confirmed, as above. The compiler version and build settings specific to the PONS contract itself are not independently confirmed, because PONS was deployed through a legacy factory that predates the launchpad's current, actively-maintained factory and its published source, and no separate source-verification record for the legacy deployment was located in this review.

Dependencies

PONS depends operationally on Robinhood Chain for execution and settlement, and on its Uniswap V3 pool for its only known market. The specific open-source libraries compiled into the legacy PONS contract are not independently confirmed, for the reason given directly above. This reflects a gap in the legacy deployment's own published source, not in Robinhood Chain.

Data availability

Robinhood Chain's data-availability mechanism is described once, in H.2 Serialisation, and applies to PONS transactions without further token-specific detail.

Robinhood Chain orders transactions on a first-come, first-served basis determined by arrival at the sequencer. A higher fee does not secure earlier inclusion. A transaction reaches soft confirmation, sub-second, once the sequencer accepts and returns a receipt for it. The sequencer then batches and posts transactions to Ethereum, typically within minutes, after which their order can only change if Ethereum itself reorganises; full hard finality follows roughly 13 minutes after posting, once the relevant Ethereum block is itself final. Moving PONS from Robinhood Chain back to Ethereum through the canonical bridge is a separate matter from transaction finality: withdrawals are subject to an additional seven-day challenge period required by Arbitrum's fraud-proof design.

Disputes over the correctness of posted state are resolved through BoLD (Bounded Liquidity Delay). Arbitrum's own generic description of BoLD presents it as supporting permissionless validation by any participant, but Robinhood Chain's specific deployment departs from that default: it is secured by a permissioned validator set, currently two validators operated by Offchain Labs and Alchemy, and operating a validator requires allowlisting plus a 1 WETH bond. This chain-specific configuration, rather than the generic protocol description, governs the network PONS is deployed on.

Beneath this, Ethereum itself runs proof-of-stake consensus: validators stake 32 ETH, blocks are proposed in 12-second slots across 32-slot epochs, and a checkpoint reaching votes from at least two-thirds of staked ETH can be justified and finalised under Casper FFG, combined with LMD-GHOST fork-choice under the Gasper protocol. Dishonest validator behaviour can be slashed. PONS does not require any separate relationship with an Ethereum validator; these mechanisms secure the settlement layer Robinhood Chain batches ultimately rely on.

Network-level fees

Every Robinhood Chain transaction fee bundles two components into a single ETH-denominated charge: an L2 execution fee for computation on Robinhood Chain, and an L1 data fee for the cost of posting that transaction's data to Ethereum, which varies with calldata size and Ethereum network conditions. Standard gas estimation accounts for both automatically. Because ordering is first-come, first-served rather than fee-based, paying a higher fee does not secure faster inclusion; it only affects execution and data-publication cost.

Protocol-level fees

The only protocol-level fee specific to PONS is the 1% swap fee charged by its Uniswap V3 pool, which is unrelated to and separate from Robinhood Chain gas. No token-contract-level transfer fee is exposed by the deployed interface.

Validator incentives

Robinhood Chain validators must be allowlisted and post a 1 WETH bond. No periodic reward schedule for them is disclosed in the sources reviewed. Separately, the party that posts a batch to Ethereum is reimbursed for that cost through the parent-chain fee component of ordinary transaction fees, via an adaptive pricing mechanism ArbOS maintains. At the Ethereum settlement layer, validators earn ETH rewards for honest participation and can be slashed for defined misconduct.

Governance and parameter change control

Robinhood Chain's protocol is governed by an eight-signer Security Council: Robinhood holds two seats, and one seat each is held by BitGo, Chainlink Labs, Fireblocks Trust Company, Offchain Labs, Paxos and Talos. Routine changes require six-of-eight approval and a seven-day on-chain timelock. Emergency changes bypass the timelock but require seven-of-eight approval. This governs the chain's protocol and ArbOS version, not PONS specifically.

FALSE

Not applicable

TRUE

Independent security firms, principally Trail of Bits and ConsenSys Diligence, have audited the Arbitrum Nitro node, core contracts, BoLD dispute system, sequencer, and successive ArbOS releases that Robinhood Chain runs on, including the ArbOS 60/61 release Robinhood Chain currently uses. No audit specific to the PONS token contract or its legacy launch factory has been located. The value “true” in field H.8 reflects audit coverage of the underlying Nitro/ArbOS technology only.

ConsenSys Diligence — Nitro Node & Core Contracts — 24 June 2022.

• Object: the Nitro node and core smart contracts forming Robinhood Chain's underlying optimistic-rollup stack (bridge, inbox, challenge manager, one-step-proof contracts, and the Rollup contract), reviewed over seven weeks (25 April–24 June 2022, 63 person-days) by two auditors.
• Results: 29 findings, comprising one critical, three major, seven medium, ten minor and eight unrated observations. The critical finding concerned unsafe default file and folder permissions in the validator's block-validation script writer, which could allow local privilege escalation through shell-command injection. The major findings included a front-runnable admin pause/unpause sequence that could let an invalid assertion be confirmed before a challenge could be raised, and a Bridge design gap that could permanently lock ETH sent with calldata to a non-contract Layer 1 address.
• Actions: one minor finding (a misleading code comment) was corrected before the report's publication, referenced against a specific Offchain Labs pull request; remediation status for the remaining findings is not established from the material reviewed.

Trail of Bits — Nitro External DA & Nitro Contracts v3.2.0 — 12 January 2026.

• Object: Nitro's external data-availability implementation and Nitro Contracts v3.2.0, covering integration behaviour for external data-availability providers and consistency between node behaviour and the challenge contracts, reviewed over four engineer-weeks by two consultants (9–19 December 2025).
• Results: four findings — one of undetermined severity (missing validation in a preimage-validation function), two low severity (missing sequencer-message length checks, and message-parsing behaviour), and one informational (blob-decoding error handling); Trail of Bits described the implementation as clear and thoughtful overall, with issues concentrated in edge cases and behavioural divergence between Nitro and the challenge contracts.
• Actions: Offchain Labs remediated all four findings — adding the missing preimage validation, introducing message-length checks before indexing, adding explanatory handling for blob-decode failures, and treating a failed certificate validation as an empty batch — and Trail of Bits marked every finding resolved following a fix review on 12 January 2026.

Trail of Bits — ArbOS 60 & 61 — 10 July 2026.

• Object: Arbitrum Nitro and the Offchain Labs go-ethereum fork, focused on the ArbOS 60 and 61 upgrades — the release Robinhood Chain currently runs — covering Nitro, Nitro Contracts, Arbitrum governance contracts, new Stylus program-fragment functionality and the multi-dimensional gas-pricing model, reviewed over roughly 24 engineer-weeks by two consultants, concluding with a review of the ArbOS 61 upgrade payload on 9 July 2026.
• Results: nine findings — one high severity (non-deterministic Go map iteration in multi-gas constraint precompiles that could return differently ordered data across nodes, a potential consensus failure) and eight informational findings, covering gas charged after a state read, inconsistent state-handle write protection, a possible panic after state finalisation, stale multi-dimensional base fees, gas-constraint validation bypasses, a fee-cap documentation mismatch, an inappropriately accepted resource weight, and saturating arithmetic that could defeat an initial-backlog cap.
• Actions: Trail of Bits recommended deterministic sorting of resource data and a project-wide ban on unordered map iteration in consensus-critical code for the high-severity finding, plus stronger validation, additional tests and documentation corrections for the informational findings; one informational finding (gas charged after a state read) is recorded as fixed by a specific pull request, but the report does not contain a consolidated fix-review table confirming all nine findings were resolved.

Trail of Bits — Nitro Node & Core Contracts, 1 of 2 — 14 March 2022.

• Object: the Nitro node, arbitrator/WAVM prover, go-ethereum fork and ArbOS, reviewed over 16 person-weeks by two consultants (10 January–11 March 2022).
• Results: 47 findings, comprising 12 high, 8 medium, 10 low, 13 informational and 4 undetermined severity. The high-severity findings centred on divergences between the Rust arbitrator and the on-chain one-step-proof contracts (an unchecked block-depth limit, inconsistent error-status ordering, missing branch-destination validation, and mismatched casting and out-of-bounds rules) that could, in combination, let a party prove an invalid state on-chain and improperly win a staked challenge; further high findings covered unchecked errors in ArbOS's ticket-opening and fee-cost paths that could crash nodes.
• Actions: not established from the material reviewed.

Trail of Bits — Nitro Node & Core Contracts, 2 of 2 — 10 October 2022.

• Object: the Arbitrum Classic-to-Nitro migration path, ArbOS's EVM and pricing logic, and AnyTrust data-availability handling, reviewed over 16 person-weeks by three consultants (5 July–19 August 2022).
• Results: 18 findings, comprising 3 high, 2 medium, 8 low, 4 informational and 1 undetermined severity. The high-severity findings covered two distinct ways a crafted message could panic an ArbOS or AnyTrust validator node (denial of service), extra per-transaction computation in the NUMBER/BLOCKHASH opcodes that lengthened block-creation time, and an incorrect internal calculation that fed a wrong value into the Layer 2 pricing model.
• Actions: not established from the material reviewed.

Trail of Bits — Arbitrum BoLD, initial audit (then "challenge protocol v2") — 2 August 2023.

• Object: the BoLD dispute architecture Robinhood Chain uses for validator disputes, including the on-chain edge-challenge contracts and the off-chain validator (edge tracker and challenge watcher), reviewed over 20 engineer-weeks by two consultants across March–June 2023.
• Results: 34 findings, comprising 8 high, 6 medium, 5 low, 13 informational and 2 undetermined severity. Most high-severity findings concerned the off-chain validator rather than the audited contracts themselves: front-running certain validator operations could stop honest edges from being tracked or deny service to a validator node, and errors in the cumulative-timer calculation could cause a validator to believe an edge was confirmable before it actually was. The auditors noted the off-chain system was still under active development during the review.
• Actions: several off-chain issues are recorded as remediated as development continued during the engagement; the auditors' broader recommendations (formal documentation of assertion creation and validator incentives, an incident-response plan, and expanded off-chain testing) were outstanding as of the report date. A dedicated follow-up engagement (below, 2 May 2024) covered fixes arising from this audit.

Trail of Bits — BoLD contract fixes from the August 2023 audit, and sequencer-inbox delay-buffer changes — 2 May 2024.

• Object: the updated BoLD timer logic (moved from top-down to bottom-up accounting), a new assertion-staking-pool contract, and the delay-buffer censorship-resistance feature added to the sequencer inbox, reviewed over roughly five engineer-weeks in April 2024.
• Results: 6 findings, comprising 1 low and 5 informational severity, with no medium, high, critical or undetermined findings; the auditors stated they did not uncover any serious issues. The low-severity finding was that the staking pool's deposit function did not block deposits once an assertion had already been staked or fully funded, which could let a later depositor's funds be used to refund an earlier depositor from a losing challenge.
• Actions: remediation was recommended for all six findings; no confirmation of a subsequent fix is established from the material reviewed.

Trail of Bits — Sequencer Liveness Review — 11 March 2025.

• Object: the core Sequencer code responsible for ordering and feeding transactions into ArbOS, reviewed over three engineer-weeks by two consultants (24 February–7 March 2025).
• Results: one low-severity finding: repeated, uncached reads of StateDB and ArbOS state when an optional per-transaction condition-checking feature is enabled could degrade Sequencer performance for all users, a denial-of-service risk tied to that specific configuration rather than to normal operation.
• Actions: caching was recommended as the fix; the report separately supplies a prototype fuzz test for the Sequencer. No confirmation of a subsequent fix is established from the material reviewed.

Market volatility and liquidity

PONS can lose all its value. Prices on the trading platform form without the safeguards used in regulated securities markets, and the platform does not guarantee market depth or liquidity for any crypto-asset, including PONS.

Transaction irreversibility

A trade executed on the trading platform is a book entry recorded in the platform's own systems. Once PONS is withdrawn to an external wallet, that withdrawal is broadcast to Robinhood Chain and is irreversible from that point; incorrect withdrawal details supplied by the holder are the holder's own responsibility, and the trading platform accepts no liability for a resulting loss.

Custody

The trading platform holds client PONS in an omnibus wallet alongside other clients' holdings, under its own crypto-asset custody authorisation. PONS held this way is legally segregated from the platform's own assets, but is not covered by any deposit-guarantee or investor-compensation scheme, and a holder bears a pro-rata share of any shortfall if a sub-custodian the platform uses becomes unable to meet its obligations. A holder may instead withdraw PONS to a self-hosted wallet, taking on responsibility for that wallet's own keys.

Reference-market restrictions (background).

PONS's only evidenced market outside the trading platform is a separate, non-EU launchpad interface, which excludes persons in the European Union, the United Kingdom, and a further list of sanctioned jurisdictions from using it. This does not affect access to PONS on the trading platform; it means that the only alternative on-chain market for PONS is not accessible to the audience this white paper is prepared for.

Delisting Risks

Bitstamp Europe S.A. might remove the token from trading in line with Bitstamp Markets Trading Rules.

Issuer identification

No issuer-specific financial, governance or organisational information can accordingly be attributed to PONS beyond the deployment and platform facts set out here and in Part H.

Pons Labs as launchpad operator

The Pons platform's terms permit Pons Labs and its affiliates to hold, trade or feature tokens available through the platform without disclosing their own holdings, disclaim any fiduciary or advisory duty arising from that activity, and give Pons Labs broad, largely undisclosed discretion to restrict, suspend or terminate a user's access.

Legacy launch factory deployer

The address that called the legacy launch factory and received the resulting PONS supply and Uniswap V3 position is an externally owned account. No evidence reviewed for this white paper establishes the identity of the natural or legal person controlling that address, and nothing establishes that it is under Pons Labs's control.

Legacy administrative control

The deployed PONS contract still exposes a callable setInitialBuyRecipient write function and records the legacy launch factory as a contract address. It is not established who may call that function today, or whether the legacy factory or the contract that received the initial Uniswap V3 position carries freeze, pause, upgrade, withdrawal or fee-redirection powers.

Supply and burn mechanics

The deployed PONS contract reports a fixed total supply of 1,000,000,000 PONS. A transaction dated 15 July 2026 is recorded as transferring approximately 1,980,000 PONS, under 0.2% of total supply, to the conventional Ethereum-style dead address, and the token's own platform listing separately displays an active "burned" indicator for PONS. This demonstrates an actual, small reduction in economically accessible supply; it does not establish a mandatory or continuing obligation to execute further burns, and no burn schedule or mechanism is exposed in the deployed contract's interface.

Liquidity position concentration

The PONS launch transaction placed almost the entire original token supply into a single PONS/ETH 1% Uniswap V3 position. Execution quality is accordingly sensitive to the depth available in that specific position, rather than to liquidity spread across multiple independent pools.

Public ledger privacy

PONS activity takes place on a public blockchain. Wallet addresses, transaction hashes, balances and smart-contract interactions may remain permanently and publicly observable, the platform operator cannot edit, hide, reverse or delete information recorded on Robinhood Chain, and a wallet address may constitute personal information where it can be linked to an identifiable person.

Third-party infrastructure dependency (interface level).

The Pons interface itself relies on external wallets, remote procedure call services, indexers, explorers and other infrastructure providers to display data and prepare transactions. Failure, unavailability, inaccurate data, or a change in those services may impair the interface's ability to show current PONS state or prepare a transaction, independently of the underlying network's own operation.

Platform continuity and maintenance

The platform's terms give the operator unrestricted discretion to modify, suspend, restrict or discontinue the interface altogether, with no obligation to preserve off-chain data or continue operating any particular feature. If the interface were discontinued, PONS's public contracts would remain technically reachable, but the organised trading surface, price simulation, slippage controls and other tooling this section relies on would not.

Legacy liquidity-contract implementation uncertainty

The PONS launch transaction transferred the Uniswap V3 position representing PONS's launch liquidity from the legacy factory to a separate contract address. It is not established that the contract's withdrawal, ownership or fee-redirection permissions, limiting assurance over the administrative conditions applying to PONS's original liquidity position.

Smart-contract and protocol logic risk

PONS depends on smart-contract execution for token transfers and for interaction with its liquidity pool. Defects, vulnerabilities or unexpected behaviour in the token contract, the pool contracts, or the underlying Nitro/ArbOS stack could result in failed transactions, incorrect execution, or loss of value.

Sequencer availability risk

PONS inherits the availability characteristics of Robinhood Chain. Robinhood operates the sequencer and gives no guarantee of uptime; downtime, latency or unavailability may delay or, absent the forced-inclusion route described in Part H, prevent inclusion of a PONS transaction.

Layer 2 governance and validator concentration

Robinhood Chain's protocol governance is exercised by an eight-member Security Council, and its BoLD dispute-resolution system currently uses two permissioned validators. Concentration of governance and validation functions among a limited number of parties creates dependency on their continued availability, key security and correct operation.

Ethereum data availability and Layer 1 dependency

Robinhood Chain uses Ethereum blobs for data availability and posts chain data to Ethereum. PONS therefore inherits a dependency on Ethereum execution and beacon infrastructure, and disruption to those services may impair node synchronisation, data retrieval or Layer 2 operation.
RPC, node and explorer dependency (protocol level). Independently of the Pons interface, submitting or observing a PONS transaction at the network level depends on RPC endpoints, the sequencer feed, full nodes and block explorers. Robinhood Chain's public RPC endpoints are rate-limited and operating an independent full node requires substantial local resources plus ongoing access to Ethereum execution and beacon endpoints.

DEX and pool dependency

PONS's evidenced market infrastructure is a PONS/ETH 1% Uniswap V3 pool created during the launch transaction. Disruption, defects, or reduced effective liquidity affecting that pool or its dependent contracts may impair PONS trading and execution quality without altering underlying PONS balances.

Quantum computing risk

PONS transfers, in common with ordinary Ethereum-style accounts, are authorised by ECDSA signatures over the secp256k1 curve. Once an address has sent a transaction, its public key is exposed on-chain; a sufficiently powerful quantum computer running Shor's algorithm could in principle derive the corresponding private key from that exposed public key and forge further signatures. No quantum computer available today is remotely close to this capability, and public estimates place a credible threat at the end of this decade at the earliest, with U.S. NIST guidance anticipating deprecation of ECDSA by 2030 and disallowance by 2035. This is a long-horizon, ecosystem-wide risk inherited from Ethereum's account model rather than one specific to PONS or Robinhood Chain, and no PONS-specific or Robinhood Chain-specific quantum-migration plan is evidenced.

Offer-related risks

• Custody: PONS held in custody is legally segregated from the trading platform's own assets under its crypto-asset-service-provider authorisation, so it does not form part of the platform's own estate if the platform becomes insolvent.

Crypto-asset-related risks

• Supply and burn mechanics: PONS supply and token movements are publicly observable through the deployed contract and the block explorer. The contract exposes a public total-supply reading, and both the original issuance and the recorded transfer to the dead address can be independently verified on-chain, reducing opacity around recorded supply movements.

Project implementation-related risks

• Third-party infrastructure dependency: Robinhood Chain supports multiple independent managed RPC providers, including Alchemy, QuickNode, Blockdaemon, dRPC and Validation Cloud, and permits operation of independent full nodes. This provider diversity and self-hosted node access reduce reliance on any single RPC service for network connectivity and state retrieval.

Technology-related risks

• Sequencer availability risk: Robinhood Chain, as an Arbitrum Nitro chain, accepts transactions submitted directly to Ethereum's Delayed Inbox as an alternative to the ordinary sequencer route; a well-functioning sequencer typically incorporates such a transaction within about ten minutes, and any participant can force its inclusion after 24 hours regardless of sequencer cooperation. This limits, without eliminating, the practical effect of prolonged sequencer unavailability or censorship.
• Smart-contract and protocol logic risk: The underlying Nitro node, core rollup contracts, dispute system and successive ArbOS releases that Robinhood Chain runs on have undergone repeated independent security audits, most recently covering the ArbOS 60/61 release Robinhood Chain currently uses. This reduces, without eliminating, the risk of a defect in the shared Layer 2 technology; it does not extend to the PONS token contract itself, for which no dedicated audit is evidenced.
• DEX and pool dependency: The PONS/ETH liquidity pool is deployed through the standard, immutable Uniswap V3 factory and pool contracts, shown as independently verified on the Robinhood Chain block explorer, rather than through bespoke or unverified automated-market-maker code specific to PONS.
• Quantum computing risk: The Ethereum Foundation has an active, NIST-aligned post-quantum research and migration programme targeting completion of core post-quantum infrastructure by approximately 2029, including an account-abstraction path that would let individual accounts adopt quantum-safe signatures without a single protocol-wide cutover. This mitigation sits at the Ethereum settlement layer that Robinhood Chain, and therefore PONS, inherits; it is not yet complete, and no Robinhood Chain, or PONS-specific migration plan is evidenced.

Bitstamp Europe S.A.

549300XIBGTJ0PLIEO72

PONS

Robinhood Chain orders transactions on a first-come, first-served basis determined by arrival at the sequencer. A higher fee does not secure earlier inclusion. A transaction reaches soft confirmation, sub-second, once the sequencer accepts and returns a receipt for it. The sequencer then batches and posts transactions to Ethereum, typically within minutes, after which their order can only change if Ethereum itself reorganises; full hard finality follows roughly 13 minutes after posting, once the relevant Ethereum block is itself final. Moving PONS from Robinhood Chain back to Ethereum through the canonical bridge is a separate matter from transaction finality: withdrawals are subject to an additional seven-day challenge period required by Arbitrum's fraud-proof design.

Disputes over the correctness of posted state are resolved through BoLD (Bounded Liquidity Delay). Arbitrum's own generic description of BoLD presents it as supporting permissionless validation by any participant, but Robinhood Chain's specific deployment departs from that default: it is secured by a permissioned validator set, currently two validators operated by Offchain Labs and Alchemy, and operating a validator requires allowlisting plus a 1 WETH bond. This chain-specific configuration, rather than the generic protocol description, governs the network PONS is deployed on.

Beneath this, Ethereum itself runs proof-of-stake consensus: validators stake 32 ETH, blocks are proposed in 12-second slots across 32-slot epochs, and a checkpoint reaching votes from at least two-thirds of staked ETH can be justified and finalised under Casper FFG, combined with LMD-GHOST fork-choice under the Gasper protocol. Dishonest validator behaviour can be slashed. PONS does not require any separate relationship with an Ethereum validator; these mechanisms secure the settlement layer Robinhood Chain batches ultimately rely on.

See H.5

2026-07-13

2026-08-27

Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5).
Full methodology available at : https://www.micacryptoalliance.com/methodologies/esg

Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5).
Full methodology available at: https://www.micacryptoalliance.com/methodologies/esg

Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5).
Full methodology available at: https://www.micacryptoalliance.com/methodologies/esg

Land use: 0.00181 m²

Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5).
Full methodology available at: https://www.micacryptoalliance.com/methodologies/esg

Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5).
Full methodology available at: https://www.micacryptoalliance.com/methodologies/esg

Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5).Estimates on individual node weight, hazardous components and depreciation rate are used.
Full methodology available at: https://www.micacryptoalliance.com/methodologies/esg

Data provided by the MiCA Crypto Alliance as a third party, with no deviations from the calculation guidance of Commission Delegated Regulation (EU) 2025/422, Article 6(5). Usage of natural resources is approximated through land use metrics. Land use, water use and water recycling are calculated based on energy mix-specific estimates of purchased electricity land intensity, purchased electricity water intensity, and water recycling rates. Full methodology available at: https://www.micacryptoalliance.com/methodologies/esg