> For the complete documentation index, see [llms.txt](https://whitepaper.after-bell.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.after-bell.uk/risks-and-limitations/infrastructure-risk.md). # Infrastructure Risk Covers risks from networks, services, and dependencies used by the protocol. ### A hybrid system still depends on infrastructure AFTERBELL relies on Robinhood Chain, smart contracts, an off-chain CLOB, oracle infrastructure, a frontend, and an off-chain keeper. If a critical component is unavailable at the wrong time, market operations can be interrupted. An interruption does not imply every asset is lost or every protocol state disappears. The impact depends on the component and function involved: matching, settlement, resolution, or user interaction. ### Robinhood Chain and sequencer risk Robinhood Chain is a Layer-2. The source identifies a specific scenario: if the sequencer goes down during resolution, markets can get stuck. ``` Market reaches resolution ↓ Sequencer goes down ↓ Required on-chain transition cannot proceed normally ↓ Market can become stuck ``` Timing matters because a prediction market may reach its resolution point while the chain cannot process the required on-chain state change. Resolution can then be delayed. The source does not define the exact transaction mechanics. The documented response is to wait for the sequencer to return, then resolve manually. This is the source-supported response. It does not imply an alternate sequencer, emergency RPC, bridge, forced inclusion, L1 fallback, or automatic recovery. {% hint style="warning" %} A sequencer outage is primarily an availability or liveness risk. It can delay market operations without proving that funds are lost. {% endhint %} ### CLOB dependency The off-chain CLOB uses Node.js and WebSocket for normal order matching. It receives signed orders and matches compatible trading intent before `CTFExchange` settles activity on-chain. If the CLOB becomes unavailable, normal order matching can be impaired. This affects new trading activity. It does not mean already-settled on-chain outcome positions disappear or are automatically changed. The source does not define a database, cache, queue, cloud provider, load balancer, or recovery system. No infrastructure redundancy should be assumed. ### Oracle infrastructure Resolution uses the Chainlink Stock Token Feed as the primary input and the Robinhood REST API as the secondary cross-check. If either source is unavailable or inconsistent, resolution can be delayed or moved into the exception path. ``` Chainlink + Robinhood API ↓ comparison ≤5% → normal resolution >5% → pause → manual resolution ``` The 5% circuit breaker is the documented response to material disagreement. It is not a fallback feed or proof that either source is correct. ### Smart-contract security Smart contracts handle settlement and market logic. They are not yet audited, and an audit is planned before mainnet. Until then, the code is described as testnet-grade. This is a security limitation, distinct from availability. An audit may improve review before mainnet, but it does not guarantee security. The source does not identify specific vulnerabilities, so none are asserted here. ### Infrastructure dependency map | Component | Role | Failure scenario | Potential impact | | --------------- | ------------------------------ | ----------------------------------- | ----------------------------------- | | Robinhood Chain | On-chain execution | Chain or sequencer unavailable | Market operations can be delayed | | Sequencer | Layer-2 transaction sequencing | Goes down during resolution | Markets can become stuck | | CLOB | Order matching | Matching infrastructure unavailable | Normal trading can be impaired | | Chainlink | Primary price input | Feed unavailable or problematic | Resolution can be impaired | | Robinhood API | Cross-check | API unavailable or inconsistent | Verification path impaired | | Smart contracts | Settlement and market logic | Contract bug or failure | Protocol operations can be affected | ### Availability, security, and integrity Availability risk means the system cannot operate normally because a component is unavailable. A sequencer outage and a CLOB outage are availability risks. Security risk means a technical failure or vulnerability could cause incorrect or unsafe behavior. Unaudited contract code is a security limitation. Oracle inconsistency is a resolution-integrity risk. It affects the correctness of the external input used to determine redemption, which is why the circuit breaker pauses the market above the stated threshold. ### Current limitation AFTERBELL is still under development. Its infrastructure is not presented as failure-proof, and the source makes no uptime guarantee. This is whitepaper **v0.1, September 2026**. Revenue projections are not proven, organic liquidity is not guaranteed, and AFTERBELL has no current token. It is a product, not a token launch. ### Conclusion The on-chain architecture does not remove infrastructure dependency. It moves settlement and protocol state into smart contracts, while the complete product still depends on the underlying chain, sequencer, CLOB, oracle sources, frontend, and off-chain operations. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://whitepaper.after-bell.uk/risks-and-limitations/infrastructure-risk.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.