-
Notifications
You must be signed in to change notification settings - Fork 10
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
refactor: move from transaction id to transaction hash #479
refactor: move from transaction id to transaction hash #479
Conversation
…nsaction-hash # Conflicts: # backend/protocol_rpc/endpoints.py # tests/common/transactions.py
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very good job, only one endpoint that got restored when it was removed before
…ion-id-with-transaction-hash
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good! all minor comments
My main question is the one about the transaction hash being the current ID
backend/database_handler/migration/versions/99d3f1bc5a08_add_hash.py
Outdated
Show resolved
Hide resolved
backend/database_handler/migration/versions/99d3f1bc5a08_add_hash.py
Outdated
Show resolved
Hide resolved
This reverts commit f0a502a.
…ion-id-with-transaction-hash
🎉 This PR is included in version 0.8.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Fixes #451
What
Move frome id to hash in the transaction model.
Why
To get closer to eth spec.
Testing done
Checks
Reviewing tips
User facing release notes