Components Overview

Base Component

Cohort NFT (ERC 721) The Cohort is an NFT contract that extends the standard NFT on the blockchain. Each blockchain has a widely used Cohort NFT token deployed on it, and the Silicon blockchain also has a Cohort NFT issued by Silicon developers. Although anyone can issue a Cohort NFT token with the same functionality, it is recommended to use a common NFT to prevent ecosystem confusion.
Cohort Item A Partner can mint a Cohort Item for their community and define its basic attributes. One NFT Item represents one Cohort, and the membership and points for this Cohort are managed through a Manager. Most of the information, including basic attributes, is recorded in the Cohort Item, but the membership list is not stored on the blockchain. Instead, only the representative value of the list, the MerkleRootHash, is recorded.
Member A Partner can manage the membership list for their owned and minted Cohort Item through the Manager. When providing the membership list, Partners can choose between blockchain wallet addresses or a custom identity managed by them, and this decision is made when creating the Cohort Item. A Partner can have only one identity mapping, which means that the same custom identity must be used for the membership lists of all Cohort Items owned by that Partner. For more details, refer to 📄Address Identity. Members in a Cohort have membership status as well as additional point information. The points are managed by the Partner and are assigned based on the policies set by the Partner. The usage of points is determined by the Builder.

MerkleProof Component

Snapshot A Partner can request the creation of MerkleTree information to finalize their managed membership and upload it to the blockchain. The Manager generates the MerkleRootHash based on the Cohort membership list at the time of the request and asks the Partner for signature information required for Rollup. Once the correct signature is completed, the Manager delivers the MerkleTree information of the Cohort to the designated Prover. The Prover compiles the MerkleProof information and publicly provides the data needed for Rollup. The Snapshot includes nonce information and signature details, and the nonce must continue to increase to Rollup the Cohort data on-chain.
Rollup Rollup is the process of recording the MerkleRootHash, which is the representative value of large memberships managed by the OpenCohort system, on-chain. This significantly improves efficiency by allowing the blockchain to verify summarized data instead of processing individual memberships, minimizing the membership management costs for the Partner. This method plays a crucial role in expanding the blockchain’s processing capacity while maintaining security and decentralization. Data that is not Rolled-up cannot be used on-chain, and Snapshot information must be Rolled-up for it to be effectively used on the blockchain. With the Rollup Signature provided by the Prover, anyone can Rollup the Cohort Snapshot to the blockchain, not just the Partner. Cohort Items store records of all Snapshots, enabling the use of specific data from past points in time.

Airdrop Component

AirdropDeployer The data of various Partners managed on the blockchain through the OpenCohort system can be utilized in multiple ways, with one of the most representative use cases being Airdrop incentives through membership and point proof. OpenCohort supports various types of Airdrops utilizing Cohorts, allowing Users to claim incentives provided by Builders. The Airdrop Deployer developed by Silicon developers has been deployed on the Silicon blockchain and can be used by anyone with knowledge of the blockchain, including Builders and Airdrop Helpers.
Airdrop SBT (ERC 721 & ERC 5192) Airdrop is an NFT contract deployed on the blockchain that extends the standard NFT and implements the SoulBound Token (SBT) under the ERC-5192 standard. The Airdrop Contract supports four types of Airdrops (Weight, Count, Constant, Unit), enabling Builders to select the most suitable incentive model for their project and efficiently allocate incentive resources. Unlike Cohort NFTs, which use a single minted Item, Airdrops issue new Airdrop SBTs for each incentive setting. Partners can include users without blockchain wallets as Airdrop recipients through identity mapping. Additionally, users who generate wallets via Account Abstraction can claim Airdrop incentives without ETH for gas fees and deploy the Account Abstraction wallet on the blockchain simultaneously. This allows access to the blockchain even without initial assets, encouraging a wider variety of community users to easily enter the Web3 environment of OpenCohort.
Airdrop SBT Item An Airdrop SBT Item is automatically issued to users who receive a specific Airdrop incentive. This Airdrop SBT Item, issued to the user, serves as an on-chain record reflecting their activity and identity, and offers additional rewards beyond the Airdrop incentive. Furthermore, users who continuously contribute to the project and community can receive additional incentives based on their previously issued Airdrop SBT Items, promoting active participation and growth in the Web3 projects and communities, thereby fostering a positive feedback loop.

PreviousParticipants NextAddress & Identity

