Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IPLD Resolver: Gossip votes on top-down message finality #447

Closed
aakoshh opened this issue Mar 13, 2023 · 0 comments · Fixed by consensus-shipyard/ipc-libs#106
Closed

IPLD Resolver: Gossip votes on top-down message finality #447

aakoshh opened this issue Mar 13, 2023 · 0 comments · Fixed by consensus-shipyard/ipc-libs#106
Assignees
Labels

Comments

@aakoshh
Copy link
Contributor

aakoshh commented Mar 13, 2023

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:

  • 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)
@aakoshh aakoshh self-assigned this Mar 20, 2023
@jsoares jsoares transferred this issue from consensus-shipyard/ipc-libs Dec 19, 2023
@jsoares jsoares added the s:ipc label Dec 19, 2023
@jsoares jsoares closed this as not planned Won't fix, can't repro, duplicate, stale Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants