Set up a chain for Vela
Vela runs on any EVM chain that has twelve known contracts and one precompile. Enter a chain and this page will tell you which of those it has, which it lacks, and who can put them there. Two of the twelve are needed only by a wallet holding more than one passkey; the list says which.
Names, IDs and gas-coin symbols are looked up in the chain directory. An RPC URL is used as given, so this works for a private or local chain too.
What this page checks, and why
Why these twelve contracts?
They are the exact set the wallet itself checks before it lets you add a network: the account contract and its factory, the ERC-4337 EntryPoint and Safe’s module for it, the passkey signer, the two CREATE2 factories everything else is deployed through, and the passkey signer factory a wallet with more than one key needs. The list on this page is read from the wallet’s source, so the two cannot disagree.
Why is the same address used on every chain?
Every contract here is deployed to a deterministic address — either a keyless transaction whose sender is fixed, or CREATE2 through a factory. Because the addresses are the same everywhere, a Vela account has the same address on every chain, and a passkey created once works on all of them.
Why can’t the P-256 precompile be deployed?
The verifier’s address, 0x100, is written into the setup data every Vela address is derived from. Pointing at a verifier contract somewhere else would change every address on every chain, for everyone. So a chain either has the P-256 precompile (EIP-7951 / RIP-7212) or Vela cannot run on it — and only the chain’s operators can change that.
Is the gas I send refundable?
For the two keyless deployments, no: their sender has no owner, and the pre-signed transaction spends a fixed fee. Send exactly what the step says. For the throwaway deployer, yes — sweep the leftover back to yourself when you are done.