-
Notifications
You must be signed in to change notification settings - Fork 25
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
Adoption of EIP-681 #90
Comments
EIP 681 is still a draft. Therefore, if we adopt it then we can not finalize the AEX until the base EIP is finalized. |
Why we can't finalize it internally? They have invested more resources into developing that standard, it does not have the sense to ignore it even if it has a draft status. |
@davidyuk I see many comments from you to AEX-4 and EIP-681 now seems to be final. it would probably be good to adapt it. do we follow any analogy to other chains right now in that regards? personally I don't like to have AEX-4 in the title as it is independent discussion IMO. AEX-4 has been withdrawn anyway. so I am changing that. |
The current version of AEX-4 based on BIP-0021 adding some breaking changes to it without proved rationale. I propose to take EIP-681 as a base for AEX-4, and try to adopt it changing as less as possible. Most of the things are implemented better there, especially an ability to call the contact method.
https://github.com/ethereum/EIPs/blob/master/EIPS/eip-681.md
The text was updated successfully, but these errors were encountered: