Cap(CAP)

Cap is a decentralized credit protocol built around a stablecoin system and on-chain lending mechanics. Its documentation describes cUSD as the main stablecoin vault, stcUSD as a yield-bearing staked version of cUSD, and CAP as the protocol’s governance and utility token.

Key facts#

• Project: Cap
• Token: CAP
• Network: Ethereum
• Main protocol assets: cUSD and stcUSD
• Core use case: On-chain credit backed by collateral, underwriting, and financial guarantees
• Source reference: https://docs.cap.app/resources/whitepaper
• CAP supply: Fixed supply of 10 billion tokens according to Cap documentation
• Governance: CAP governance rights are described as phased in as the protocol matures

Cap’s system is organized around a vault structure. Users deposit whitelisted backing assets to mint cUSD. The protocol documentation states that cUSD supply is backed 1:1, plus protocol fees, by a basket of approved backing assets. cUSD can be burned or redeemed to withdraw assets according to the vault rules.

stcUSD is the staked version of cUSD. It is described as an ERC4626 vault where users deposit cUSD and receive shares. Protocol yield is distributed to stcUSD holders through a profit-locking process, which spreads newly received yield over a set lock duration instead of recognizing it all at once. This design is intended to reduce short-term manipulation around yield notifications.

Cap also includes a fee auction module. Protocol fees are collected, then sold through permissionless Dutch auctions. Buyers pay in cUSD, and the proceeds are routed to the fee receiver so that cUSD can be distributed to stcUSD holders.

The CAP token is separate from cUSD and stcUSD. CAP has a fixed 10 billion token supply and is used for governance and protocol utility as defined by Cap’s documentation. Token allocations include ecosystem and community, private investors, project team, ICO, private TVL deals, Echo community sale, and market makers.

Cap is best understood as a DeFi credit protocol rather than a general-purpose blockchain. Its main design question is whether on-chain vault mechanics, underwriters, guarantees, and fee distribution can support transparent credit activity while controlling risk.

Cap Introduction#

Cap is an Ethereum-based credit protocol focused on issuing and managing credit through on-chain stablecoin infrastructure. The project’s documentation describes Cap as a credit platform backed by financial guarantees, with a system built around cUSD, stcUSD, lending mechanics, underwriting, fee auctions, and the CAP governance and utility token. Cap — Cap (CAP) is a cryptocurrency and operates on the Ethereum p…

Cap is not a separate Layer 1 blockchain. It operates through smart contracts on Ethereum and uses contract modules for vault management, minting, fractional reserves, lending, fee auctions, delegation, oracles, and access controls. The protocol’s core asset is cUSD, a stablecoin described as being backed by whitelisted assets held in the vault system. stcUSD is the staked form of cUSD and represents a claim on cUSD deposited into an ERC4626 vault that receives protocol yield.

The project is positioned around “verifiable credit,” meaning that core credit mechanics are expressed through contracts and source-visible protocol processes rather than only private accounting. This does not remove credit risk, smart contract risk, liquidity risk, or governance risk. It does mean that key system rules, such as minting, burning, fee auctions, interest harvesting, and yield distribution, are designed to be observable on-chain.

The CAP token is distinct from cUSD and stcUSD. CAP is the governance and utility token of the Cap protocol, with a fixed supply of 10 billion tokens according to Cap’s tokenomics documentation. Governance rights are described as phased as the protocol matures. Revenue generated by the protocol is described as being used for discretionary buybacks, but that statement is not a guarantee of token value, future demand, or market performance.

Source reference: https://docs.cap.app/resources/whitepaper

Part 1: Whitepaper Review#

Cap’s documentation describes a credit protocol where stablecoin issuance, lending, underwriting, and fee distribution are combined into a single DeFi system. The whitepaper and related docs place cUSD at the center of the design. cUSD is presented as the protocol’s stablecoin vault token. Users mint it by depositing approved backing assets, and they burn or redeem it to withdraw backing assets according to vault rules.

The cUSD contract is described as a UUPS upgradeable ERC20 that inherits vault, minter, and fractional reserve modules. The documentation says cUSD supply is backed 1:1, plus protocol fees, by a basket of whitelisted backing assets. The vault module manages supply, so the documentation specifies that there is no direct admin mint or burn function for cUSD outside the defined supply-management process.

stcUSD is the protocol’s staked version of cUSD. It is an ERC4626 vault that accepts cUSD deposits and issues shares. Yield accrues when the lending system realizes vault interest and transfers cUSD to the stcUSD contract. The documentation highlights a profit-locking mechanism: newly notified yield vests linearly over a configured lock duration. This is important because it reduces the chance that a user can enter the vault immediately before a yield event, capture an unfair share, and exit quickly.

The fee auction module is another key part of the system. Cap’s docs describe permissionless Dutch auctions where accumulated protocol fees are sold to the winning bidder. The auction buyer pays in cUSD. Auction proceeds are sent to the fee receiver, which converts and distributes value to stcUSD holders. The Dutch auction price decays over time, with documentation noting that auctions use a starting price, duration, minimum start price, payment token, recipient, and multiplier for the next auction’s starting price.

Cap also includes underwriting mechanics and financial guarantees. The documentation index references borrower onboarding, underwriter onboarding, shared security networks, and integrations or guides for systems such as Symbiotic and EigenLayer. These materials show that Cap’s credit model is not limited to a simple collateral vault. It also depends on underwriters and guarantee structures that help define how credit exposure is created, monitored, and covered.

