# Getting Started Bool Network Testnet has achieved its first target of supporting all EVM-compatible blockchains including prominent L1s and L2s. For testing purposes, [primary contracts](/evm-ecosystem/technical-reference/deployment-addresses.md) are deployed onto [a selection of EVM blockchains](/evm-ecosystem/technical-reference/chain-ids.md) to enable developers to design and modify their omnichain protocols on top of Bool Network. However, supporting EVM blockchains is far from demonstrating the comprehensive features of Bool Network. Based on its innovative design, Bool Network is capable and robust to support cross-chain message transmission across heterogeneous blockchains. Bool Network's development team is progressively working on supporting more on-EVM blockchains and stay tuned! The outline of developing an omnichain protocol is as follows: * Configure JSON-RPC providers for the chains your protocol plans to support (or running your own nodes). * Request testing tokens from different [Faucet](/evm-ecosystem/technical-reference/faucet.md). * Construct an AMT bridge through Bool Scan and detailed instructions are given [here](/evm-ecosystem/amt-bridges.md). * [Integrate ](/evm-ecosystem/amt-bridges/bind-consumer-to-anchor.md)your smart contracts with chain-specific anchors on each blockchain. * Test your protocol functionalities and monitor the status of each cross-chain message on [BoolScan](https://boolscan.com/bridge/?network=testnet). An [example](/evm-ecosystem/application-examples/helloweb3.sol.md) has been given. * Remember to keep in touch with the [Bool Network team](https://t.me/BOOLDevCamp) since they are always there to help. --- # 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.bool.network/evm-ecosystem/getting-started.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.