> 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/the-afterbell-thesis.md). # The AFTERBELL Thesis The core thesis behind outcome markets for price and event expectations. The AFTERBELL thesis begins with a practical observation: a market close is a trading schedule, not an end to uncertainty. Earnings are released. News develops. Products launch. Global markets move. Participants form new expectations about prices and events. The regular stock session may be closed, but the question remains open. **The bell never rings.** AFTERBELL is designed to turn those questions into explicit prediction markets for stock-token outcomes. ### From a question to a redeemable outcome The proposed product flow is deliberately simple: ``` Question → Market → Yes / No → Market-implied expectation → Resolution → Redemption ``` Each stage has a distinct purpose. A question defines what is being tested. A market lets participants take opposing positions. Yes and No prices express the terms at which those positions trade. Resolution determines which outcome is correct. The winning outcome can then be redeemed. This format is intended to make a view concrete. Instead of beginning with an instrument and inferring what it represents, a participant begins with the proposition itself. “Will NVDA close above $150 on Friday?” is understandable before any trade occurs. The market then gives that proposition a price. The thesis does not depend on claiming that markets can remove uncertainty. They cannot. It depends on making uncertainty tradable in a precise form. ### Build around the relevant asset infrastructure AFTERBELL is designed around stock tokens in the Robinhood Chain ecosystem. The source references stock tokens such as NVDA, TSLA, and AAPL, with USDG as the settlement asset. These are ecosystem components that AFTERBELL proposes to use, not components it claims to have created. This choice keeps the product focused. The intended question is not an abstract forecast about any topic. It is a defined outcome connected to an asset or event that participants already follow. The settlement asset and tokenized outcomes provide a path from market participation to a final redemption result. The market types described by the source reflect the same focus. They include weekly closes, earnings, pre-market and after-hours conditions, and 24/7 crypto markets. Each is a different way of expressing a time-bound question. The detailed design of those markets belongs in the Market Design section. ### Use a trading model suited to binary outcomes AFTERBELL starts with a central limit order book rather than an automated market maker (AMM). This is a product decision shaped by the binary nature of prediction-market outcomes. At resolution, one outcome is worth $1.00 under the market terms and the other is worthless. The source argues that this structure is unfavorable for AMM liquidity providers, who can face a one-sided final result. An order book instead lets buyers and sellers state the prices at which they are willing to trade. The thesis is not that a CLOB eliminates liquidity challenges. It does not. Market depth must still be built, and the source recognizes that early markets may need liquidity bootstrapping. The choice is that an order book provides a more appropriate starting structure for the proposed binary markets. ### Verify an answer before settling Prediction markets are only as credible as their resolution. AFTERBELL therefore proposes a dual-source model: a Chainlink stock-token feed as the primary source and the Robinhood REST API as a cross-check. If those sources differ by more than 5%, the market pauses rather than resolving automatically. An administrator can manually resolve using off-chain evidence when needed. This approach is summarized by the source as **“trust, but verify, twice.”** That phrase also marks an important boundary. The proposed system is not described as completely trustless. It includes an administrative resolution path, and it depends on external data sources. The design preference is to stop when evidence materially conflicts, not to force an automated answer. ### A focused product thesis The thesis is not that every investor needs another trading venue. It is that some stock-related questions are naturally expressed as defined Yes or No outcomes, particularly when information continues to arrive outside ordinary stock-market hours. AFTERBELL proposes to serve those questions with: * Stock-token markets on Robinhood Chain. * USDG settlement. * Order-book trading for opposing binary positions. * Verified resolution with a pause on material source disagreement. The product remains under development. It has no token, its smart contracts are not yet audited, and its future liquidity, adoption, and revenue are not proven. These constraints are central to evaluating the thesis. The following sections examine whether the proposed market, resolution, and technical choices can support it in practice. --- # 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/the-afterbell-thesis.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.