Feature/of 236 remove operator filter from all erc721 implementations #129
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Removes open sea's operation filter from contracts.
The reason being was that the operation filter wasn't deployed to sepolia so it causes the deployment to revert.
Me and @tinypell3ts did this at some point on arbitrum-sepolia and I believe the ERC721 contracts were deployed the way seen in this PR. This to bring the codebase inline with what is deployed.
I ran into the same issue when deploying the staging contracts see PR #128 , and so the
Base
andLazyMint
contracts here are what are currently deployed.Related Issue/Bounty
OF-236
Type of Change
Please check the boxes that apply to your pull request:
Testing
N/A no tests were written for operation filter functionality, all tests pass with
forge test