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

Support 0x04040404 for supportsInterface function #68

Closed
wants to merge 1 commit into from
Closed

Support 0x04040404 for supportsInterface function #68

wants to merge 1 commit into from

Conversation

ghost
Copy link

@ghost ghost commented Feb 15, 2024

Description

Would be great if we could support 0x04040404 as an identifier for DN404 contracts, so that the contract could automatically call setSkipNFT before transfer, etc.

Checklist

Ensure you completed all of the steps below before submitting your pull request:

  • Ran forge fmt?
  • Ran forge snapshot?
  • Ran forge test?

Pull requests with an incomplete checklist will be thrown out.

@ghost ghost mentioned this pull request Feb 15, 2024
@Vectorized
Copy link
Owner

Just try catch call setSkipNFT. Not a fan of 165, it can be spoofed.

Btw, all contracts are automatically whitelisted to skip NFTs.

@ghost
Copy link
Author

ghost commented Feb 15, 2024

@Vectorized Hmm would it be problematic if the token is sent before the contract deployment? https://despac1to.medium.com/carefully-use-openzeppelins-address-iscontract-msg-sender-4136cc6ff66d

edit ) seems like _ADDRESS_DATA_INITIALIZED_FLAG prevents it though.

@Vectorized
Copy link
Owner

Vectorized commented Feb 15, 2024

🤔 Lemme marinate on this.

@ghost ghost closed this by deleting the head repository Apr 22, 2024
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant