Error when writing Genesis Block - GenesisProxy.protectSetUpProxy contract call was reverted: Already Protected #2196
Description
Description
I suffered a catastrophic issue with my original chain which ran for over 15 million blocks. The local GETH Rootchain I was running failed due to corrupted data after a power outage caused a unsafe shutdown. Upon restarting, it auto truncated the chain and completely ruined the blockchain data. Since the Rootchain no longer functioned, neither did my Edge powered chain.
In an attempt to fix this, I tried using the Regenesis process to start a new Edge chain using the old data. I was successfully able to recover the old Trie data and go through the Regenesis process with no issue at all (Create Genesis file, Deploy Stake Manager, Deploy Rootchain Contracts, Whitelist Validators, Register Validators, Stake Validators, and Finalize Genesis Set). The issue arises once I go to start the new chain after the Regenesis Process and copying over old Trie Data. For reference, I have started an entirely new Rootchain and Edge nodes, using new keys across the board.
The error I receive is:
"Error writing genesis block: GenesisProxy.protectSetUpProxy contract call was reverted: Already Protected"
Could this be an issue because the Trie Data from the previous chain contains the GenesisProxy contract at the same address?
Your environment
- Ubuntu 22.04.4
- Edge v1.3.1
- Locally run with custom Geth Rootchain
Steps to reproduce
- Regensis of an already existing Edge chain using v1.3.1 across the board.
- Launch local GETH Rootchain
- Deploy Rootchain Contracts
- Whitelist and Stake Validators
- Run Edge Client
