-
Notifications
You must be signed in to change notification settings - Fork 38
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 sudt with registry address #649
Merged
jjyr
merged 39 commits into
godwokenrises:develop
from
jjyr:refactor-sudt-with-registry-address
Apr 18, 2022
Merged
Refactor sudt with registry address #649
jjyr
merged 39 commits into
godwokenrises:develop
from
jjyr:refactor-sudt-with-registry-address
Apr 18, 2022
Conversation
This file contains 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
blckngm
reviewed
Apr 7, 2022
blckngm
reviewed
Apr 7, 2022
blckngm
reviewed
Apr 7, 2022
blckngm
reviewed
Apr 7, 2022
blckngm
reviewed
Apr 7, 2022
blckngm
reviewed
Apr 7, 2022
blckngm
reviewed
Apr 7, 2022
blckngm
reviewed
Apr 7, 2022
blckngm
reviewed
Apr 7, 2022
blckngm
reviewed
Apr 7, 2022
blckngm
reviewed
Apr 7, 2022
blckngm
reviewed
Apr 7, 2022
Flouse
added a commit
to Flouse/godwoken-docker-prebuilds
that referenced
this pull request
Apr 7, 2022
blckngm
reviewed
Apr 11, 2022
blckngm
reviewed
Apr 11, 2022
zeroqn
previously approved these changes
Apr 12, 2022
magicalne
previously approved these changes
Apr 12, 2022
jjyr
force-pushed
the
refactor-sudt-with-registry-address
branch
from
April 13, 2022 05:43
389ca01
to
e7be075
Compare
ErrMsg: 1. failed Unlock error Invalid signature: Wrong chain_id, expected: 71400 actual: 0 2. Invalid signature: Mismatch pubkey hash
jjyr
force-pushed
the
refactor-sudt-with-registry-address
branch
from
April 14, 2022 07:52
0783572
to
fdfd7d1
Compare
Rebased |
keroro520
reviewed
Apr 14, 2022
keroro520
previously approved these changes
Apr 14, 2022
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
FeeQueue benchmark test is failing. Otherwise LGTM. |
Fixed the benchmark test. @sopium @keroro520 |
blckngm
previously approved these changes
Apr 15, 2022
zeroqn
reviewed
Apr 15, 2022
zeroqn
approved these changes
Apr 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
CHANGES
Related PRs