[H3] - M3MBER 🏅

We build ENS namewrapper (ERC-1155) & subname empowered membership protocol w/ onchain expiry. Inspired by the drawbacks of life-time payment nature of NFT or token release: expensive, and core team not incentivized to provide consistent service.

0
1

Challenges

Deploy your Dapp on Infura with MetaMask and Truffle Dashboard

Pool 1,000 USDC

We use Infura with MetaMask and Truffle Dashboard for our DApp.

Best Use of Existing Subgraph(s)

Ranked 4,500 USDC

Using ensgoerli subgraph - generate a lot of ens data for the visualization.

#BUIDLathon 2023 DAOs + Community Track

Pool 15,000 USDC

It's ENS namewrapper (ERC-1155) & subname empowered membership protocol w/on-chain expiry. It's beneficial as it introduced a new membership type - temporal, renewable membership, but on-chain - to DAO/Community that will benefit DAO/Community to build out more sustainability (recurring income for DAO) and more actively (only member constantly renew stay)

Project details

M3MBER

One-liner

ENS namewrapper (ERC-1155) & subname empowered membership protocol w/on-chain expiry.

Problem we solve

  • The one-time purchase nature of NFT/token leads to two main problems with membership: 1. High barrier of entry for the user as it’s expensive; 2. Lack of incentivization of the core team/community leaders to deliver consistent value as there are few recurring revenues

  • There is no standardized on-chain membership with expiry yet

Solution we buidl

  • A platform where the community leads & service providers can build subname membership of domain name. Here are the main features:

    • To the admin: can set up membership rules, can create a mint link for others to mint (profitable with mint price), airdrop and even bulk airdrop memberships, and also a management panel to overview all subname memberships.

    • To the user: can mint membership, can overview all of their membership, can extend, transfer, sell their membership.

  • An API (& SDK in the future) for DApp to build subname-gated interaction

    • API: https://m3-mber-eth-denver.vercel.app/api/m3mber_verify

    • Example: {address: “0xD9F8bf1F266E50Bb4dE528007f28c14bb7edaff7”, name:”parentname.eth”}

Why ENS Namewrapper?

  • It’s on-chain but with expiry!

  • Wide adoption of ENS (2.6 million registered) w/ many DApp adoption leads to better interoperability of ENS Subname too

  • Namewrapper allows parents to make rule-based expiry extension, and also makes subnames ownable and transferrable

Reference

  • Youtube: https://www.youtube.com/watch?v=I_polQxDzUQ (Pls check it out as it goes deep and holistic about our idea, platform, and API!)

  • Github: https://github.com/M3MBER-ETHDenver/M3MBER-ETHDenver

  • Demo URL: https://m3mber-ethdenver.vercel.app/ (Note that the namewrapper contract is updated the night before submission, so if you newly mint name on alpha.ens.domains (using v5 of namewrapper), you may not be able to use the platform (using v4 of namewrapper). We did not upgrade the smart contract because ensgoerli’s subgraph is not updated yet, so there will be data missed if we update to v5).

  • Mint a subname thru:

    • https://m3mber-ethdenver.vercel.app/join/dop3.eth

    • https://m3mber-ethdenver.vercel.app/join/degens.eth

    • https://m3mber-ethdenver.vercel.app/join/airports.eth