Badges V2 - main planning ticket

[joelamouche]

Following discussion here: #167

Here are some of the thoughts that led to this decision:

• Most of the badges right now come from the Guild and are based on contributions, almost no peer issued badges
• It seems a lot of Guild members are looking to learn, practice skills, gain experience
• We should guide users with a clearer learning path by providing event and aggregated skill badges
• I heard OSS contributors like leaderboards so maybe we should gamify the Guild experience more.
• We have low engagement on badge creation and curation

We will introduce 4 types of badges:

• Peer badge: competence label, attested by a peer (so what we had before basically)
• Guild Contribution badge: This badge is on a per PR/issue basis and represents contribution to the Guild, issued by The Guild
• Guild Skill badge: aggregated/computed badge, attested by the system. So for example 1 PR with rust gives you Rust lvl1 badge and 3 PRs give you Rust lvl 2 and FE contrib+BE contrib+Smart contract contrib gives you Web3 Full Stack dev badge.
• Guild Event badges: Guild issued, time based badge. Such as "Number 1 contributor February 2026" or even better if we can organize Hackathons.

What I think we shouldn't include in V2:

I think we should postpone introducing external contributions into the system formally because if we do then we decide to figure out how to incentivize members to review those. For now if there are any they should be handled by the Peer badges.

I think we should also postpone the implementation of Badge hierachy/knowledge tree because we have seen little engagement by members on badge creation so far and it seems a Guild led knowledge structure is preferable at this point.

In the same spirit, TCR on badge names should be defered because we have low engagement on badge creation and curation.