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

Allow seeding k3 randomness and return index of invalid label #165

Closed
Tracked by #5185
poszu opened this issue Dec 19, 2023 · 0 comments · Fixed by #166
Closed
Tracked by #5185

Allow seeding k3 randomness and return index of invalid label #165

poszu opened this issue Dec 19, 2023 · 0 comments · Fixed by #166
Assignees

Comments

@poszu
Copy link
Collaborator

poszu commented Dec 19, 2023

Each verifier must verify a different subset of k3 indices to support distributed verification. To achieve that, the randomness seed used to select k3 indices must include a unique value for the verifying node (public key, p2p peer ID, etc.).

To create a malfeasance proof, we need to know which index in the proof is invalid. The result from the verification method should include this information.

@poszu poszu self-assigned this Dec 19, 2023
@poszu poszu transferred this issue from spacemeshos/go-spacemesh Dec 19, 2023
@poszu poszu moved this to 🔖 Next in Dev team kanban Dec 19, 2023
@poszu poszu moved this from 🔖 Next to 🏗 Doing in Dev team kanban Dec 20, 2023
@poszu poszu changed the title option to verify selected indices in POST and return index of invalid label Seed k3 randomness with verifier ID and return index of invalid label Dec 21, 2023
@poszu poszu changed the title Seed k3 randomness with verifier ID and return index of invalid label Allow seeding k3 randomness and return index of invalid label Jan 11, 2024
@github-project-automation github-project-automation bot moved this from 🏗 Doing to ✅ Done in Dev team kanban Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant