"When planning a membership system, we'll need to think about membership as bundles of access, permission, and status across these Web2 services."

"Having a token brings a community together loosely with a financial stake, but composable membership holds a community together long term with social capital"

"Put in a Web3 context, a group of people holding or trading the same token does not mean you are a community - at best, it gives you clusters."

"Access is discovery, permissions are responsibility, status is weight."

"This membership funnel is shaped different from the activity funnel above, as the customizable design area gets larger the deeper you go:"

"Access: For the most part, ERC20's are best for access because requirements are fluid and the tokens are more liquid."

"Permissions: I personally believe permissions should be tightly coupled to a stake. To be given the responsibility for some set of actions, there should be risk involved. Unlike access, permissions should evolve and can be revoked."

"Status: This layer has the largest area because it is tied to attributes and metadata. Status in a community has the highest amount of variance, as it will likely be event-dependent."

"aking the treasury ""weighted voting power"" example, if you give status based on what is being voted on that highlights specific community members while also ensuring that it isn't always the participant with the most tokens has the most sway."

"In Web2, membership forms around services. In Web3, services from around membership. Put simply, being a YouTube subscriber does not affect your privileges when engaging in a Twitch chat or a subreddit."

"This kind of membership interoperability is certainly possible in Web2, and I think Patreon was the closest to getting a hierarchical membership structure in place."

"In Web3, no one is fighting to be at the top of the membership hierarchy because the primitives (tokens) aren't owned by any one platform. Smart contracts are our APIs and we can code revenue splits right into them."

"They will be forced to fit around the composable membership systems that we all enable and create. In other words, the community is the platform:"

"There's an argument to be made that in the end, apps will just be a bunch of composable components where each piece is owned by a different platform."

"We'll define social capital as building an allowance for trust, experimentation, and flexibility within a community."

"This means having a membership system that improves ownership of decisions and prevents a social fork."

"Define Roles: Roles are bundles of the different layers of membership and are tied to specific participant personas."

"Doing this well opens up a pathway for growth and also clarity for all members. This starts to give us history too"

"Specify Incentivizes: Pet3rpan mentioned in the article linked earlier that trust and engagement are key to participation."

"Also, I cannot stress enough the importance of history here. Membership + Identity + Relationships will probably be the best proxy for a reputation score, which opens up the path to more creatively weighted incentives."

"Assign Roles: This step is more technically difficult than the others, given the challenge of plugging membership systems into existing platforms."

"as long as we have an identity solution (connecting addresses to user metadata across platforms) and a membership solution (managing roles and tokens intuitively), I think we'll be able to tackle the platform integration problem elegantly."

"Composable membership shapes more than just communities, it will shape ecosystems and platforms as well."

"Ecosystems are forming around metadata already, and this will force a reorganization of Web2 platforms to provide a much more open surface to be built upon."