The Quorum Developer Quickstart utility can be used to rapidly generate local Quorum blockchain networks for development and demo purposes using Besu and GoQuorum
Apache License 2.0
135
stars
101
forks
source link
Should a QBFT Node Have a 'Validator Smart Contract'? #292
From what I understand (or heard somewhere), if you specify the validatorsmartcontractaddress value in the qbft settings field in the genesis.json file of a QBFT node (for example, 0x......089), it designates a smart contract that dynamically manages the validator nodes.
From what I understand (or heard somewhere), if you specify the
validatorsmartcontractaddress
value in theqbft
settings field in thegenesis.json
file of a QBFT node (for example,0x......089
), it designates a smart contract that dynamically manages the validator nodes.This project demonstrates this concept well: https://github.com/Consensys/validator-smart-contracts
Of course, while it is dynamic, it is not automatic, so it seems that something else is needed to add or remove node information. (Am I mistaken?)
However, it is disappointing that such an example is not seen in quorum-dev-quickstart.
I haven't tested it yet, but could it be that QBFT automatically registers this even if the
validatorsmartcontract
option is not specified?