---
# System prepended metadata

title: Suggestions for Membership and Contribution Management in PubDAO

---

# Suggestions for Membership and Contribution Management in PubDAO

***The discussion so far***
From what I gather, the goal here is to capture memberships (that enable / give access to *something*) and contributions (that trigger rewards or incentivise contributors in a way that makes them want to continue contributing).

As suggested by <@519376255309709322>, a membership pass (ERC721 or ERC1155) given to whitelisted addresses is the way to go. However, the frequency of issuance and criteria of issuance is not solidified.

***The PUB Token***
The utility of the PUB token is **voting** (it enables token holders who also have membership badges to vote, even vote in proportion their number of shares).

Another one is **access** (as stated in the example, access to token-gated PubDAO publications).

A third one is **rewards** (using DeWork's tokenised voucher for retroactive staking).

***A Suggestion***
I feel that for the above purposes, a token + POAPs + membership badges is not an optimal solution. A better solution would be having upgradable membership badges that also store members' contributions. This would work as follows:

**1. Setup clear membership levels and mobility criteria**
Capturing potential contributor's interest is key. By making them wait, we risk having them lose interest. Instead of deciding whether to let people buy tokens, receive it after doing work or waiting for it, we could have membership levels that range from, for example, newcomer or level 1 to core team or level 5, and then give a membership badge to anyone who comes. Engage them from day 1. 

**2. Using contributions or "Proofs-of-Work" to level up members**
By capturing member's work through contribution badges, you can easily create a mobility criteria we just discussed, which could look like: *x contributions take you to level y which unlocks z perks.*

**3. Use membership levels for context-based voting**
Upgradable membership badges can store not only membership levels, but also member categories. So you could enable context-based voting: for example level 4 folks in the operations forum will have a disproportionately higher say than, a level 2 person from the creators forum. Just an example, but this could customised as needed.

**4. Rewarding members**
By capturing member contributions through badges that are connected to their memberships, you can automate membership upgrades / downgrades and even retroactive pay your members easily. 

**5. Use these tokens to work with token-gated tools**
Since these badges would essentially be ERC721s, they would ideally work with your favourite web3 tools right out of the box.