> For the complete documentation index, see [llms.txt](https://bridgem.gitbook.io/bridgem-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bridgem.gitbook.io/bridgem-1/introduction/highlights.md). # HighLights ***The first cross-chain bridge focused on BTC and ETH L2 networks*** Pioneering Cross-Chain Connectivity: BridgeM facilitates bidirectional transfer of assets between Bitcoin and Ethereum networks, enhancing liquidity and fostering mutual ecosystem growth. ***Scalability and Security*** BridgeM is built to scale, with plans to extend additional ETH Layer2 networks like Arbitrum and Optimism, ensuring compatibility and openness for future expansion. Furthermore, BridgeM incorporates multiple third-party infrastructures and funds as validator nodes for the cross-chain bridge, thereby enhancing its security. ***BridgeM's Mission of Integration*** BridgeM's core mission is to swiftly and securely integrate the Bitcoin ecosystem with the Ethereum ecosystem, enabling ERC20 assets to thrive within the Bitcoin ecosystem and vice versa, fostering collaboration and investment diversity. ***Offical Link*** Website: [https://bridgem.io](https://bridgem.io/) Twitter: --- # 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://bridgem.gitbook.io/bridgem-1/introduction/highlights.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.