-
Notifications
You must be signed in to change notification settings - Fork 50
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
feat(pool): handle UREP-020 and track reputation of unstaked entities #522
Conversation
Codecov ReportAttention:
Additional details and impacted files
... and 1 file with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more.
|
003349f
to
ba528c8
Compare
ba528c8
to
3c0be7f
Compare
d679944
to
c70cee8
Compare
c70cee8
to
341ec0b
Compare
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.
Lets make sure this is as close to compliant with the latest ERC-7562, while still passing all tests on the commit we've pegged to.
If there are changes in ERC-7562 that cause failures, lets capture them as tickets so we know to update them when we move to a new spec test commit.
One more small nit on the PR to fix up the entities stuff.
Do these changes fix those errors we spoke about in the spec tests? |
c2c2f98
to
0b881ff
Compare
3d0ebc1
to
d83e4c2
Compare
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.
One last comment and then this is good to go. Can you squash to a single commit?
@dancoombs I enabled squash and merge after that chat the other day, will use the PR title as the commit message |
Closes #454, closes #354
Proposed Changes
SAME_SENDER_MEMPOOL_COUNT
check out fromPoolInner
intoUoPool
SAME_SENDER_MEMPOOL_COUNT
check