> 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/why-now.md). # Why Now Why the current market and infrastructure environment supports AFTERBELL’s approach. AFTERBELL is being proposed at a point when several required components are referenced as available in the same ecosystem. The case for building now is not that success is assured. It is that the product no longer needs to begin by creating every underlying building block itself. The relevant question is whether existing infrastructure can support a focused prediction-market product for stock-token outcomes outside traditional market hours. ### The components are already identifiable The source identifies Robinhood Chain as the intended ecosystem and names three foundational components: * Stock tokens, including NVDA, TSLA, and AAPL. * USDG for settlement. * Chainlink price feeds. Each solves a different part of the proposed product. Stock tokens establish the assets around which markets can be framed. USDG provides the settlement asset. Price feeds provide an input to resolution. AFTERBELL’s proposed role is to combine these components into a product experience: select a defined question, trade Yes or No, and redeem the outcome after resolution. This is different from claiming ownership of the infrastructure. AFTERBELL does not claim to create the stock tokens, USDG, or Chainlink feeds. Its thesis is that a specialized prediction market can be built on top of them. ### Familiar questions meet a defined market format Stock participants already encounter directional questions. They ask whether a company will beat earnings, whether a price will cross a threshold, or whether a product announcement will change expectations. These questions remain intelligible even when the underlying equity market is closed. Prediction markets provide a familiar conceptual format for making those views explicit. The source references Polymarket as existing precedent for prediction-market products. AFTERBELL’s proposed specialization is stock-token outcomes on Robinhood Chain, rather than a claim to have created the prediction-market category. The combination matters because it narrows the product problem. A participant does not need to begin with a general-purpose forecasting system. They can begin with a stated stock-related outcome and choose Yes or No. A market price provides the current trading terms for that view. ### The proposed architecture matches the timing problem The central product premise is that information does not follow regular trading hours. Earnings can arrive after close. News can break over a weekend. Global developments can change expectations while conventional equity markets are unavailable. A product designed for 24/7 availability can address the timing mismatch directly. Its purpose is not to replace conventional stock trading. It is to provide a distinct format for defined outcome questions that remain relevant after the bell. At a high level, the proposed flow is simple: a user selects a market, signs an order, and buys Yes or No through an off-chain central limit order book. Smart contracts on Robinhood Chain are intended to hold USDG and issue ERC-1155 outcome tokens. A dual-source process then supports resolution. These are proposed architecture choices, not evidence of a deployed and audited system. ### Existing infrastructure does not remove product risk Availability of components is a reason to explore the product. It is not proof that the product will work. The source identifies several limitations: * Regulatory clarity for prediction markets involving securities is uncertain. * Organic liquidity is not guaranteed. * New markets may require liquidity bootstrapping. * Smart contracts are not yet audited; an audit is planned before mainnet. * Revenue models and roadmap targets are projections, not demonstrated results. Competition also remains material. The source identifies competition risk from HoodOptions and Polymarket. Existing products can validate interest in adjacent behaviors while also making differentiation and execution more difficult. AFTERBELL does not claim inevitable adoption, market dominance, or a guaranteed first-mover advantage. ### Why the timing is appropriate to test the thesis The current opportunity is a convergence of identifiable assets, a settlement mechanism, price-data infrastructure, and a product category with established precedent. These ingredients make it possible to test a narrower proposition: can stock-token questions become useful, liquid Yes or No markets outside traditional equity hours? The answer remains unproven. The roadmap’s targets for markets, TVL, and traders are future targets, not current achievements. Financial models are projections, not realized revenue. The project is still in development, and it has no token. What exists is a credible starting point for building and evaluating the product. The infrastructure referenced by the source provides the pieces. AFTERBELL is designed to assemble them into a specific market experience: prediction markets for stock tokens, available when the ordinary bell has already rung. --- # 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/why-now.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.