How do I connect ChainList to Lodol?

Authenticate ChainList once from your workspace and every action and trigger it supports becomes available to drop into a workflow. There is no glue code to write or maintain.

All integrations

ChainList

CryptocurrencyUtilities

Look up any EVM network from a workflow. ChainList is the public registry of close to three thousand Ethereum-compatible networks: search them by name, chain ID or currency, get the settings a wallet needs to add one, pull a working RPC endpoint with its operator's logging policy attached, turn a transaction hash or a wallet address into a block explorer link, find the faucets for a test network, and see which layer 2s roll up to which network and over which bridges. Endpoints ChainList lists but nothing can call (config-file templates, notes, bare hostnames) are left out, so every address that comes back is one you can use. Every action reads: nothing here changes anything. No account or API key is required.

Get Started Browse all integrations

6 actions

Actions

Steps your workflow can run in ChainList.

Find networksSearch the EVM networks ChainList publishes, or browse them ranked by how much value is locked on them. Search by name, short name, chain ID or currency symbol: 'arbitrum', 'matic' and '8453' all work. Each network comes back with its chain ID, its currency, a working RPC endpoint and its block explorer, so the next step can use it without a second lookup. Test networks are included and labelled.

Get network detailsGet everything ChainList holds about one network: its chain id in both decimal and hex, the coin gas is paid in, a working RPC endpoint, its block explorer, what it is built on and which bridges reach it. It also comes back with the five boxes a wallet's 'Add a network' form asks for, already filled in, so connecting a wallet is a copy rather than a hunt. Anything worth knowing first (a re-used chain id, a network still incubating) arrives as a warning rather than buried in a field.

Get RPC endpointsGet the RPC endpoints published for one network, each with what its operator says it does with your requests. HTTPS by default, because that is what most things can call; switch to WebSocket for a subscription. Narrow to the operators that log little or nothing when the traffic is someone's. Endpoints ChainList lists but nothing can call (config-file templates, notes, bare hostnames) are left out, so every address that comes back is one you can use.

Get block explorer linksTurn a transaction hash, a wallet address, a block number or a token contract into a link on the right block explorer for the network it is on: the link to put in the Slack message or the email. Leave the value empty to just list the explorers. Only explorers that promise a fixed link shape are linked into, so a link that comes back opens something rather than a 404, and a hash pasted where an address goes is caught here rather than at the explorer.

Get test network faucetsFind where to get test funds for a test network, so a deployment or a test run does not stall on an empty wallet. Give it your wallet address and the faucets that take one in their own address bar come back ready to open. Ask a live network and it says so, and names the test networks to ask instead rather than coming back empty.

List networks built on a networkList the layer 2s and shards that roll up to one network (the hundred or so built on Ethereum, the handful built on Base) each with the bridges that move funds between the two. Ask it about a layer 2 instead and it says what that one is built on, so the same step answers the question from either end.