# FDRY Token Disclosure This page exists so the asset is accurately described. It is a neutral disclosure, not a promotion, and that framing is intentional. ## What FDRY is, in one paragraph FDRY is the optional coordination asset described in the Unbrowse Maintenance Network paper. Its role is deliberately narrow: economically accountable participation in higher-trust route maintenance, bonding, and dispute resolution, and only if and when the route graph matures enough to need that. It is not a payment token for ordinary route usage, not a governance wrapper, not a ranking token, and not a claim of ownership over the graph. The paper is explicit that the product wedge works with no native asset at all, and that nothing in Unbrowse depends on forcing FDRY into the story early. ## You do not need FDRY to use Unbrowse Ordinary route access is settled in stable-denominated terms. A user never has to hold FDRY, price anything in token units, or think about it to resolve and execute routes. If FDRY is irrelevant to your use of Unbrowse, that is the expected default, not a gap. ## Token specifics are not published here Network, contract, and acquisition details are intentionally not listed on this page. The maintenance layer that would give the asset a function is sequenced after the wedge, so publishing token specifics now would put the narrative ahead of the system, which is the opposite of how the paper says this should be approached. Specifics will be disclosed through an official channel if and when that layer is live. Treat any contract address attributed to FDRY that does not come from an official Unbrowse channel as unverified. ## Not financial advice Nothing here is investment advice, an offer, or a solicitation. This page describes a system component for completeness. For the reasoning behind the asset's narrow role, read [Accountable Bonding and Where FDRY Fits](/concepts/accountable-bonding.md) and the Maintenance Network paper. A fuller version of that paper is being prepared for release. --- # Agent Instructions: 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: ``` GET https://docs.unbrowse.ai/reference/fdry.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.