Develop on Ethereum
Connect to MetaMask
Connect MetaMask
Highbury EVM is compatible with MetaMask, the most popular browser wallet.
Metamask config
To access Highbury EVM, you’ll first need to add Highbury’s network configuration in MetaMask:
Mainnet
- Network Name: Highbury EVM Co-Chain
- New RPC URL: https://highbury.furya.io
- Chain ID: 710
- Currency Symbol: FURY
- Explorer URL: https://explorer.furya.io
Verified Mainnet Contracts
- Wrapped Fury (WFURY):
0xc9A0A35D0f36808db5359A02dC77ebfc66c463d7
(view on explorer) - Multicall
0x72B03E9F2Df1CA70257fc23744FA03926B27CcAe
(view on explorer) - Multicall2
0x1287c80Bb3edd10bEAF1881B327F8A224AcA7df5
(view on explorer)
Testnet
- Network Name: Highbury EVM Testnet
- New RPC URL: https://evm.testnet.furya.io
- Chain ID: 710
- Currency Symbol: FURY
- Explorer URL: https://explorer.testnet.furya.io
Local
- Network Name: Localhost 8545
- New RPC URL: http://localhost:8545
- Chain ID: 4200
- Currency Symbol: FURY

MetaMask account
To send transactions from your account using MetaMask, import your Fury account to MetaMask via private key. You can do so by clicking on the profile picture image and then selecting ‘Import Account’. From the ‘Select Type’ dropdown, select ‘Private Key’.

It’s possible to generate your Fury EVM compatible private key using futool. From the futool
repository:
# Start a local dockerized fury blockchain
futool testnet bootstrap --fury.configTemplate evm
# Add an alias to the dockerized fury blockchain
alias dfury='docker exec -it generated_furynode_1 fury'
# Export private key for named account 'validator'
dfury keys unsafe-export-eth-key validator --keyring-backend test
# 8A753652CB29472A01FAECF50EC1244C307B585466B2C52373539DA0100F3CED