# Networks and assets

Supported networks and asset types

Splits supports some networks fully (all features available) and a longer tail partially (balances and sending work; accounting history, swaps, bridging, and NFTs may not be available). Owners turn networks on and off per workspace in [Settings > Networks](https://app.splits.org/settings/team/networks/) (see [Settings](https://splits.org/docs/workspaces/settings)). Any listed network can be enabled, regardless of tier; **balances are shown for enabled networks only**.

Enabled networks are kept in sync: an account has the same address, signers, threshold, and owner on all of them, because [signer changes are signed once for every active network](https://splits.org/docs/accounts/thresholds#changing-signers-and-thresholds). An account's state is synced to a newly enabled network before the account is used there; disabling a network requires nothing onchain.

Email support to request another network or asset type; most EVM-equivalent networks can be supported, pending our underlying providers.

## Fully supported networks

Every feature works on these networks:

* Ethereum Mainnet
* Base
* Optimism
* Arbitrum
* Celo
* World Chain
* Tempo
* Polygon (PoS)
* BNB Smart Chain
* HyperEVM
* Robinhood Chain

## Partially supported networks

On partially supported networks, you can manage balances, send funds, swap, and bridge assets. Transaction history and accounting are not available. NFT management is available only on Zora.

* Linea
* Zora
* Monad
* MegaETH
* Scroll

## Sending to other networks

Tokens can be bridged and sent to an external address on Solana and any EVM [Relay network](https://docs.relay.link/references/api/api_resources/supported-chains); see [Swaps](https://splits.org/docs/transactions/swaps).

## Recovering assets from unsupported networks

A Splits account can be reconstructed at the same address on an unsupported EVM network, then used to bridge stranded assets to a supported network.

Prerequisites: an RPC for the unsupported network, the account's original creation parameters, and access to enough [recovery signers](https://splits.org/docs/workspaces/recovery#recovery-signers) to meet the recovery threshold.

1. Reconstruct the canonical factory deployment and account creation calls from the Splits contracts and the account's original configuration.
2. Simulate the calls. Confirm the predicted account addresses exactly match the Root, Treasury, and stranded account addresses. **Stop if any address differs.**
3. Deploy the canonical factory contracts, then the Root, Treasury, and stranded account in ownership order.
4. Use the recovery signers to authorize a transaction from the stranded account that bridges its assets to a supported network.
5. Verify the bridge receipt and destination-chain transfer. Activity on the unsupported network does not appear in Splits transaction history or accounting.

## Browser extension and WalletConnect

The [browser extension](https://splits.org/docs/introduction/extension) and in-app [WalletConnect](https://splits.org/docs/integrations/walletconnect) work on any enabled network, regardless of tier.

## Supported assets

* Native tokens (e.g. ETH)
* ERC-20
* ERC-721
* ERC-1155

All supported assets work on all fully supported networks. If you send an unsupported asset to a Splits account, contact us and we will attempt to make it recoverable.

## Programmatic access

Via the [Splits CLI / MCP](https://splits.org/docs/introduction/agents):

* `splits chains list`: every listed network with its tier and per-feature capability flags (**Read** scope)
* `splits chains get --chainId 8453`: one network's entry (**Read** scope)

The underlying endpoint is `GET /public/v1/chains` (API key with **Read** scope); see [Use the API](https://splits.org/docs/introduction/agents#use-the-api). Networks in gradual rollout are excluded until fully rolled out.