> ## Documentation Index
> Fetch the complete documentation index at: https://docs.grapl.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Supported chains

> The local GRAPL deployment, candidate EVM networks and requirements for public support.

**Reviewed October 4, 2026. Only Anvil has a GRAPL deployment.** The direction is EVM networks with compatible Uniswap v4 and hooks, beyond the original Robinhood focus.

## Available environment

| Environment | Chain ID | GRAPL status |
| - | - | - |
| Anvil on HTTP loopback | 31337 | Local development and integration tests |
| Public mainnets and testnets | Network-specific | No GRAPL deployment published |

See the [local address snapshot](/reference/contracts). A Uniswap PoolManager deployment is infrastructure, not evidence that GRAPL is deployed on that network.

## Candidate networks

The networks below have v4 infrastructure listed by the [official Uniswap deployment directory](https://developers.uniswap.org/docs/protocols/v4/deployments), reviewed on the date above. They are candidates, not tested GRAPL production networks. Consult that directory for current upstream addresses and additional networks.

| Candidate | Chain ID | GRAPL deployment |
| - | - | - |
| Ethereum | 1 | None |
| Unichain | 130 | None |
| Optimism | 10 | None |
| Base | 8453 | None |
| Arbitrum One | 42161 | None |
| Polygon | 137 | None |
| Avalanche | 43114 | None |
| BNB Smart Chain | 56 | None |

**Robinhood Chain** remains an intended target. Its network configuration, chain ID and compatible v4 prerequisites have not been verified here. No address or partnership is implied.

## What qualifies a network for support?

<Steps>
  <Step title="Verify the execution environment">
    Confirm chain ID, token decimals, Cancun EVM compatibility and the
    network-specific v4 PoolManager code and interfaces. Do not assume upstream
    addresses match across chains.
  </Step>

  <Step title="Verify the GRAPL deployment">
    Check hook permission bits, router settlement, pools, fee/reward behavior
    and chain-specific integration or fork tests. Publish source commit,
    deployment transactions, block, verified contracts and role assignments.
  </Step>

  <Step title="Complete production dependencies">
    Choose and verify governance and secure randomness, replace the
    chain-31337-only game/oracle, approve economics and finish security review
    and monitoring.
  </Step>
</Steps>

## Multichain direction

```mermaid theme={null}
flowchart TD
  App[GRAPL app] --> ChainA[Independent deployment on chain A]
  App --> ChainB[Independent deployment on chain B]
  ChainA --> StateA[Local pools, GEM, roots and reserve]
  ChainB --> StateB[Local pools, GEM, roots and reserve]
```

This diagram describes a target model, not running cross-chain functionality. No bridge, messaging layer, cross-chain swap, unified GEM balance, global mint cap or cross-chain bag delivery exists. GRAPL supply representation and benefit portability require separate decisions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.