Skip to content
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

Sherlock-31 Final: EIP 4494 compliance #907

Merged
merged 1 commit into from
Jun 28, 2023
Merged

Conversation

prateek105
Copy link
Contributor

@prateek105 prateek105 commented Jun 23, 2023

Description of change

High level

bytes4 interfaceId
) public view virtual override returns (bool) {
return
interfaceId == type(IPermit).interfaceId || // 0x5604e225
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can just use the constant bytes4 in the equality check and have the derivation in the comment to save gas.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is less likely to be called from a contract in a transaction, I'm happy with it as-is for readability tradeoff.

@grandizzy grandizzy changed the title Sherlock Final 31: EIP 4494 compliance Sherlock-31 Final: EIP 4494 compliance Jun 24, 2023
Copy link
Collaborator

@MikeHathaway MikeHathaway left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

---We already have an external nonces method implemented--- This is just for the interface

Copy link
Collaborator

@MikeHathaway MikeHathaway left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@grandizzy
Copy link
Contributor

We already have an external nonces method implemented

I think the new function is only in interface that is overriden by existing one

Copy link
Contributor

@ith-harvey ith-harvey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The links that summarize the issue may die... please copy and paste the issue into the description directly

Copy link
Contributor

@grandizzy grandizzy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@EdNoepel EdNoepel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As mentioned in the other PR, I'm surprised OZ does not offer a fully-baked EIP-4494-compliant ERC-721 token.

@grandizzy
Copy link
Contributor

The links that summarize the issue may die... please copy and paste the issue into the description directly

done

Copy link
Contributor

@ith-harvey ith-harvey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants