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.

Sign up for GitHub

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

Jump to bottom

Spike: should we truncate sha256 hashes to <=254 bits instead of using 2 fields? #1867

Closed
dbanks12 opened this issue Aug 29, 2023 · 2 comments
Closed

Spike: should we truncate sha256 hashes to <=254 bits instead of using 2 fields? #1867

dbanks12 opened this issue Aug 29, 2023 · 2 comments
Assignees
@jeanmon

Comments

@dbanks12
Copy link
Collaborator

No description provided.

@dbanks12 dbanks12 added this to A3 Aug 29, 2023
@dbanks12 dbanks12 converted this from a draft issue Aug 29, 2023
@dbanks12 dbanks12 added the spike label Aug 29, 2023
@dbanks12
Copy link
Collaborator Author

Also discuss same with Blake!

@jeanmon jeanmon moved this from Todo to In Progress in A3 Sep 5, 2023
@jeanmon
Copy link
Contributor

jeanmon commented Sep 5, 2023

We discussed this with @iAmMichaelConnor and he did not have any objection.
Therefore, we have opened a task for the backlog to simplify the protocol by using truncation:
#2019

@jeanmon jeanmon closed this as completed Sep 5, 2023
@github-project-automation github-project-automation bot moved this from In Progress to Done in A3 Sep 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jeanmon jeanmon

Labels
None yet
Projects
A3
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dbanks12 @jeanmon