> 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/market-design/weekly-close-markets.md). # Weekly Close Markets Covers markets based on an asset’s weekly closing price. Weekly close markets turn a stock-price condition at a defined weekly endpoint into a binary Yes/No question. They are designed around a specific closing-price event, rather than a general view that a stock may rise or fall at some point. ### A defined Friday condition The source example is: > Will NVDA close above $150 on Friday? This creates two outcomes. Yes represents the condition that NVDA closes above $150. No represents the condition that it does not. The stated resolution point is **Friday 4 PM EST**. That defined point is important. The market is not asking whether NVDA trades above $150 at any random moment during the week. It asks about the specified Friday close. A clear condition gives traders a common proposition and gives the resolution system a defined moment to evaluate. ### Participation before resolution ``` Question → Yes / No order → CLOB trading → Friday close → price verification → resolution → redemption ``` Participants select the market and choose Yes or No. Their signed orders enter the off-chain CLOB, where compatible orders can be matched. The source also permits new paired shares to be minted from USDG. The resulting positions are ERC-1155 outcome tokens, not ownership of NVDA itself. Trading activity occurs before the resolution point. The source does not specify exact market opening or closing mechanics, so this page does not assume them. What is specified is the distinction between the tradable period and the defined Friday-close resolution condition. ### Price and outcome Suppose Yes trades at $0.72 and No at $0.28. The Yes price can be read as an approximately 72% market-implied expectation at that time. It is neither a guarantee nor an objective probability. If NVDA closes at $152 on Friday, Yes wins. A Yes position purchased for $0.72 becomes redeemable for $1.00 under the stated model. The No outcome becomes worthless. The example difference between the Yes purchase price and redemption value is $0.28 before applicable fees. ### Resolution dependency Weekly-close markets depend directly on a reliable price at the defined endpoint. AFTERBELL proposes Chainlink Stock Token Feed as the primary source and the Robinhood REST API as an off-chain cross-check. If the sources differ by more than 5%, the market pauses and may require manual administrative resolution using off-chain evidence. The market therefore has a clear boundary but not an automatic guarantee of resolution. Oracle integrity, available liquidity, regulatory uncertainty, and unaudited contracts remain material limitations. AFTERBELL is still in development, and this market format is proposed product design rather than a proven live capability. --- # 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/market-design/weekly-close-markets.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.