> For the complete documentation index, see [llms.txt](https://docs.uma.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uma.xyz/resources/network-addresses/new-network-requests.md). # New Network Requests The following are the evaluation criteria UMA considers when adding Optimistic Oracle support for a new network. UMA aims to support as many networks as possible to deliver the best experience for our integrating protocols and users. However, integrating a new network requires a significant investment. Therefore, the evaluation criteria were established to ensure that the benefits to UMA's integrating protocols and users outweigh the development, security, and operational costs of adding a new network. Please note that these requirements are subject to change as the EVM (Ethereum Virtual Machine) and Layer 2 ecosystem continue to evolve. Meeting these requirements is the initial step in our evaluation process and does not guarantee support. ### Non-Negotiable Criteria: **The below are a pre-requisite to any consideration:** * EVM-Compatible Network a canonical token and message bridge to mainnet * ≥ 2 or more Independent RPC Node Providers (without block range limits for log queries) * 30-Day Moving Average TVL on the network > $75M * Block Explorer with Etherscan-Compatible API, contract verification and ABI fetching * Availability of token mappings data source with Ethereum mainnet * Dedicated support channel containing technical members of the network with priority support commitment to advise on contract development and debug data quality * Subgraph support for testnet and mainnet * Wallet connector libraries support for testnet and mainnet ### Get in Touch with UMA * Drop a message in the [UMA Discord Server](https://discord.com/invite/jsb9XQJ) * Send an email to --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.uma.xyz/resources/network-addresses/new-network-requests.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.