Tokenomics are described for CAP. The token has a fixed supply of 10 billion. Allocation categories include ecosystem and community at 47.37%, private investors at up to 20%, project team at up to 20%, ICO at 5%, private TVL deals at 3.75%, Echo community sale at 3.28%, and market makers at 0.6%. The documentation states that the circulating supply at token generation consists of the ICO allocation plus 10% from the ecosystem and community allocation, totaling roughly 15% of total supply. Cliff-gated allocations for private investors, the project team, and the Echo community sale begin unlocking 12 months after token generation. At the one-year point, 25% of those allocations unlock, followed by linear monthly vesting for three years.

Part 2: Analysis#

Cap’s design can be understood as an attempt to bring structured credit mechanics into DeFi while keeping important parts of the accounting and distribution process visible through smart contracts. In simpler DeFi lending markets, users supply assets and borrowers take overcollateralized loans. Cap’s documentation points to a broader credit design with borrower onboarding, underwriter onboarding, guarantees, lending mechanics, and stablecoin vault operations.

The most important distinction for users is the difference between CAP, cUSD, and stcUSD. CAP is the governance and utility token. cUSD is the stablecoin vault token. stcUSD is the staked ERC4626 vault share that receives cUSD yield flows. Confusing these assets can lead to a poor understanding of risk. Holding CAP is not the same as holding cUSD. Holding cUSD is not the same as holding stcUSD. Each asset has its own role, risk exposure, and economic design.

cUSD depends on the quality, valuation, liquidity, and management of whitelisted backing assets. If backing assets lose value, become difficult to trade, face oracle issues, or become subject to governance changes, the stability assumptions around cUSD are affected. The documentation states that the cUSD price is based on the weighted average of underlying asset values via a CapTokenAdapter. That makes oracle design and asset selection central to the system.

stcUSD introduces another layer. It does not only represent cUSD exposure; it also participates in protocol yield distribution. The profit-locking design is a risk control. By vesting notified yield over time, the protocol aims to make share pricing less exposed to flashloan-style timing attacks. However, profit locking does not remove the underlying risks of the lending system, collateral system, borrower behavior, smart contracts, or governance decisions.

The fee auction process is an interesting part of Cap’s value routing. Rather than distributing every collected asset directly, the protocol sells accumulated fees through a Dutch auction. The buyer receives the auctioned assets and pays cUSD. That cUSD is routed to the fee receiver for distribution to stcUSD holders. This creates a market-based process for converting fee assets into cUSD, but it also depends on auction participation, fair pricing, and correct contract behavior.

From a risk perspective, Cap sits in a category where transparency does not equal safety. On-chain accounting can make flows easier to inspect, but the protocol still has technical, market, operational, and governance dependencies. Users need to understand the role of financial guarantees, the specific rights of underwriters, how borrowers are onboarded, how liquidations work, which assets back cUSD, and how access controls can change over time.

CAP tokenomics are more detailed than many early-stage projects because the documentation provides supply, allocation, and vesting information. The fixed supply of 10 billion gives a clear cap on token issuance, but allocation and unlock timing matter for market structure. Large cliff and vesting schedules can influence circulating supply over time. That is an informational point, not a price forecast.

Cap’s strongest educational takeaway is that modern DeFi credit protocols often separate governance tokens, stable-value assets, and yield-bearing vault receipts. CAP, cUSD, and stcUSD each represent a different part of the system. Evaluating Cap means reading those components separately, then studying how they interact through lending, fee auctions, oracles, and governance.

Internal Linking Section#

Readers new to Cap can start by reviewing how smart contracts and tokens work on Ethereum, since Cap is deployed on Ethereum. For broader context on crypto collateral and base assets, ChainClarity’s Bitcoin explanation gives useful background on the asset that shaped crypto’s monetary design. Users comparing DeFi ecosystems can also review Solana and Avalanche to understand how different networks approach throughput, fees, and application design.

Cap is most closely related to DeFi credit, stablecoin vaults, staking vaults, and governance-token design. It is not just a token listing. Its documentation describes a multi-contract credit system with minting, burning, auctions, yield routing, access controls, oracles, borrower onboarding, underwriter onboarding, and token vesting.

FAQ#

Q: What is Cap?

A: Cap is an Ethereum-based DeFi credit protocol built around cUSD, stcUSD, lending mechanics, underwriting, fee auctions, and the CAP governance and utility token.

Q: What is CAP used for?

A: CAP is described by the project as the governance and utility token of Cap. Governance rights are phased as the protocol matures, according to the documentation.

Q: What is cUSD?

A: cUSD is Cap’s stablecoin vault token. The documentation says it is minted by depositing whitelisted backing assets and burned or redeemed to withdraw backing assets through vault rules.

Q: What is stcUSD?

A: stcUSD is the staked version of cUSD. It is an ERC4626 vault share that receives yield distributed through the protocol’s fee and lending flows.

Q: How does Cap distribute protocol fees?

A: Cap uses a fee auction module. Accumulated fees are sold in a Dutch auction, buyers pay in cUSD, and proceeds are routed to the fee receiver for distribution to stcUSD holders.

Q: Is CAP the same as cUSD?

A: No. CAP is the governance and utility token. cUSD is the stablecoin vault token. stcUSD is the staked vault version of cUSD.

Q: What are the main risks?

A: Main risks include smart contract risk, oracle risk, backing-asset risk, liquidity risk, borrower and underwriting risk, liquidation risk, auction participation risk, and governance risk.