Skip to content
This repository has been archived by the owner on Dec 20, 2023. It is now read-only.

Update on-chain membership after reconfiguration in subnets #125

Closed
adlrocha opened this issue Mar 20, 2023 · 1 comment
Closed

Update on-chain membership after reconfiguration in subnets #125

adlrocha opened this issue Mar 20, 2023 · 1 comment
Labels

Comments

@adlrocha
Copy link
Contributor

In consensus-shipyard/ipc-actors#70 a new set_validators method has been implemented in the gateway in order to be able to track the validators in a subnet on-chain. This will be key for certain processes like the execution of top-down messages.

This method can only be executed implicitly and the idea is the following:

  • When a new reconfiguration is triggered and successful in Mir, validators push a message to their message pools from the system actor to the gateway to set the new validator set so that it is included in the next block. When peers face this message in a block, they execute it implicitly to update the on-chain validator information.
  • There shouldn't be duplicates of this message in a block, but if there are, it doesn't matter because they are all executed implicitly, and they lead to the final end result. The only issue is that these messages will take block space.
  • Also, as this messages are executed implicitly, their validity can be verified by validators before including it in a block. If a validator tries to forge it or include an invalid message that sets the validator set it will lead to them ending up with the wrong state and merging from the valid chain.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant