Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

CIP 22 - Upgrade epoch SNARK data - Discussions #72

Closed
5 of 9 tasks
kobigurk opened this issue Nov 10, 2020 · 0 comments
Closed
5 of 9 tasks

CIP 22 - Upgrade epoch SNARK data - Discussions #72

kobigurk opened this issue Nov 10, 2020 · 0 comments
Assignees
Labels
HF Required Ring 0 Changes that can cause consensus failure

Comments

@kobigurk
Copy link
Contributor

kobigurk commented Nov 10, 2020

Deployment Checklist

  • Specification
  • Implementation
    • celo-blockchain
  • Testing
    • Unit tests
    • Ephemeral testnet with one validator, run plumo-prover against it
    • Ephemeral testnet with multiple validators, run plumo-prover against it (@lucasege)
  • Verification
    • Run plumo-prover against the chain
@prestwich prestwich changed the title Discussions about "[0022]: Upgrade epoch SNARK data for flexibility, slashability and security" CIP 22 - Upgrade epoch SNARK data - Discussions Dec 1, 2020
@prestwich prestwich added Ring 0 Changes that can cause consensus failure HF Required labels Dec 1, 2020
@celo-org celo-org locked and limited conversation to collaborators Mar 21, 2023
@carterqw2 carterqw2 converted this issue into discussion #327 Mar 21, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
HF Required Ring 0 Changes that can cause consensus failure
Projects
None yet
Development

No branches or pull requests

3 participants