Historical hash #4683
Open
Historical hash #4683
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ma2bd
force-pushed
the
historical_hash
branch
2 times, most recently
from
4d1f652 to
578aab6
Compare
ma2bd
force-pushed
the
historical_hash
branch
2 times, most recently
from
8b432e0 to
a6c77f5
Compare
ma2bd
force-pushed
the
historical_hash
branch
from
88bf2c0 to
cc2e828
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Add support for historical hashing
Proposal
ClonableViewI ended up with a solution that is entirely separate from
HashableView.Test Plan
CI
Release Plan
This won't be trivial to release in testnet but maybe still doable.