-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Update EIP-5615: Move to Last Call #6185
Conversation
✅ All reviewers have approved. |
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.
Your security considerations is still "Needs discussion." That'll need to be filled out (even with just "none") before going into last call.
Done (this branch isn't updated) |
@SamWilsn fixed |
@eth-bot rerun |
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.
Whether the given token id exists, previously existed, or may exist
This is ambiguous. Should exists
return true or false in each of these cases:
- Token cannot exist (unambiguously false?)
- Token exists (unambiguously true?)
- Token could exist, but has never been minted.
- Token has existed, but has been destroyed.
I'd reword and move some bits around:
Move to specification:
Implementations MAY support ERC-165 interface discovery with an id of
0x...
, but consumers MUST NOT rely on it.
Move to rationale:
This EIP does not mandate ERC-165 support as this interface is simple enough that the extra complexity is unnecessary and would cause incompatibilities with pre-existing implementations.
False. It's not ambiguous. It's a binary OR of all three options. |
@@ -4,7 +4,8 @@ title: EIP-1155 Supply Extension | |||
description: A simple mechanism to fetch token supply data from EIP-1155 tokens | |||
author: Pandapip1 (@Pandapip1) | |||
discussions-to: https://ethereum-magicians.org/t/eip-5615-eip-1155-supply-extension/10732 | |||
status: Review | |||
status: Last Call | |||
last-call-deadline: 2023-03-08 |
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.
last-call-deadline: 2023-03-08 | |
last-call-deadline: 2023-04-27 |
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.
I read through it and believe there is no ambiguity about when to return zero.
Approved and please don't forget to update the deadline
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.
All Reviewers Have Approved; Performing Automatic Merge...
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.
All Reviewers Have Approved; Performing Automatic Merge...
No description provided.