EZswap, a well-known community-focused NFT decentralized exchange (DEX), has recently shared on Twitter that the platform’s team has found a royalty bug on Opensea. The team not only detected the bug successfully but also carried out thorough research on it. As a result of that, it offered a solution to assist the NFT projects. The purpose of offering the respective solution was to help Opensea in having a remarkable future instead of centralization.
EZswap Team Finds Opensea’s Royalty Bug and Attempts to Solve It
In its Twitter posts, EZswap mentioned that the platform deployed the bug on the chain. In this way, the company advised the consumers to discover the penultimate log item called “Initialized.” As per it, the address that is listed there counts as the consumers’ latest developed royalty sub-contract. It also stated that the users should focus on the 2 “Initialized” in the respective logs.
According to it, if the consumers are not sure, they should click on a given contract to clarify. It added that, if the name of the contract is “EIP2981MultiReceiverRoyaltyOverrideCloneable,” they should proceed. After that, it mentioned the 2nd step. In this step, it noted that the clients should register the royalty sub-contract that they have just developed with the use of the REGISTRY center.
Additionally, it specified that the consumers should move to the contract with the address given by it. There, it added, the users should enter the address of their NFT contract and the royalty sub-contract. In its words, “EIP2981RoyaltyOverrideFactory (0x73417822938f2cb740B9f9b560cABfA0413440a1) is the present registration contract focusing on the OS royalties.
The Platform Offers a Solution by Doing the Steps Separately
The 1st step is the cloning of a royalty sub-contract. The 2nd step is to initialize the respective sub-contract. The 3rd step is the registration of the respective sub-contract. The platform brought to the front that, 3 days back, someone updated the implemented contract. As a result of that, the 3rd step cannot be accomplished in this way the royalties verification fails.
While elaborating on it, EZswap disclosed that an NFT owner can validate effectively. In this respect, the solution is to develop an exclusive factor that just retains the initial 2 steps. After that, the interaction with the REGISTRY should be done separately in the 3rd step for effective validation.
