> For the complete documentation index, see [llms.txt](https://armorfi.gitbook.io/armor/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://armorfi.gitbook.io/armor/features-and-highlights/one-stop-protocol-cover-shop.md). # Coverage Solutions Aggregator The Armor network coverage is underwritten by Nexus Mutual. We will add support for other coverage products in the future as the market matures. ### Fully collateralized Coverage Nexus Mutual has a stringent risk policy with a proven track record and deep capital pool availability to ensure that user funds are always fully collateralized, and the full amount of claims can be paid. ### Chain-verified claims process When a claim is submitted to Armor, it will trigger a review process where withdrawals are limited and governance will investigate and determine whether or not a claimable hack took place. If a hack has occurred and user funds are affected, then governance may proceed to submit the claim to Nexus Mutual’s claims process. Armor token holders will also participate in Nexus Mutual’s process for claim approvals and payouts as a proxy mechanism for the NXM delegated to the ArNXM vault. When a payout is confirmed, they will be received to Armor’s payout treasury then distributed to an airdrop faucet for affected recipients to claim their payout from. --- # 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://armorfi.gitbook.io/armor/features-and-highlights/one-stop-protocol-cover-shop.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.