Last updated 16 days ago

Base Component

Cohort NFT (ERC 721) The Cohort is an NFT contract that extends the standard NFT on the blockchain. Each blockchain has a widely used Cohort NFT token deployed on it, and the Silicon blockchain also has a Cohort NFT issued by Silicon developers. Although anyone can issue a Cohort NFT token with the same functionality, it is recommended to use a common NFT to prevent ecosystem confusion.

Cohort Item A Partner can mint a Cohort Item for their community and define its basic attributes. One NFT Item represents one Cohort, and the membership and points for this Cohort are managed through a Manager. Most of the information, including basic attributes, is recorded in the Cohort Item, but the membership list is not stored on the blockchain. Instead, only the representative value of the list, the MerkleRootHash, is recorded.

Member A Partner can manage the membership list for their owned and minted Cohort Item through the Manager. When providing the membership list, Partners can choose between blockchain wallet addresses or a custom identity managed by them, and this decision is made when creating the Cohort Item. A Partner can have only one identity mapping, which means that the same custom identity must be used for the membership lists of all Cohort Items owned by that Partner. For more details, refer to 📄Address Identity. Members in a Cohort have membership status as well as additional point information. The points are managed by the Partner and are assigned based on the policies set by the Partner. The usage of points is determined by the Builder.

MerkleProof Component

Snapshot A Partner can request the creation of MerkleTree information to finalize their managed membership and upload it to the blockchain. The Manager generates the MerkleRootHash based on the Cohort membership list at the time of the request and asks the Partner for signature information required for Rollup. Once the correct signature is completed, the Manager delivers the MerkleTree information of the Cohort to the designated Prover. The Prover compiles the MerkleProof information and publicly provides the data needed for Rollup. The Snapshot includes nonce information and signature details, and the nonce must continue to increase to Rollup the Cohort data on-chain.

Rollup Rollup is the process of recording the MerkleRootHash, which is the representative value of large memberships managed by the OpenCohort system, on-chain. This significantly improves efficiency by allowing the blockchain to verify summarized data instead of processing individual memberships, minimizing the membership management costs for the Partner. This method plays a crucial role in expanding the blockchain’s processing capacity while maintaining security and decentralization. Data that is not Rolled-up cannot be used on-chain, and Snapshot information must be Rolled-up for it to be effectively used on the blockchain. With the Rollup Signature provided by the Prover, anyone can Rollup the Cohort Snapshot to the blockchain, not just the Partner. Cohort Items store records of all Snapshots, enabling the use of specific data from past points in time.

Airdrop Component

AirdropDeployer The data of various Partners managed on the blockchain through the OpenCohort system can be utilized in multiple ways, with one of the most representative use cases being Airdrop incentives through membership and point proof. OpenCohort supports various types of Airdrops utilizing Cohorts, allowing Users to claim incentives provided by Builders. The Airdrop Deployer developed by Silicon developers has been deployed on the Silicon blockchain and can be used by anyone with knowledge of the blockchain, including Builders and Airdrop Helpers.

Airdrop SBT (ERC 721 & ERC 5192) Airdrop is an NFT contract deployed on the blockchain that extends the standard NFT and implements the SoulBound Token (SBT) under the ERC-5192 standard. The Airdrop Contract supports four types of Airdrops (Weight, Count, Constant, Unit), enabling Builders to select the most suitable incentive model for their project and efficiently allocate incentive resources. Unlike Cohort NFTs, which use a single minted Item, Airdrops issue new Airdrop SBTs for each incentive setting. Partners can include users without blockchain wallets as Airdrop recipients through identity mapping. Additionally, users who generate wallets via Account Abstraction can claim Airdrop incentives without ETH for gas fees and deploy the Account Abstraction wallet on the blockchain simultaneously. This allows access to the blockchain even without initial assets, encouraging a wider variety of community users to easily enter the Web3 environment of OpenCohort.

Airdrop SBT Item An Airdrop SBT Item is automatically issued to users who receive a specific Airdrop incentive. This Airdrop SBT Item, issued to the user, serves as an on-chain record reflecting their activity and identity, and offers additional rewards beyond the Airdrop incentive. Furthermore, users who continuously contribute to the project and community can receive additional incentives based on their previously issued Airdrop SBT Items, promoting active participation and growth in the Web3 projects and communities, thereby fostering a positive feedback loop.