Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Proposed HF5 @ 22800 #19
Proposed change allows us to change the algorithm used by header.Hash() at later times. It is worth noting that (in this PR) the header version does NOT need to make it into the block chain, and IS ignored by rlp, and NEVER sent peer-to-peer. The header version is calculated locally with two parameters: block height and current running chain config (Mainnet, Testnet, etc)
If your instance of aqua is expecting block 200 to be hashed with "algorithm A", if you receive a header from a peer, you will not receive the version along with it. The local node calculates which version hash algorithm to apply to a block. The resulting hash would mismatch, and parent hashes would also break validation.
There are a ton of instances of the
With these changes,
Testing Argon2id POW
With aquachain command: Run with
With aquaminer command:
The rc2 zips have aquachain-HF5rc2 bundled with aquaminer (standalone miner)
About the testnet
I have switched my explorer to testnet (explorer.aquanetwork.co)
Testnet has one bootnode, and finding peers isn't too bad. Lots of mainnet peers trying to connect, but then disconnect due to unequal genesis blocks (mainnet and testnet have two different genesis blocks)
Previous hard forks are activated on their block number. HF1 is at block one, HF2 at block two, etc.
HF5 (block 5) is where argon2id is activated.