global-synchronizer/understand/validator-roles

[giscus[bot]]

global-synchronizer/understand/validator-roles

Understanding what it means to operate a validator on Canton Network

https://docs.canton.network/global-synchronizer/understand/validator-roles

[waynecollier-da]

This phrasing could be misleading, and I suspect it is the source of confusion in the ecosystem:

---

As a validator, you trust that:
The synchronizer orders transactions fairly
Super Validators maintain availability
Network parameters are set appropriately
Upgrades are coordinated properly

You do NOT need to:
Run consensus nodes
Verify all network transactions
Participate in governance votes
Operate synchronizer infrastructure

---

Specifically, the following points:

• "As a validator, you trust that the synchronizer orders transactions fairly". This is not true in the case of the Global Synchronizer. The more accurate statement for the Global Synchronizer is that the Validator trusts that a 2/3 majority quorum has not colluded falsely order transactions, and that "f" nodes are not blocking transactions. In other words, the Validator is not merely trusting "the synchronizer"; it is relying on a set of BFT guarantees.

If a synchronizer is operated by a group of nodes that is too small to provide BFT guarantees (3 or fewer), then it is true that the Validator simply has to trust the synchronizer.

• "As a validator, you trust that: Network parameters are set appropriately". It's unclear what this means. If the SVs set their network parameters incorrectly, they may fail to reach quorum. If they do reach quorum, and consensus advances, any errors in network parameters should (in theory) be irrelevant.
  * The same holds for "upgrades are coordinated properly". If the Global Synchronizer--or any synchronizer--is operating, then upgrades have been coordinated. I'm not sure what insight this point provides.

• "As a Validator, you do NOT need to: Run consensus nodes". This is misleading. Every Validator is a Consensus node, in the sense that it participates in consensus around transaction validation. Perhaps rephrase to "As a Validator you do NOT need to run a synchronizer consensus node" but that is covered later in the list, so I'd recommend just dropping this point.