> For the complete documentation index, see [llms.txt](https://rooter-3.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rooter-3.gitbook.io/whitepaper/the-90-days.md). # The 90 days A person has 90 days from a coin's birth to claim it. What happens at the end of the window is the clearest difference between Rooter and what came before. ## If the person has claimed Nothing changes. The window is irrelevant. Their share is theirs from the block they claimed, forever. ## If the person has not claimed Anyone can call `sweep()`. The escrow that accrued under the account during the window is paid into the coin's Rooter Pool and distributed to holders exactly as fee is. Then the window resets and escrow begins accruing for the person again. A person who claims on day 200 gets everything from day 91 onward. What they did not collect in the first 90 days went to the people who held the coin while they were absent. ## Why not burn it The incumbent model uses unclaimed fees to buy the coin back and burn it. That helps every holder a little, in proportion to supply, and helps nobody in particular. A sweep pays the same value to the specific wallets that held the coin during the specific window in which the person did not turn up. They are the reason there was a market at all. Rooter pays them. ## What sweep cannot do It cannot run early. It cannot pay anyone but the coin's own Rooter Pool. It cannot touch escrow of an account that has claimed. And because it is public, nobody has to trust Rooter to trigger it. --- # 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://rooter-3.gitbook.io/whitepaper/the-90-days.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.