> For the complete documentation index, see [llms.txt](https://docs.bracket.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bracket.fi/product/brkteth/contract.md). # Contract ### brktETH's contract live on Ethereum Although our escrow contract was deployed on both Ethereum and Arbitrum networks, after brktETH is allocated, the **brktETH contract will live on Ethereum**. Technically, the escrow contract will call the brktETH contract to mint brktETH in exchange for its escrow collateral. The escrow contract will receive brktETH that can now be claimed by users, and the brktETH contract will have it's treasury funded with the assets that were previously in the escrow contract. Like other LST/LRTs, you will be able to bridge your tokens to other chains. However because the most common use case will be to invest in strategies within the Bracket Platform, we anticipate the vast majority of users will keep their brktETH on Ethereum. As we describe in the [Bracket Platform](/product/bracket-platform.md) section, Strategy managers will be able to bridge assets multi-chain to generate yield for their strategy depositors.\ \ **Address**: 0x6C8550167BbD06D4610a6A443eCbEd84Bd1AccD6 --- # 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.bracket.fi/product/brkteth/contract.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.