Precompile Overview
Interact with native Subnet-EVM precompiles
Available Subnet-EVM Precompiles
Below are listed out the default Subnet-EVM precompile interfaces.
Interacting with Precompiles
If a precompile is enabled within the genesis.json
using the respective ConfigKey
we can interact with the precompile using Foundry or other tools such as Remix.
Below are listed out the addresses and ConfigKey
of default precompiles we can enable in Subnet-EVM. The address and ConfigKey
are defined in the module.go
of each precompile contract.
Precompile | ConfigKey | Address |
---|---|---|
Deployer Allow List | contractDeployerAllowListConfig | 0x0200000000000000000000000000000000000000 |
Native Minter | contractNativeMinterConfig | 0x0200000000000000000000000000000000000001 |
Transaction Allow List | txAllowListConfig | 0x0200000000000000000000000000000000000002 |
Fee Manager | feeManagerConfig | 0x0200000000000000000000000000000000000003 |
Reward Manager | rewardManagerConfig | 0x0200000000000000000000000000000000000004 |
Warp Messenger | warpConfig | 0x0200000000000000000000000000000000000005 |
For example, if contractDeployerAllowListConfig
is enabled in the genesis.json
:
We can then add an Enabled
address to the Deployer Allow List by interacting with the IAllowList
interface at 0x0200000000000000000000000000000000000000
Last updated on