𝗔𝗹𝗹𝗼𝘄𝗹𝗶𝘀𝘁𝘀 𝗥𝗲𝗻𝗲𝘄𝗲𝗱: 𝗧𝗵𝗲 𝗸𝗲𝘆𝘀 𝘁𝗼 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝘆 𝗼𝗽𝗲𝗿𝗮𝘁𝗶𝗼𝗻𝘀

Tokens were previously the primary means of co-ordination, but there are non-tokenized ways for decision-making and operations for communities.

Allowlists are one of them, see the best and newest usecases in this post:

guild.mirror.xyz/moQ1ub-ciwRv8yDfQC9mBJ9QomVS-dwJlrcCHb3qVZU

With Guild, allowlists can be:

• uploaded as requirements to getting rewards,
• created as outputs after a completed behavior,
• and exported for further use in more roles on Guild or in other applications.

Use them to: identify early adopters, create smaller workgroups, build onchain governance without tokens, and plan future rewards.

The Guild Model of Requirements, Roles and Rewards allows for building role structures around a set of requirements, including 𝗮𝗹𝗹𝗼𝘄𝗹𝗶𝘀𝘁𝘀.

”Be a core member and be on an allowlist to vote”

Allowlists always have been are a vital part of the toolkit of communities.

Guild's modular access management model helps builders to have more insight into who their members are and grants more agency over community functions.