> For the complete documentation index, see [llms.txt](https://docs.brightunion.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brightunion.io/buying-coverage/chains-multi-chain.md). # Chains, multi chain Bright Union app implements the concept of [Global Risk Chain](https://brightunion.io/blog/risk-chain.html) introduced by the team in 2024. The concept enables multiple use cases, and first of them - allowing sales of DeFi covers cross multiple EVMs. Regardless of where the cover is purchased, it will be: * fulfilled on the chain where the underwriting capital pool is located * the cover will protect the user's wallet against risks on **all** EVMs Example: *Vitalik has purchased a cover protecting his $500k investments on Aave V3, Balancer V4 and Hyperliquid, for 90 days. He's purchased it on Gnosis chain, paying $500 Gnosis USDs. From that moment he is 100% covered on **every** EVM where these protocols exist. Under the hood, the underwriting capital ($500k) actually resides on Ethereum, and that's where the cover was fulfilled.* --- # 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://docs.brightunion.io/buying-coverage/chains-multi-chain.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.