Participants
Last updated
Was this helpful?
Last updated
Was this helpful?
OpenCohort involves a variety of participants. Understanding these entities, from the 'Silicon Blockchain' to 'Individual Users,' is essential for developing and applying the protocol. Based on this understanding, decide how you want to engage with OpenCohort.
The Silicon Blockchain is a key sponsor supporting the decentralized OpenCohort protocol. Through OpenCohort, Cohort NFTs based on the Silicon Blockchain are minted, and the Merkle Root Hash is stored. The Prover URI is recorded on the blockchain, and the incentive protocol that users receive for participating in the Cohort is also executed on the blockchain. Additionally, the Silicon Blockchain supports OpenNameTag to enhance the value of public address information.
The Manager is a decentralized service provider responsible for managing Cohort memberships. Key functions include:
Partners can add, modify, or snapshot their customer community and points in the Cohort following the Manager protocol.
Partners (typically) submit Identity Mapping Signatures through the Manager.
The Manager stores and manages membership and snapshot history for each Cohort.
The Manager generates the MerkleRootHash of the snapshot and collects information for rollups. The Manager may also perform the rollup.
The Manager provides finalized Cohort snapshot information, rollup information, and Identity Mapping details to the Prover.
The Prover plays a role in providing finalized Cohort information to users and the ecosystem in a static format. The Prover can be an API or a decentralized static file system.
Users can verify Prover information through the Cohort NFT recorded on the blockchain.
The Prover provides Proof of Cohort membership and points, which are proofs related to the Merkle Hash of a specific snapshot.
The Prover offers Identity Signatures provided by the Manager to users (users must be aware of their identity).
The Prover provides the Merkle Root Hash for the Cohort rollup, other attribute values, and the Partner's signature information. Anyone can use these signatures to roll up Cohort information on the blockchain.
The Prover provides dump forms of Proof information, snapshot membership data, and Identity Signature information, allowing anyone to query and verify the Merkle Tree.
Partners play a crucial role in expanding their customer (User) communities into the Web3 space. Through OpenCohort, Partners transparently manage memberships, communities, and identity verification while promoting community participation through incentives. They support a smooth transition and growth of their user community in Web3, encouraging interaction.
Partners can issue Cohort NFTs and manage multiple Cohorts (e.g., Best Player Cohort, Most Visitor Cohort, etc.).
Partners manage Cohort membership and points through the Manager.
Even if a user does not have a blockchain wallet, the Partner can manage the Cohort membership based on the user’s identity. However, only the Partner can determine whether the identity contains personal data, and OpenCohort and other participants are not responsible for the exposure of public data recorded on the blockchain.
Partners can trustlessly disclose Signature information that maps the provided identity to the blockchain wallet address where the actual incentive will be received.
Partners take snapshots of Cohort memberships and provide snapshot signature information. This signature information is used for blockchain rollups, and all snapshot history can be checked on the blockchain.
Builders play a central role in driving innovation in the Web3 ecosystem by using the OpenCohort protocol to create new projects and communities. Builders can release new projects (tokens or exclusive content) to designated users. They also form new user communities by strategically communicating with targeted users through promotions and incentives. The participants of Builder projects become the foundation for the continued growth of the project and ecosystem through a virtuous cycle of converting into new Cohorts.
Builders can perform airdrops to membership targets supplied by Partners. They can use the standard airdrop protocol or utilize the Airdrop Helper.
Builders can also conduct airdrops targeting past membership data.
Builders can offer incentives to Cohorts with assets other than their project assets.
Builders, being Partners who manage community memberships, can also use services that automatically manage platform community memberships into Cohorts.
Builders offer grants for membership information provided by Partners. Partners can receive grants from Builders as their community grows.
Through OpenCohort, users can express their identity and membership based on activities in games, media, social interactions, and more across Web2 and Web3 spaces, connecting with other users with similar interests. These social interactions facilitate the growth of Web3 communities and the foundation for new projects, fostering the growth of the Web3 ecosystem. Moreover, users create a positive feedback loop of active participation and growth in the Web3 ecosystem by earning benefits and incentives for their activities.
Users can earn blockchain-based incentives for their activity histories on various platforms.
The process centered around user memberships in the Web3 ecosystem through OpenCohort is as follows: each platform offers user activity-based membership as a Cohort through OpenCohort as a Partner. Builders provide incentives to the Cohort. Users can obtain Proof through the Prover or Identity Signatures as needed.
While OpenCohort provides various opportunities for all participants, it may be difficult for all users to easily understand and utilize the protocol. This is where the Airdrop Helper aids Builders interested in forming communities in Web3 to focus on their projects and activates the various Cohorts provided by Partners. Airdrop Helper can independently generate platform Cohorts as needed, encouraging more Builders to participate and leading the virtuous cycle of the ecosystem.
