[Y14] - RoyaltyLoyalty 🏅

Create an extension for EIP-2981 (NFT Royalty Standard) to define a RoyaltyPayment event, standard hook for a marketplaces to send a royalty payment to a royalty receivers, and additional royalty configuration options

Challenges

Best Use of Infura NFT API

Ranked 6,000 ETH

Used it to quickly iterate when we were redeploying NFT contracts to testnet :)

Web3Modal Theming Challenge

Ranked 5,000 USDC

Checkout around 4 min in the video :) we have a really nice them

Most Useful Web3 Tool

Ranked 2,500 ETH

We created a very useful tool for artists :)

Best new subgraph(s)

Ranked 5,500 USDC

Hopefully the subgraph for royalty events can be used as a base for a lot of artists in the future :)

Developer Infrastructure/tooling on Mantle

Ranked 6,000 ETH

We deployed our contracts to multiple chains via a CREATE3 factory and we deployed a CREATE3 factory to base so all our deployments would be at the same address. See readme of github repo :)

Best Use of Existing Subgraph(s)

Ranked 4,500 USDC

We used Lens' subgraph to figure out which collectors of an artist were following them :)

#BUIDLathon 2023 NFTs + Metaverse + Gaming Track

Pool 15,000 USDC

Hopefully a new EIP!

Polygon NFT Analytics Challenge

Ranked 10,000 ETH

Created a creator focused dashboard to look at how their collector base is paying royalties

Integrate Lens

Pool 10,000 USDC

Integrated Lens so artists can create private gated posts for subsets of their collectors to engage with them :)

Build on Base 🔵

Ranked 15,000 USDC

We deployed our contracts to multiple chains via a CREATE3 factory and we deployed a CREATE3 factory to base so all our deployments would be at the same address. See readme of github repo :)

Build on Pocket Network

Pool 3,750 USDC

Used it as our RPC :)

Project details

Whether or not marketplaces respect royalty payments is a hot topic in the current NFT market. The problem we see in this debate is not directly related to enforcement but rather that there is no easy way for a creator to see when and where royalties are respected. With this data, creators would be able to incentivize greater adherance to their defined social contract.

To confront this problem we propose an extension to EIP-2981 that includes a standardized royalty payment event and a payment hook on the token contract that emits this event. Using these two pieces a contract is able to more dynamically respond to the routing and side effects of these payments.

In addition to the interface implementation, we have also implemented a sample marketplace that responds to our interface and routes royalty payments through the hook. Using this exchange with a mock token we can emit an event every time a royalty is or is not respected and index this data off-chain using our custom subgraph.

Finally, with these pieces, we have created our web app Royalty Loyalty. This dashboard allows creators to easily see what addresses are or are not respecting loyalties. From here the creator can interact with these addresses through integration with Lens and possibly find ways further enforce their unique social contract around royalties.