Closed shellteo closed 1 year ago
We're currently trying to use same-address on all networks. modifying the "deterministic deployer" is not a solution, since it by itself, modifies the resulting address. It would be nice to fix the scripts to support non-deterministic EntryPoint addresses, but then it is far more difficult to validate the same implementation is indeed deployed on all networks. Might be better to persuade the network operator to perform a "state-change" that would let the standard deterministic deployer by deployed on the network, and thus all deployments that depend on it will work seamlessly. on mantle, it might require just to allow running this single transaction at the cost of 100 gwei
Description
I am having trouble starting the bundler service after successfully deploying the EntryPoint contract. The error is "FATAL: Invalid entryPoint contract at xxx. wrong version?"
Environment
Steps to Reproduce
1. Deterministic-deployment-proxy deployment on Mantle testnet
1)Modify the JSON_RPC in scripts/test.sh as shown in the figure below
Execute
./scripts/test.sh
and an error is reported as follows.Our mantle testnet transactions are all set to 1wei, so modify the
gasPrice
inscripts/compile.ts
to 1wei, as shown in the figure belowExecute npm run build to generate the output/deployment.json file, then execute ./scripts/test.sh to deploy the contract to Mantle.
2. Deploy the EntryPoint contract to Mantle testnet
Add the
mantleTestnet
network anddeterministicDeployment
configuration tohardhat.config.ts
in theaccount-abstraction
project.Execute
yarn run deploy --network mantleTestnet
command to deployEntryPoint
contract andSimpleAccountFactory
contract, the results are as follows3. Run the bundler service
According to the content deployed in the third step, modify the
network
,EntryPoint
andbeneficiary
in thepackages/bundler/localconfig/bundler.config.json
configuration in the bundler projectExecute the following command to start bundler
and then report an error