> 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/protocol-overview/what-afterbell-is.md). # What AFTERBELL Is Defines AFTERBELL as a prediction-market protocol for tradable market outcomes. AFTERBELL is a proposed prediction-market product for stock-token outcomes. It turns a defined future question into a market with two positions: **Yes** and **No**. The product is designed for questions that remain relevant when traditional stock markets are closed. An earnings release, weekend announcement, or global market movement can change expectations outside regular equity hours. AFTERBELL’s intended role is to give those expectations a clear market format: prediction markets for stock tokens, available 24/7. ### A market represents a question Every market begins with a condition that can be evaluated later. For example: > Will NVDA close above $150 on Friday? The market has two mutually exclusive outcomes. A participant buys Yes if they believe the condition will be met. They buy No if they believe it will not. The resulting positions are not shares of NVDA. They are outcome positions tied to this specific question. The price of each outcome reflects the terms at which participants are willing to trade. In the source example, Yes trades at $0.72 and No trades at $0.28. That can be read as the market expressing an approximate 72% implied expectation for Yes at that time. It is not an objective probability or a promise of the result. If NVDA closes at $152 under the market’s defined resolution condition, Yes wins. A Yes share purchased for $0.72 becomes redeemable for $1.00, producing a $0.28 difference before applicable fees. No becomes worthless. ### The product flow At a conceptual level, AFTERBELL follows this sequence: ``` Question → Yes / No positions → Trading → Resolution → Redemption ``` A user selects a market and signs an order without a gas fee for the signature step. The order enters an off-chain central limit order book (CLOB). The system can match compatible orders from participants or mint new paired shares from USDG. Smart contracts on Robinhood Chain hold USDG, issue ERC-1155 Yes and No outcome tokens, and settle markets. The CLOB is an intended trading model, not a claim that the product is already deployed. It is chosen because binary outcomes have a final one-sided result: when Yes wins, No is worthless, and vice versa. The dedicated Trading Architecture section explains the rationale and mechanics in depth. ### The surrounding infrastructure AFTERBELL is designed for the Robinhood Chain ecosystem. The source references stock tokens including NVDA, TSLA, and AAPL; USDG as the settlement asset; and Chainlink stock-token price feeds. These are infrastructure components AFTERBELL proposes to use. They are not created by AFTERBELL. The distinction between the layers is important: * The **prediction market** defines and trades a question. * The **stock-token ecosystem** provides the referenced assets. * **USDG** is the settlement asset. * The **resolution process** determines which outcome wins. Markets can cover weekly closes, earnings, pre-market and after-hours conditions, and 24/7 crypto outcomes. Each must define its condition and resolution basis clearly. ### Resolution is a verified process AFTERBELL proposes to use a Chainlink stock-token feed as the primary source and the Robinhood REST API as a cross-check. If the two sources differ by more than 5%, the market pauses. An administrator can manually resolve using off-chain evidence when needed. This model is not completely trustless. It depends on external data and includes an administrative path. The intended principle is “trust, but verify, twice.” {% hint style="warning" %} AFTERBELL remains in development. Smart contracts are not yet audited, organic liquidity is not guaranteed, and regulatory clarity around securities-related prediction markets is uncertain. AFTERBELL has no token. {% endhint %} --- # 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/protocol-overview/what-afterbell-is.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.