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

Add new transaction for validators to submit DataCommitments #199

Closed
evan-forbes opened this issue Feb 2, 2022 · 0 comments
Closed

Add new transaction for validators to submit DataCommitments #199

evan-forbes opened this issue Feb 2, 2022 · 0 comments
Assignees

Comments

@evan-forbes
Copy link
Member

To accomodate the QGB, validators need a way to submit signatures for a data commitments so that relayers can easily find them and submit them to the bridged chain. To do this, we will introduce MsgSubmitDataCommitment

This new message type needs to convey

  • the signature
  • that the validator's associated bridge address
  • the commitment
  • the range of blocks that that commitment was generated over

The business logic for this message needs to check that

  • the range of blocks is correct
  • the signature is valid
  • that the provided validator's bridge address is the one associated with that validator

Lastly, relayers will need to be able to query these commitments in a similar fashion to how they query ValSetConfirms

tracking issue #44

@evan-forbes evan-forbes moved this to TODO in Celestia Node Feb 2, 2022
@evan-forbes evan-forbes moved this from TODO to In Review in Celestia Node Feb 11, 2022
@evan-forbes evan-forbes moved this from In Review to TODO in Celestia Node Feb 11, 2022
@evan-forbes evan-forbes moved this from TODO to In Progress in Celestia Node Feb 21, 2022
@rach-id rach-id moved this from In Progress to Done in Celestia Node Feb 24, 2022
@rach-id rach-id closed this as completed Mar 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Archived in project
Development

No branches or pull requests

2 participants