Participants & Roles
The Credit Coop Protocol V2 has three participant types: Vault Depositors, Vault Curators, and Borrowers. Each interacts with the Protocol through the Interface in a distinct capacity.
Vault Depositors
Vault Depositors supply Digital Assets to Vaults through the Interface. Vaults are non-custodial pooled smart contract structures that allocate capital across Credit Lines and sources of liquid asset yield.
CMBT Labs does not hold, control, or have access to deposited Digital Assets at any time.
Upon deposit, Vault Depositors receive Vault Tokens representing their pro rata participation in the Vault. Vault Tokens are redeemable for the underlying stablecoin, subject to available liquidity in the Vault.
Vault Curators
Vault Curators manage a Vault by determining how capital is allocated across Credit Lines and sources of liquid asset yield.
Curator responsibilities include:
Approving borrower deployments within the Vault
Setting facility parameters, including credit limits and collateral requirements
Processing deposit and redemption requests
CMBT Labs does not exercise discretion over capital allocation decisions made by Curators. All Curator actions are executed via smart contracts. Curator obligations are further governed by any applicable Vault Curator Agreement.
Borrowers
Borrowers access Digital Assets through one or more Credit Lines via the Interface.
As a Borrower, you are solely responsible for:
Setting collateral and Credit Line parameters in line with the risks you are willing to accept
Monitoring the Collateral Ratio of each Credit Line on an ongoing basis
Repaying each Credit Line in full before its Due Date
To avoid liquidation, you may need to deposit additional Collateral and/or repay from Reserves if your Collateral Ratio approaches the applicable minimum threshold. If the Collateral Ratio falls below that threshold, liquidation of Collateral and Reserves will be authorised in accordance with the liquidation mechanics described in the Servicer & Liquidation section.
Borrowers may also configure Revenue Contracts as a repayment source through the Spigot smart contract.
Important: All transactions executed through the Interface are irreversible and final. You are responsible for carrying out your own due diligence before interacting with the Protocol.
Last updated
Was this helpful?