Important
- Adding custom EVM-compatible blockchains to your Fireblocks is a premium feature that requires an additional purchase. Contact your Customer Success Manager for more information.
- Before your custom EVM-compatible blockchain becomes available on the Fireblocks platform, you must provide Fireblocks with a commercial agreement signed by all involved parties.
To add a custom EVM-compatible blockchain to the Fireblocks platform, first make sure addresses are structured in Ethereum format (see details here), specifically as 42 hexadecimal characters.
Then, for seamless integration with our backend flow, the following node requirements must be met:
- The node type is either “go ethereum” (geth) or some parity node (OpenEthereum).
- The “go ethereum” node supports the following endpoints (i.e., these endpoints must be implemented):
- xpool_content or eth_getBlockByNumber with pending transactions
- eth_getBlockByNumber
- eth_getLogs or eth_getBlockReceipts
- eth_getTransactionReceipt
- eth_blockNumber
- debug_traceBlockByNumber
- debug_traceTransaction
- Parity nodes/non-“go ethereum” nodes must support the following additional endpoints:
- parity_getBlockReceipts
- parity_pendingTransactions
- trace_block
- Trace_transaction
- The “go ethereum” node supports the following Web3 SDK (more info here):
- getTransaction
- getBlock
- getTransactionReceipt
- blockNumber
- getBalance
- send_raw_transaction
- Recover_transaction
After the above information is verified, provide the following preliminary information to your Fireblocks Customer Success Manager.
- Public/private node RPC URL (please supply API key if needed)
- Indication whether your system requires whitelisting Fireblocks IP addresses
- Chain ID
- Network ID (optional; if not provided, the Chain ID is used instead)
- Native token name & symbol
- CoinMarketCap link of the native token, to provide a United States dollar (USD) equivalent of the asset (optional)
- Block explorer (optional; if provided, your custom blockchain can be added to the Fireblocks platform)
- Decimals (optional; the default is 18)
- SLIP-44 coin type (optional; the default is 60 as ETH)
- Mainnet / Testnet
- Fee structure (before/after London Fork)
- Gas required (Yes/No)
- Finality state:
-
Yes - then how many blocks does it consist of?
-
No - then after how many confirmed blocks is a transaction considered “safe”?
-