Mtg and Lana meeting notes:

\- we need nostr public key to get the badge to someone

\- there will be a section on the profile showcasing badges that a maker can get from their activity

\- Do badges need to be filterable? We can categorize them in 2 groups: 1. badges that a maker CAN have 2. badges that a maker has gotten

\- Design: we need to design the badges that can be obtained through maker activity

\- Where do we display them? on the profile, maybe as the card. Do we display them in other profile components? For example on the post cards? We can showcase the number of badges a maker has

\- We display the special badges on the feed, for example when a maker gets a special badge for example, for the 100th story, or for hackathon achievement, it can show up on the feed as a story.

User journey - how badges get issued and show up on the profile: 

1\. an admin creates a badge 

2\. we give the badge a requirement 

3\. the badge is created, the user goes to section of the badges and sees all of them. 

4\. The maker did something or achieved some special award deserving of the badge. 

5\. How might we issue the badge to the public key if maker has multiple?

The user gets the badge: we do it automatically and send the notification or email to the admin. the admin goes to the external tool. Public key: we ask the user to send us the public key, on which they want to obtain the award. it's a one-time thing?

6\. We confirm the public key, by asking a maker to confirm the public key, and the admin goes to the badge page and links the key. 

7\. the maker sees the badge as their obtained badge. They should be able to share it.