Skip to content
This repository was archived by the owner on Sep 1, 2023. It is now read-only.
This repository was archived by the owner on Sep 1, 2023. It is now read-only.

Blur bypasses Operator Filter Registry? #91

Description

@agsola

After taking a look at this tweet:
https://twitter.com/pandajackson42/status/1620081518575235073
It seems they did with their own conduit, and the seem to be honouring Royalties.

But, what stops Blur from not honoring Royalties? Using their own conduit allows them to remove or introduce any arbitrary fees as long as the user list the NFT under their conduit.

But, on the other hand a new conduit is a new contract that could be blocked, right? Will you? Or being royalties complain on this conduit is enough to follow the rules as long as they honour royalties?

EDIT: I've done some more research and realized that they actually are using OpenSea's conduit. Then, there's no way to forbid it, right?

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions