You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a mechanism the agents can use to submit their vote on the finality of a top-down message observed on the parent-subnet, before it can be executed on the child subnet.
It will be up to the agent to manage the state of voting:
to keep repeating messages (we can never assume that others have received and processed it)
to check if a CID has indeed been observed on the parent subnet
to aggregate the votes
the signing of messages, as they have to be signed with the validator key, which is unknown to the Resolver
The interface with the Resolver will be limited to:
the Client gets a new method to publish a vote about a CID to a specific subnet
the Service gets a new method to subscribe to events published to any of the subnets it provides data for (presumably providing data for a subnet means the agent is a validator on the subnet, able to resolve bottom-up messages to the parent, and therefore interested in votes from other validators on the subnet)
The text was updated successfully, but these errors were encountered:
Part of #453
Create a mechanism the agents can use to submit their vote on the finality of a top-down message observed on the parent-subnet, before it can be executed on the child subnet.
It will be up to the agent to manage the state of voting:
The interface with the Resolver will be limited to:
Client
gets a new method to publish a vote about a CID to a specific subnetService
gets a new method to subscribe to events published to any of the subnets it provides data for (presumably providing data for a subnet means the agent is a validator on the subnet, able to resolve bottom-up messages to the parent, and therefore interested in votes from other validators on the subnet)The text was updated successfully, but these errors were encountered: