Hypercerts-Minter Fork

[psparacino]

The Hypercerts minter should be able to handle user flows for both chapter leads and chapter members.

The chapter lead (Lead) flow will have some minimal admin features in addition to minting hypercerts.

The chapter member (Member) flow will focus on minting hypercerts.

Features

Chapter Lead Stories

1. I want to be able to mint hypercerts for my chapter
2. I want my address to be whitelisted and associated with my chapter
3. When creating a hypercert I want my chapter info saved so I don't have to refill every field every time I want to mint a hc
4. I want to be able to recognize members by name, not only address.
5. I want to be able to add and remove members from my chapter.
6. I want to allow members to mint without needing a wallet (*nice to have)
7. I want a hypercert template for chapters (* less clear, bitbeckers for clarity)

Chapter Member Stories

1. I want to be recognized as belonging to my local chapter
2. I want to be able to recognize other members by name, not only address
3. I do not want to be required to use a wallet to mint hypercerts
4. I want a selection of hypercert templates (design element)

Page Features:

1. Separate user flows if wallet address is chapter lead or member
2. Member should ideally not need a wallet address to sign in. akin to: https://web3auth.io/

Chapter Lead Features:

1. Chapter information saved for minting
2. Can add or remove members from chapter. Should have names connected to addresses
3. Mint Hypercerts from app
4. Past hypercerts shown in app
5. Hypercerts template

Chapter Member Features:

1. Can apply to join chapter
2. Does not need wallet in order to connect
3. Mint Hypercerts from app
4. Past hypercerts shown in app
5. Hypercerts template

Designs: https://www.figma.com/file/uC0GYIDUgPDTcS7XbJcH9o/Wireframe-GPN-Hypercerts-app?type=design&node-id=0-1&mode=design&t=v638iRRggsqE065j-0

Possible stack and integrations:

• web3Auth / keyp (members)
• Gelato for gasless transactions (members)
• Supabase