> For the complete documentation index, see [llms.txt](https://docs.0y.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.0y.world/trading/how-to-read-the-binance-settlement-proof.md). # How to Read the Binance Settlement Proof When a Fast Market settles, 0Y provides a Binance settlement proof link so you can independently verify the final price used to determine the result. This guide explains how to read the proof and identify the settlement price. ### What is the Settlement Proof? The settlement proof is a direct query to Binance's public API. It returns the 1-second candlestick (kline) data for the final second before the market closes. For example, if a market closes at 03:30:00 UTC, the settlement proof uses the 03:29:59 UTC candle. Its Close price represents the final traded price recorded during that second, immediately before the market closes. Because the data comes directly from Binance's public API, you can check the settlement price independently. An example link looks like this: ```json [[1792380599000,"82572.44000000","82572.45000000","82572.44000000","82572.44000000","0.05519000",1792380599999,"4557.17306360",4,"0.01000000","825.72450000","0"]] ``` ### What the Response Means The API returns one row of data containing several fields. Here's how to read it: | # | Field | Meaning | | -- | ---------------------- | ------------------------------------------------------------------------------------ | | 1 | Open time | When this 1-second candle started (in milliseconds) | | 2 | Open | Price of the first trade in this second | | 3 | High | Highest trade price in this second | | 4 | Low | Lowest trade price in this second | | 5 | Close | Price of the last trade in this second. This is the market’s final settlement price. | | 6 | Volume | Amount of BTC traded during this second | | 7 | Close time | When this 1-second candle ended | | 8 | Quote volume | Total USDT traded (price × size across all trades) | | 9 | Trades | Number of trades that happened in this second | | 10 | Taker buy volume | BTC bought by market buyers in this second | | 11 | Taker buy quote volume | USDT value of those market buys | | 12 | Ignore | Unused field, always returns 0 | ### Which value determines the result? The Close price (field 5) is the settlement price 0Y uses to determine the market result. In the example above, the Close price is $82,572.44. ### How to convert the timestamp The Open time (field 1) is a Unix timestamp in milliseconds. To convert it into a readable date and time: 1. Copy the Open time value, for example: 1792380599000. 2. Open a Unix timestamp converter, such as[ https://www.unixtimestamp.com/](https://www.unixtimestamp.com/). 3. Paste the timestamp and view the converted date and time in UTC. For this example, the candle starts at 2026-10-19 03:29:59 UTC. ### Example API response: \[\[1792380599000,"82572.44","82572.45","82572.44","82572.44","0.05519",1792380599999,"4557.17",4,"0.01","825.72","0"]] Reading this response: * Candle time: 2026-10-19 03:29:59 UTC * Open: $82,572.44 * High: $82,572.45 * Low: $82,572.44 * Close (settlement price): $82,572.44 * Number of trades: 4 ### Still have questions? Reach out to us via our Support chat on predict.0y.world. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.0y.world/trading/how-to-read-the-binance-settlement-proof.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.