1

Looking at the image, it seems to me you are importing the backup of a private network to a node initializated with the Mainnet. I suspect this because: geth says ChainID is 1, so Mainnet the import process seems to stop with the very first block and the error is unknown ancestor, so it don't know the genesis block your block #1 hash is not the hash of the ...


1

1) I'm curious about this one ! :) 2) Yes, if you set period to 0, commit new mining work whenever a transaction arrives 3) Unlocking is done "under-the-hood" it's not a transaction, it's more an "authentication" 4) Sealers are defined in the genesis file, but you can add it by using Geth clique.propose("Sealer address", true) 5) It depends on your ...


1

PoA networks do not natively have rewards baked into the consensus. There are instances where these are created with smart contracts that make system calls (see Energy Web Chain and POS_DAO) , but if you run clique natively there will be no block rewards. References: EIP 225 POS DAO Energy Web Chain - System Contracts - Rewards Contract


1

How to implement a new custom consensus algorithm in a network? As per your question you need to first fork private ethereum blockchain(go ethereum) and need to modify consensus.go file as per your custom requirements. Hope this will help you.


1

Both sealers are configured with the same etherbase 0x933e73c3f959759c169effa4019c8faf7d05ce33. And the second sealers fails to sign blocks because it is locked: WARN [09-20|17:00:54.874] Block sealing failed err="authentication needed: password or unlock" You have to pass the sealer address with geth parameter --miner.etherbase XXXX.


Only top voted, non community-wiki answers of a minimum length are eligible