Creator Rewards

Screenshots

Problem Statement

We built a web app for creators that have a Creator Coin (CC), to enable them to engage with their fans in new and innovative ways. The app has two tabs, an "Earn" tab and a "Rewards" tab, both configurable by the creator. On the earn tab, creators can set up campaigns to automate rewarding fans with their CC in return for certain actions like subscribing to their newsletter, or referring a friend. And then, on the rewards tab, fans can redeem their CC for NFTs (which we help the creator mint lazily upon redemption) and other rewards (e.g. virtual meet and greet).Next stepsImplement status tiers using ERC-1155 tokens, allowing creators to offer tiered benefits to fans based on engagementBuild out more earning actions (e.g. answer poll, attend an event, etc.) and reward options (e.g. AMA, free event tickets, discount on merch)Creator dashboard to design and manage their rewards program

Solution

We used React, NextJS, and Express primarily. For authentication & handling Creator Coin (CC) transfers we used Rally.io's oAuth and APIs, and for smart contracts, we used Solidity/OpenZeppelin. We also minted an NFT on-chain (https://rinkeby.etherscan.io/address/0xf8a29c3006ee61a5724a708abc7b3c591fbb2783#code). We avoided setting up a real DB, just opting for an Airtable DB instead. We went with Rally's CC implementation and APIs because we wanted to make the product something that could actually be valuable to creators, and to-date the gas fees have made any form of rewards program untenable on Ethereum.Subscribe to earn - this just collects a fan's email address, rewarding them with CC for the submission and dropping the email into an AirtableRefer a friend to earn - we generate a unique referral link per-fan-per-creator. If another fan subscribes from a referral link, we automatically award points to the referrerNFT redemption - at the moment we're just minting an NFT on-chain on behalf of the creator when a fan selects the NFT redemption option. Next steps would probably be to either port over to an existing protocol like Rarible, or to continue investing in building out smart contracts to handle more sophisticated use cases (e.g. open editions, etc.)