Predeployed Contracts:
To enable some bleeding-edge features that EVM provides (like pay gas with any tokens), we have developed an ability to deploy contracts in genesis config. Initially it was done to deploy Entrypoint contract only, but we have supported this functionality for any contract with some limitations.
How to use:
Step 1: Compiling your contracts
Currently we are supporting contracts that are compiled with Forge or Hardhat. If you want any other tool to be supported, consider creating an issue and attach and example of compiled contract.
Here are compilation guides:
When you have compiled the contracts, take the resulting JSON for your contract and save into a single directory for the future deployment.
Step 2: Creating the configuration
In the directory where you have saved the contracts, create a file name "contracts.json". In this file you should store an array of contract metadata, that contains filename of the artifact and the address where you want this contract to be deployed to. So, it should like like this:
[
{
"address": "0x81ead4918134AE386dbd04346216E20AB8F822C4",
"filename": "Entrypoint.json"
}
]You can take as an example a file in our EVM template in path contracts/contracts.json.
Step 3: Building the chainspec
During the step when you generate a chainspec pass the parameter --predeployed-contracts with a path to the directory where you have stored the contract artifacts and the configuration:
./target/release/parachain-template-node build-spec --disable-default-bootnode --predeployed-contracts=<path_to_dir> > plain-parachain-chainspec.json