bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 15쪽 중 2쪽
$100M USD loan backed by $200M of staked ETH collateral (200% overcollateralization) with hypothetical rates set below. 
| Parameter | Value |
| -------------------------- | ----- |
| USD unsecured borrow rate | 10% |
| USD risk-free rate | 4% |
| ETH unsecured lending rate | 4% |
| ETH native (PoS) yield | 3% |
**Flow of cashflows**
```
$10M from Borrower
├─→ $4M Lenders' minimum (risk-free rate on $100M)
├─→ $2M Underwriters' minimum (4% target on $200M − 3% native PoS)
└─→ $4M Excess Value (available for distribution)
```
Lenders earn the floating hurdle rate above the risk-free floor, Underwriters earn their negotiated premium above the 4% minimum, and the Excess Value is distributed by market pricing relative to the asset premium.
***
# Risks
Below are the main risks associated with Cap's current design.
**Smart Contract Risk:**
* Cap operates without reliance on third-party custodians, regulatory frameworks, or manual oversight. cUSD holder protections are enforced exclusively by code-based adherence to Cap’s protocol rules. While Cap’s smart contracts have been rigorously audits, users should be aware of risks associated with potential code vulnerabilities.
**Counterparty Risk:**
* **Shared Security Models**: Cap is built on Shared Security Marketplaces like EigenLayer. As such, it is exposed to their platform risk.
* **Reserve collateral**: If the reserve assets may depeg, users are exposed to these changes of price. Underlying reserve assets may also be frozen, seized or forfeited for illegal or sanctioned use.
* **Delegation collateral**: If the delegation assets are volatile (i.e. levered via looping), this increases the chance of liquidations as collateral value may fluctuate. Cap restricts the type of collateral to mitigate this risk.
* **Bridge and Oracle Risk**: If users wish to interact with cUSD from any chain, they will be exposed to the risk of third-party bridges that transfer cUSD from Ethereum and oracles that price cUSD.
* **Idle Asset Risk**: Idle assets may be deposited into integrated protocols such as Aave and Morpho until they are borrowed. As such, Cap is exposed to these protocol risks.
**cUSD Depeg Risk:**
* A force majeure event may create a mismatch between cUSD and the reserve assets. However, the highly liquid and regulated nature of the reserve assets render this unlikely.
**Protocol Risk:**
* **Redemption Risk:** Redemptions are guaranteed at all times for cUSD holders. However, redemptions may be delayed if the reserve assets are fully utilized. Dynamic interest rates prevent full utilization, always ensuring liquidity to be withdrawn atomically.
* **Liquidation Risk:** Malicious or undercollateralized Borrowers put Underwriters in liquidation risk. However, Underwriters can preemptively mitigate these risks, due to the fact that Borrowers in Cap are whitelisted regulated financial institutions.
* **Guarantor Agreements**: Underwriters are able to sign off-chain Guarantor Agreements (GAs) with their counterparties. These agreements can specify recourse provision, loan terms, and strategy constraints. Hence, the chance of an actual liquidation event is equivalent to these regulated entities filing for bankruptcy.
* **Quantifying risk**: It is possible to model the risk premium via credit spread. Particularly, the [return per unit of risk](https://docs.google.com/spreadsheets/d/1D04AYjvRBMCg09kSLpL8yN94tSrCpVhD8lBBT9037R4/edit?gid=0#gid=0) can be measured based on the institution's credit ratings, credit spread and default rates.
# FAQs
## Borrower Control and Restrictions
**Q: Do Borrowers have full control over collateral once disbursed?**
No. The Borrower set will be comprised of regulated financial institutions that enter into legal agreements with Underwriters to restrict permissible strategies.
**Q. How does the protocol ensure there are no risky strategies?**
Underwriters bear direct risk for their delegation choices. By underwriting specific Borrowers, Underwriters incentivize due diligence on strategy viability.
**Q: Are there caps on collateral lent to Borrowers?**
Yes. Delegation limits and nominal exposure thresholds prevent concentration risk.
## Loan Security
**Q: Does the protocol impose minimum overcollateralization requirements on Underwriters?**
Yes, the protocol checks the collateralization ratio before the Borrower can borrow. The overcollateralization ratio is different for every collateral asset and is set conservatively to prevent any unexpected liquidations.
**Q: Which assets are accepted as Underwriter collateral?**
Only blue-chip cryptocurrencies: ETH, wBTC, Liquid Staking Tokens (LSTs), and stablecoins.
**Q: What happens if Underwriters withdraw their delegation mid-loan?**
Underwriters and Borrowers should have a prior agreement when Underwriters intend to remove delegation for position unwinding. Unilateral withdrawals will trigger liquidation. Note that there is a built-in buffer period in Shared Security Networks to mitigate an accidental withdrawal.
## Shared Security Network
**Q. How is Liquidation and Redistribution used in Cap?**
Malicious or undercollateralized Borrowers are autonomously liquidated, where Underwriter delegations are redistributed back to the Lenders.
**Q. How does Cap differ from other restaking protocols?**
Cap replaces passive Proof-of-Stake rewards with productivity-based incentives:
* Underwriters earn premiums tied to Borrower performance.
* Borrowers retain surplus yield, fostering competitive strategy innovation.
Cap takes an innovative approach of rewarding Underwriters on a Borrower basis, where counterparty risk is established one-to-one with the Borrower they are underwriting. This architecture allows Borrowers to take more agency and be rewarded for their productivity.
For details, please check out our [Productivity Based Incentives](https://mirror.xyz/0x83c21bb4Bf0EC116f5a1945AaeF847Fe3b321B32/Xg7gCAqgmcxgXhuwaWXVJDSCEIMn3_dewNWAie2Tn_k) article.
# Tokenomics
### Overview
$CAP is the governance and utility token of Cap with a fixed supply of 10 billion tokens. Token holders' governance rights will be phased as the protocol matures.\
\
Revenue generated will be used to conduct discretionary buybacks
***
#### Token Allocation
| Allocation | % of Supply |
| --------------------- | ----------- |
| Ecosystem & Community | 47.37% |
| Private Investors | ≤20.00% |
| Project Team | ≤20.00% |
| ICO | 5.00% |
| Private TVL Deals | 3.75% |
| Echo Community Sale | 3.28% |
| Market Makers | 0.6% |
***
#### Supply Schedule
The circulating supply at TGE consists of the ICO allocation and 10% from the Ecosystem & Community allocation, summing up to roughly 15% of total supply.
Cliff-gated allocations (Private Investors, Project Team, Echo Community Sale) commence unlocking 12 months post-TGE. 25% of the allocation unlock at the one year anniversary of TGE, followed by linear monthly vesting for 3 years.
# Borrower Onboarding
The following outlines the process for onboarding as a Borrower to borrow from Cap.
### 1. Requirements
* **Borrower Address**: A valid Ethereum address (EOA or multisig) to borrow
* **Underwriter**: Entity that provides credit for the Borrower. The list of current Underwriters can be found [here](https://cap.app/underwriters).
* **Borrower Parameters:**
* **Underwriting Premium**: Fixed premium rate on the amount borrowed
* **LTV**: Loan-to-Value ratio for initial maximum borrow capacity
* **Protocol Whitelisting**: The Borrower must be whitelisted by the system.
{% hint style="info" %}
A Borrower may only use one Ethereum address per Underwriter and collateral pair. They must generate a new address for each new Underwriter. Addresses cannot be changed after deployment. For best practices, we recommend using a multisig for the address.
{% endhint %}
### 2. Register to a SSN of choice
Currently, Cap supports the following Shared Security Networks.
1. [Symbiotic](/guides/borrower-onboarding/symbiotic)
2. [EigenLayer](/guides/borrower-onboarding/eigenlayer)
### 3. Complete Legal Agreements (Optional)
Borrowers and Underwriters may enter into legal agreements outlining terms of delegation, responsibilities, and compliance.
### 4. Participate in Loan Activity
Once coverage is active from the respective shared security network, Borrowers can participate in borrowing activity directly from Cap's application using the Borrower's address.
Review the risk parameters prior to loan:
* **LTV (Loan-to-Value)**: Maximum borrowing capacity (e.g., 50% = 0.5e27)
* **Maximum Borrow Amount:** Coverage x LTV
* **Liquidation Threshold**: Health factor at which liquidation can occur (e.g., 80% = 0.8e27)
* **LTV Buffer**: Minimum gap between LTV and liquidation threshold (10% = 0.05e27)
{% hint style="info" %}
While the liquidation threshold is a global parameter, the LTV can be set by the Borrower-Underwriter Pair
{% endhint %}
### 5. Updating Parameters
To update the Underwriting Premium or the LTV for the Borrower, request a change to the Cap team.
Namely, the underwriting premium can be updated via the [setRestakerRate](https://github.com/cap-labs-dev/cap-contracts/blob/1064b6a969d55c822dcf0b2c4b733ceb4118737e/contracts/delegation/Delegation.sol) function, and the LTV and LT via the [modifyAgent](https://github.com/cap-labs-dev/cap-contracts/blob/1064b6a969d55c822dcf0b2c4b733ceb4118737e/contracts/delegation/Delegation.sol#L97) function.
# Symbiotic
The following is the onboarding guide for Borrowers (referred to as *agents* in Cap contracts). The onboarding flow has been mostly automated for the Borrower — the Underwriter can handle most bulk work when deploying an instance of the [Symbiotic Vault Factory](https://github.com/cap-labs-dev/cap-contracts/blob/1064b6a969d55c822dcf0b2c4b733ceb4118737e/contracts/delegation/providers/symbiotic/CapSymbioticVaultFactory.sol#L57) contract.
Steps:
1. Once agreements have been arranged with the Underwriter of choice, provide the Borrower's Ethereum address to the Underwriter. The Underwriter will then create the Borrower-specific Symbiotic Vault
* After receiving the delegations from the Underwriter, the Borrower is now eligible to borrow. Note, Delegations will take up to 6 days to be effective stake.
{% hint style="warning" %}
To isolate liquidation risk, each Borrower can only receive effective stake from one Symbiotic Vault. Delegations from other Vaults will not count as collateral. The Borrower must create a new address for each new Vault.
{% endhint %}
Under the hood, the following steps happen:
1. The Underwriter first creates a vault via the [CapSymbioticVaultFactory](https://github.com/cap-labs-dev/cap-contracts/blob/1064b6a969d55c822dcf0b2c4b733ceb4118737e/contracts/delegation/providers/symbiotic/CapSymbioticVaultFactory.sol#L57) including the Borrower address. The call will register the Borrower as SymbioticOperator in Symbiotic's [Operator Registry](https://docs.symbiotic.fi/modules/registries/#2-operatorregistry) and complete the [Operator to Network Opt-in](https://docs.symbiotic.fi/modules/registries/#2-operator-to-network-opt-in) and [Operator to Vault Opt-in](https://github.com/cap-labs-dev/cap-contracts/blob/main/contracts/delegation/providers/symbiotic/SymbioticNetwork.sol#L77) process via the [SymbioticOperator](https://github.com/cap-labs-dev/cap-contracts/blob/1064b6a969d55c822dcf0b2c4b733ceb4118737e/contracts/delegation/providers/symbiotic/SymbioticOperator.sol#L4) contract.
2. Once the Vault is deployed, Cap will register the Borrower to Cap's system via the [addAgent](https://github.com/cap-labs-dev/cap-contracts/blob/1064b6a969d55c822dcf0b2c4b733ceb4118737e/contracts/interfaces/ISymbioticAgentManager.sol#L45) function. The function takes in the following struct:
```solidity
struct AgentConfig {
address agent;
address vault;
address rewarder;
uint256 ltv;
uint256 liquidationThreshold;
uint256 delegationRate;
}
```
This function will add the Borrower to the [Delegation](https://github.com/cap-labs-dev/cap-contracts/blob/1064b6a969d55c822dcf0b2c4b733ceb4118737e/contracts/delegation/Delegation.sol) contract, register the Vault and Borrower to Cap's [Symbiotic Network Middleware](https://github.com/cap-labs-dev/cap-contracts/blob/1064b6a969d55c822dcf0b2c4b733ceb4118737e/contracts/delegation/providers/symbiotic/SymbioticNetworkMiddleware.sol) and set underwriting premiums.
After stake becomes effective, Borrowers can start borrowing via the Asset page on Cap's app.
### Understanding Epochs
To be compatible with [Symbiotic's epoch model](https://docs.symbiotic.fi/learn/core-concepts/network#epoch), Cap has its own epoch system built. As a result, there are checkpoints where Cap reads stake from Symbiotic Vaults. The checkpoints are updated every 6 days, or when there is a borrow event. 
Functionally, this means that when Borrowers first receive stake, they cannot initiate a borrow until past the next Cap epoch.
### Verifying the Vault
Once the Symbiotic Vault is deployed, Borrowers may verify the deployment status via the [Delegation](https://etherscan.io/address/0x09A3976d8D63728d20DCDFEe1e531C206Ba91225#readProxyContract) and [Symbiotic Network](https://etherscan.io/address/0x98e52Ea7578F2088c152E81b17A9a459bF089f2a#readProxyContract) Contracts. Use the \_agent field to input the Borrower's Ethereum address.
* Delegation contract methods:
* Collateral: delegation asset address
* Coverage: how much stake is live
* Vaults: the Borrower-Underwriter specific Symbiotic Vault
* LTV: the max borrowable loan-to-value ratio
* liquidationThreshold
* Symbiotic Network methods:
* getOperator: get SymbioticOperator address for Borrower address
### Managing the Symbiotic App
Once registered, the Borrower profile will be updated in [Symbiotic's app page](https://app.symbiotic.fi/networks). If you wish to change the metadata on the app, please refer to [Symbiotic' guide](https://github.com/symbioticfi/metadata-mainnet) to do so.
# EigenLayer
The following is the onboarding guide for Borrowers (referred to as *agents* or *operators* in EigenLayer contracts) using EigenLayer. The process is fully automated by the Cap system via the [EigenAgentManager](https://github.com/cap-labs-dev/cap-contracts/blob/main/contracts/delegation/providers/eigenlayer/EigenAgentManager.sol) contract.
### 1. Submit AgentConfig information to the Cap team
This is the only action a Borrower needs to take. The rest of the process is handled on behalf of the Borrower.
```solidity
struct AgentConfig {
address agent; // Your agent/borrower address
address strategy; // EigenLayer strategy address (e.g., wstETH)
address restaker; // Address of the Underwriter who will delegate to you
string avsMetadata; // AVS metadata URI (can be empty string)
string operatorMetadata; // Operator metadata URI (can be empty string)
uint256 ltv; // Loan-to-Value ratio (e.g., 5e26 for 50%)
uint256 liquidationThreshold; // Liquidation threshold (e.g., 8e26 for 80%)
uint256 delegationRate; // Underwriting premium for rewards (e.g., 2e25 for 2%)
}
```
{% hint style="warning" %}
The Borrower must use a new address for each new Underwriter. The Borrower **cannot** delegate to other AVSs.
{% endhint %}
### 2. Agent Registration
Cap's Admin registers the Agent to both EigenLayer and Cap via the [addEigenAgent](https://github.com/cap-labs-dev/cap-contracts/blob/main/contracts/delegation/providers/eigenlayer/EigenAgentManager.sol#L44) function.
Specifically, the function performs the following:
* Registers Agent to Cap via [addAgent](https://github.com/cap-labs-dev/cap-contracts/blob/1064b6a969d55c822dcf0b2c4b733ceb4118737e/contracts/interfaces/ISymbioticAgentManager.sol#L45) function in the Delegation contract
* Deploys [EigenOperator](https://github.com/cap-labs-dev/cap-contracts/blob/main/contracts/delegation/providers/eigenlayer/EigenOperator.sol) beacon proxy which handles
* Registering to EigenLayer's DelegationManager
* Creating and registering to a new Operator Set in EigenLayer's AllocationManager
* Setting Operator AVS reward split 0%
* Allowlisting TOTP digest for Underwriters (valid for 28 days)
Once registered, you will have an EigenOperator proxy address and an Operator Set ID for the Cap AVS.
### 3. Allocation
After registration, there is a **17.5** day delay of the allocation configuration for EigenLayer. In this time, Underwriters cannot delegate to the EigenOperator and as such, Borrowers cannot participate in loan activities. This is because allocation magnitude cannot be updated prior to this allocation configuration delay period.
After the delay period, Borrowers can allocate delegated collateral to Cap so that it counts as effective coverage, via the permissionless [allocate](https://github.com/cap-labs-dev/cap-contracts/blob/main/contracts/delegation/providers/eigenlayer/EigenServiceManager.sol#L227) function. Adding and withdrawing collateral after this time is now instant.
Once coverage is live, Borrowers can now borrow against delegated collateral.
{% hint style="info" %}
If allocation or delegation fails, make sure the TOTP is updated via the [advanceTotp](https://github.com/cap-labs-dev/cap-contracts/blob/main/contracts/delegation/providers/eigenlayer/EigenOperator.sol#L105) function.
{% endhint %}
### 4. Verifying Information
* Agent Registration:
* IDelegation(delegation).agentData(agent).network should return EigenServiceManager's address
* Agent Config:
* IDelegation(delegation).agentData(agent)
* EigenOperator Deployment:
* IEigenServiceManager(eigenServiceManager).getEigenOperator(agent)
* Operator address:
* IEigenOperator(eigenOperator).operator()
* Underwriter address:
* IEigenOperator(eigenOperator).restaker()
* Current Coverage:
* IEigenServiceManager(eigenServiceManager).coverage(agent)
* TOTP expiry:
* IEigenOperator(eigenOperator).getCurrentTotpExpiryTimestamp()
### 5. Updating Metadata
Borrowers can update operator metadata at any time via the [updateOperatorMetadataURI](https://github.com/cap-labs-dev/cap-contracts/blob/main/contracts/delegation/providers/eigenlayer/EigenOperator.sol#L98). Please reach out to the Cap team if you are unable to host the metadata.
# Underwriter Onboarding
The following outlines the process for onboarding Underwriters to Shared Security Networks (SSNs) in Cap's protocol. Onboarded Underwriters may delegate to Borrowers approved in the Cap system.
### 1. Setup
Ensure you have:
* **Borrower Address:** Borrower's Ethereum address that will receive delegations. The Borrower must be already registered in Cap's system. The list of current Underwriters can be found [here](https://cap.app/borrowers).
* **Underwriting Premium**: Agree on a fixed rate to receive from the Borrower
* **Collateral Asset:** The asset to be used as vault collateral (ETH/BTC-denominated ERC20s)
### 2. Choose SSN
Select SSN of choice for delegations, and follow the corresponding onboarding guide to complete set up and start delegating.
1. [Symbiotic](/guides/underwriter-onboarding/symbiotic)
2. [EigenLayer](/guides/underwriter-onboarding/eigenlayer)
Collateral management, i.e. delegations and withdrawals, are handled within each SSN. Underwriters are advised to monitor delay periods specific to the SSN.
{% hint style="danger" %}
Withdrawing delegations immediately lowers coverage. Delegated assets in the withdrawal queue are liquidatable until the end of the withdrawal delay. Hence, a withdrawal below the liquidation threshold makes the delegation asset liquidatable.
{% endhint %}
While a time buffer is in place to mitigate risk, it is recommended that Underwriters whitelist depositors to prevent malicious/accidental withdrawals that may trigger unintended liquidation.
### 3. Complete Legal Agreements (Optional)
Borrowers and Underwriters may enter into legal agreements outlining terms of delegation, responsibilities, and compliance.
##프로젝트로 돌아가기