> 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/introduction/overview.md). # Overview A concise introduction to AFTERBELL and the market experience it is designed to provide. AFTERBELL is a proposed prediction-market product for stock-token outcomes. It is designed for a simple question: when a trader has a view on a stock-related outcome, can that view become a clear, tradable Yes or No position? The product is designed around markets that remain relevant outside traditional equity-market hours. A stock exchange may close, but earnings releases, product news, global developments, and investor expectations continue. AFTERBELL’s position is direct: **the bell never rings.** ### A market for a defined question A prediction market turns a specific future outcome into tradable positions. Rather than buying an asset outright, a participant chooses between two outcomes: * **Yes** — the stated condition will occur. * **No** — the stated condition will not occur. For example, a market could ask: > Will NVDA close above $150 on Friday? If a Yes position trades at $0.72 and a No position trades at $0.28, those prices express the market’s current expectation of the outcome. The price is not a guarantee. It is the price at which participants are willing to take the opposing sides of a defined question. If NVDA closes at $152 under the market’s resolution terms, the Yes outcome wins. A Yes share purchased for $0.72 becomes redeemable for $1.00. In that example, the difference is $0.28 before applicable fees. The losing No outcome has no redemption value. This structure makes the trade legible. The participant does not need to infer how a range of prices, expiries, or contract terms maps to a view. They select the outcome they believe will resolve. ### Designed around stock tokens AFTERBELL is designed for stock-token markets in the Robinhood Chain ecosystem. The referenced infrastructure includes stock tokens such as NVDA, TSLA, and AAPL; USDG for settlement; and Chainlink price feeds. AFTERBELL does not create those underlying components. Its proposed role is to build a prediction-market product on top of them. The market questions can concern price levels, weekly closes, earnings events, and other defined outcomes. The broader product direction also includes 24/7 crypto markets and markets for pre-market and after-hours conditions. Each market must state its condition and resolution basis clearly. The detailed market catalogue and lifecycle appear later in this documentation. ### From question to redemption At a high level, a participant: 1. Selects a market with a defined condition and resolution time. 2. Buys Yes or No at an available price. 3. Holds, trades, or closes the position before resolution. 4. Redeems the winning outcome after the market resolves. The proposed system uses an off-chain central limit order book (CLOB) to match orders. When appropriate, new paired outcome shares can be minted from USDG. Smart contracts on Robinhood Chain hold settlement funds and issue ERC-1155 Yes and No outcome tokens. A participant signs an order in the browser without a gas fee for that signature step; the system then matches the order or follows the proposed minting path. These details describe the intended architecture, not a claim that the product is already live or audited. The dedicated architecture sections explain the proposed contracts, matching engine, and order lifecycle. ### Resolution requires verification The product depends on a credible answer to each market question. AFTERBELL’s proposed approach uses a Chainlink stock-token feed as the primary source and cross-checks it against the Robinhood REST API. If the two sources differ by more than 5%, automated resolution pauses. An administrator can manually resolve using off-chain evidence when required. That model is not presented as completely trustless. It is designed around the principle: **trust, but verify, twice.** The resolution process, its assumptions, and its limitations are examined in the Oracle & Resolution and Trust Model sections. {% hint style="warning" %} AFTERBELL is still being developed. Smart contracts are not yet audited, and an audit is planned before mainnet. Regulatory clarity for prediction markets involving securities also remains uncertain. {% endhint %} ### What AFTERBELL is not AFTERBELL is a product concept and development effort. It does not currently have a token, and it is not a token launch. It should also not be understood as a promise of liquidity, adoption, or revenue. Future roadmaps and financial models remain targets and projections. They are not evidence of current market volume, trader activity, or proven product-market fit. The pages that follow explain why this product exists, the gap it is designed to address, the thesis behind its design, and why the current infrastructure makes the concept practical to pursue. --- # 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/introduction/overview.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.