-
Notifications
You must be signed in to change notification settings - Fork 114
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
fix: make tx receipt root field nullable #308
Conversation
API E2E Test Results207 tests 207 ✅ 19s ⏱️ Results for commit 1b54dd1. ♻️ This comment has been updated with latest results. |
Unit Test Results 4 files 263 suites 11m 44s ⏱️ Results for commit 1b54dd1. ♻️ This comment has been updated with latest results. |
Visit the preview URL for this PR: |
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.
LGTM as a quick fix, nits are up to you
@Column({ type: "bytea", transformer: hexTransformer, nullable: true }) | ||
public readonly root?: string; |
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.
Maybe makes sense leaving a comment that this field is only relevant on L1 pre byzantium fork (EIP658), but was present in ZKsync API before, so it cannot be just dropped.
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.
good idea, done.
packages/worker/src/migrations/1730806000905-TxReceiptRootColumnNullable.ts
Show resolved
Hide resolved
🎉 This PR is included in version 2.50.6 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
What ❔
Make tx receipt root field nullable.
Why ❔
RPC doesn't return this field anymore. Here is the corresponding PR.
Checklist