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 EffectHash test vectors #4613

Open
redshiftzero opened this issue Jun 13, 2024 · 0 comments · May be fixed by #4879
Open

add EffectHash test vectors #4613

redshiftzero opened this issue Jun 13, 2024 · 0 comments · May be fixed by #4879
Assignees
Labels
A-testing Area: Relates to testing of Penumbra
Milestone

Comments

@redshiftzero
Copy link
Member

We should add test vectors for the EffectHash mechanism for transaction signing, i.e. we should generate a bunch of random TransactionPlans, compute their EffectHash, and add them as test vectors. This will guard against additions of proto fields from breaking the effect hash as well as aid in development for others implementing transaction signing.

@redshiftzero redshiftzero added the A-testing Area: Relates to testing of Penumbra label Jun 13, 2024
@github-actions github-actions bot added the needs-refinement unclear, incomplete, or stub issue that needs work label Jun 13, 2024
@aubrika aubrika added this to the Sprint 10 milestone Aug 20, 2024
@aubrika aubrika removed the needs-refinement unclear, incomplete, or stub issue that needs work label Aug 26, 2024
@aubrika aubrika modified the milestones: Sprint 10, Sprint 11 Aug 26, 2024
@aubrika aubrika modified the milestones: Sprint 11, Sprint 12 Sep 9, 2024
@aubrika aubrika modified the milestones: Sprint 12, Sprint 13 Sep 23, 2024
@aubrika aubrika modified the milestones: Sprint 13, Sprint 14 Oct 7, 2024
@aubrika aubrika modified the milestones: Sprint 14, Sprint 15 Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-testing Area: Relates to testing of Penumbra
Projects
Status: In progress
Development

Successfully merging a pull request may close this issue.

3 participants