Precompile-EVM is a repository for registering precompiles to Subnet-EVM without forking the Subnet-EVM codebase. Subnet-EVM supports registering external precompiles through precompile/modules
package. By importing Subnet-EVM as a library, you can register your own precompiles to Subnet-EVM and build it together with Subnet-EVM.
There is an example branch hello-world-example in this repository. You can check the example branch to see how to register precompiles and test them.
First, you need to create your precompile contract interface in the contracts
directory and build the ABI. Then you can generate your precompile files with ./scripts/generate_precompile.sh --abi {abiPath} --out {outPath}
. This script installs the precompilegen
tool from Subnet-EVM and runs it to generate your precompile.
In plugin/main.go
Subnet-EVM is already imported and ready to be Run from the main package. All you need to do is explicitly register your precompiles to Subnet-EVM in plugin/main.go
and build it together with Subnet-EVM. Precompiles generated by precompilegen
tool have a self-registering mechanism in their module.go/init()
function. All you need to do is to force-import your precompile packprecompile package in plugin/main.go
.
You can build your precompile and Subnet-EVM with ./scripts/build.sh
. This script builds Subnet-EVM, and your precompile together and generates a binary file. The binary file is compatible with AvalancheGo plugins.
You can create contract tests in contracts/test
with the Hardhat test framework. These can be run by adding ginkgko test cases in tests/precompile/solidity/suites.go
and a suitable genesis file in tests/precompile/genesis
. You can install AvalancheGo binaries with ./scripts/install_avalanchego_release.sh
then run the tests with ./scripts/run_ginkgo.sh
In order to upgrade the Subnet-EVM version, you need to change the version in go.mod
and scripts/versions.sh
. You can also change the AvalancheGo version through scripts/versions.sh
as well. Then you can run ./scripts/build.sh
to build the plugin with the new version.
[v0.1.0-v0.1.1] [email protected] (Protocol Version: 26)
[v0.1.2] [email protected] (Protocol Version: 27)