-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Parity to method class #1602
Parity to method class #1602
Conversation
a458ac1
to
9a970f8
Compare
c93c650
to
1fdec7f
Compare
2e4abac
to
78af94b
Compare
fbadf4d
to
af46526
Compare
af46526
to
211b04d
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.
This may sit for a while longer, but just caught it up with master. Looks good generally and tests are happy, but I don't grok all, so couple of requests for clarification below.
Separate from the intention of this PR, we might be due for a discussion on Parity vs. OpenEthereum support (and maybe other nodes?). Lots of Parity nodes still in use, so obviously we won't chuck that out anytime soon. This topic also comes to mind though after recent All Core Devs conversations about increasing client diversity... Probably worth its own issue.
cda3b17
to
fe8e2b8
Compare
b6356d3
to
9bcdc02
Compare
9bcdc02
to
c8bdbd4
Compare
@marcgarreau I think this is (finally) ready to go! |
0ebfe76
to
864e13c
Compare
864e13c
to
cf57aa8
Compare
What was wrong?
The Parity class needed to move over to use the
Method
class andModuleV2
class.How was it fixed?
Started using
Method
andModuleV2
Todo:
Cute Animal Picture