1. Intro
Approaching our 4th auction, we are nearly 1/3 of the way through the period and it’s time we started discussing the badges we would like to create.
Deciding retroactive rewards requires having visibility on contributions, and badges provide a way to easily recognize how people have helped Botto. Financial rewards aside, this recognition is also valuable for tracking our invested efforts, building reputation, creating permissioned access, augmenting governance power, and enabling permissionless composability.
- Tracking invested efforts: In other words, gamifying the experience to promote valuable behaviour.
- Building reputation: When discussing topics, such as curation, you can see just how much someone has been voting and seen of Botto’s work
- Permissioned Access: This goes beyond roles on discord to deciding committees based on behaviour and gating those discussions.
- Augmenting Governance Power: Some have proposed hard working curators deserved more voting power for their continued dedication. These could enable that.
- Permissionless composability: SBTs are on the blockchain, so other protocol could use them as a mechanism for recruitment and services.
- Retroactive rewards: Easily see the different types of contributions and run automated accounting on different reward scenarios
2. How these badges should work:
At launch, most badges will be expanded versions of what we have set up in the onboarding bounties. This allows us to retroactively award badges for the whole period with relatively easy implementation and continuity of what we’ve already established as desirable behavior.
Most badges should be round-based, and renewed for a new round.
We will give a badge for onboarding, and badge levels will be beyond the onboarding qualifiers.
We also want to include other badges like for snapshot, and welcome other simple actions not already covered in onboarding bounties.
After launching this initial set, we will open up voting data for people to search for desirable behavior, and we can create a bounty for proposed badges that are accepted by the DAO.
Note: For calculating different levels of each badge, we used these reference numbers for Fragmentation Period:
Total Fragments: 1050 + 350*11 = 4900
Total rounds = 12
Total Days = 91 (extra week round 1)
3. Badge Types
Boosts
Level 1 - 15 (3 rounds)
Level 2 - 20 (⅓ of all rounds or 4 rounds)
Level 3 - 30 (½ of all rounds
Level 4 - 40 (⅔ of all rounds, or 8 rounds)
Level 5 - 60 (All 12 rounds boosted)
Consecutive days voted
Level 1 - 3
Level 2 - 7
Level 3 - 14
Level 4 - 30, 1/3
Level 5 - 45, 1/2
Level 6 - 60, 2/3
Level 7 - 91
Consecutive Rounds voted (not including boosting)
Level 1 - 3, ¼ of rounds
Level 2 - 6, ½ of rounds
Level 3 - 9, ¾ of rounds
Level 4 - 12, all rounds
VP spent on a single piece
Level 1 - 500VP
Level 2 - 1000VP
Level 3 - 10k VP
Level 4 - 100k VP
Level 5 - 1M VP
Number of fragments voted
Level 1 - 500
Level 2 - 750
Level 3 - 1225, or ¼
Level 4 - 2450, or½
Level 5 - 3674, or ¾
Level 6 - 4900
*based on total fragments in a 12 week period.
Voting on a winner
Level 1 - 2 rounds
Level 2 - 4, ⅓ of all rounds
Level 3 - 6, ½ of all rounds
Level 4 -8, ⅔ of all rounds
Level 5 - 12, All rounds boosted
Onboarding Badge for completing onboarding
Genesis Voter
Other badges to consider:
Voted in a snapshot -- should this be levels or per snapshot vote?
Ad-hoc support
- Successfully created a passed proposal (core team not eligible)
- Created a badge
- Collectors
- Etc.
4. Implementation
Naming and Art
For art we are thinking of making use of Botto Discards to decorate the badges. We have a sample idea for a 3d render of the discard fragments in a frame and presented with the anime of the badge. For simplicity, the team will have final discretion on naming and fragment selection, but we really appreciate suggestions!
Otterspace, L2
While we can do the full implementation ourselves, Otterspace offers a platform and support where they’ve designed for the particularities of SBTs. For instance, it is bad design to send SBTs, rather people need to opt-in to receiving them. We can still pay for them to be minted/sent rather than have users mint themselves. We would do it on an L2, Polygon or Optimism, that will allow us to keep costs down.
Definitely recommend checking out their site where they’ve done a very nice job of explaining the benefits and how their protocol works: https://otterspace.xyz/
Badge leaderboard and profiles
A view of how many people have reached each level can give a quick snapshot of the distribution of activity when considering retroactive rewards, and identify active contributors. Badges will also be added to people's profiles, though not necessarily at launch.
Retroactive rewards
**This is not part of this prop, but helpful to consider. The main point is that the proportions would be distributed not based on level, but on proportion of total for each category as we do with relative VP spent. The minimum requirement is having achieved the first level of a badge category, which creates a minimum threshold of activity and a barrier to entry for each category. **
The process could look like the following
- Set up a contest on JokeDAO, which allows for cheap, on-chain voting across up to 200 categories
- Voters can distribute their governance power across the badge categories to represent how they would like to see the retroactive rewards pool proportionately distributed.
- Having the badge leaderboard will provide useful info for making decisions. Would potentially want to open up data for this as well.
- The team will prepare an accounting of the final proportions (perhaps this could be a live accounting based on incoming votes, or show the last round’s proportions grow as the next rounds pool is added to)
- If the community voices they want to recast their votes after seeing the accounting, or rejects the proposal with the distributed accounting, the jokedao contest will be run again.
5. Timeline
Through December - Discussion and deliberation
- Source and discuss badge ideas and implications
- Determine naming and art
First week of January - Send to vote
Jan 5-19, 2 weeks for development
Jan 20th, launch when 10th auction closes
Not part of this prop:
Final retroactive rewards process
Opening up data and establishing badge bounty
