CoinYQ Dossier

The dollar with two exits and three safety layers

cUSD looks like one token, but its promise travels through a reserve vault, a lending market and an administrative control plane. The useful question is not whether the screen says one dollar. It is which asset can leave, who bears the first loss and which key can alter the path.

First fix the address, then the name

An older project also used the Cap name for synthetic trading. This asset is different. Cap USD went live for minting on 2025-08-18, and its canonical Ethereum proxy is 0xcCcc62962d17b8914c62D74FfB843d73B2a3cccC. The contract calls itself cap USD with symbol cUSD. The similarly patterned 0x88887bE419578051FF9F4eb6C858A951921D8888 address belongs to stcUSD.

That distinction separates money from a savings position. cUSD is minted and redeemed against the reserve. stcUSD is obtained by staking cUSD and is meant to collect income. Neither address identifies a bank account, a dollar deposit or ownership in Cap Labs or Covered Agents S.A.

One door chooses an asset; the other takes the basket

The Vault offers two exits. burn() destroys cUSD for one selected backing asset at oracle value. Its dynamic fee rises as that asset moves away from its target reserve weight. redeem() destroys cUSD for a proportional slice of every supported asset and applies a fixed fee. Both calls carry user-set minimum output and a deadline.

The difference becomes sharp during a depeg. A proportional redemption shares the impaired asset across redeemers; it does not manufacture a dollar. Current documentation says the live fractional reserve supports USDC and deploys idle USDC through Aave V3, while broader asset examples describe the architecture’s direction. The same docs put the minimum mint fee at 10 bps, cap it at 5%, and allow authorized whitelisted users to bypass fees.

The live reserve is therefore a one-asset instance of multi-asset code, not proof that every blue-chip asset named in an overview is already accepted. Adding another backing asset requires privileged configuration and would change the contents of proportional redemption.

Yield enters only after a second token and a credit loop

Idle reserves can earn through underlying assets or integrated lending strategies. Borrowers can also draw reserve assets after underwriters delegate enough collateral. Borrower interest combines a market-and-utilization hurdle with a negotiated underwriting premium. Harvested value reaches the fee machinery and stcUSD; it is not automatically added to every plain cUSD balance.

If a borrower’s health factor falls below its liquidation threshold, a grace period starts. Liquidators then repay debt and receive slashed underwriter collateral with a bonus that grows through the liquidation window. This is a first-loss mechanism for credit exposure. It still relies on collateral value, oracle output, shared-security networks and successful execution.

“Covered” is a waterfall, not a government seal

Cap describes two guarantee layers. Onchain, an underwriter escrows collateral for a borrower and can lose it. Offchain, those institutions may sign a guarantor agreement giving the underwriter recourse after covering a default. The agreement is optional and runs between counterparties; a cUSD holder is not thereby named as an insured bank depositor.

The limit appears in Cap’s own risk page. Reserve assets can depeg, freeze or be seized; idle funds inherit Aave or Morpho risk; bridges and oracles can fail; redemptions may be delayed at full utilization. Vault code likewise checks available balance. Even the variable named insuranceFund is an administrator-set recipient for mint and burn fees, not evidence of a regulated policy.

The final layer is a set of human keys

cUSD is a UUPS proxy, and its current implementation can be replaced by an authorized role. Cap’s published Ethereum access check places proxy upgrades, new reserve assets, fee parameters and major oracle changes behind timelock 0xD8236031d8279d82E615aF2BFab5FC0127A329ab. Developer-controlled addresses retain faster powers: the published multisig can pause, unpause, change reserve settings and whitelist users, and a developer EOA can also pause.

Covered Agents S.A., identified in the terms as a Panama corporation, operates the front end and reserves rights to modify or suspend it. The terms disclaim warranties and place digital-asset, smart-contract and shared-security risk on users. The contract supplies a conditional redemption mechanism; the documents do not turn cUSD into company equity, a dividend, a bank deposit or an unconditional legal promise to pay one fiat dollar.

How the project changed

  1. 2025-03-26
    Platform terms were revised

    The published terms identify Covered Agents S.A. as the Panama front-end operator and allocate platform risk to users.

  2. 2025-04-17
    Cap announced Chainlink price-feed integration

    The announcement described ETH/USD pricing for restaking delegations that secure operator activity.

  3. 2025-08-18
    cUSD minting went live

    Cap opened the Ethereum product with USDC as the initial reserve collateral and Symbiotic shared security.

  4. 2025-10-08
    The first-quarter implementation was documented

    Cap reported that money-market funds and EigenLayer were still future additions rather than launch components.

  5. 2026-01-29
    The Homestead program began

    A new incentive phase separately tracked cUSD holders and delegators; it did not alter tokenholder legal rights.

  6. 2026-07-23
    The announced Homestead window ended

    The point-program end date did not itself promise a token distribution or fixed return.

Evidence and primary sources

Last evidence review: 2026-09-05

What is Cap USD?

Cap USD is the base dollar token of Cap’s credit platform. The canonical Ethereum cUSD proxy is 0xcCcc62962d17b8914c62D74FfB843d73B2a3cccC; stcUSD at 0x88887bE419578051FF9F4eb6C858A951921D8888 is the separate yield-bearing wrapper. cUSD supply expands when users deposit an approved reserve asset and contracts mint cUSD, then contracts burn it when users withdraw one asset or redeem a proportional basket. Current reserve documentation lists USDC and an Aave V3 strategy, while broader baskets remain a design direction.

What problem does Cap USD solve?

A stablecoin can say “one dollar,” “yield” and “insured” while each word points to a different balance sheet. cUSD holders face the reserve and redemption code. stcUSD holders add lending and strategy yield. Borrowers take reserve liquidity; underwriters put slashable collateral behind them. The marketing word “covered” describes that collateral waterfall and optional guarantor agreements. It does not erase reserve depegs, utilization delays, oracle errors, administrator keys or the absence of deposit insurance.

How does Cap USD work?

Mint deposits an approved asset and issues cUSD at oracle value after dynamic fees. Burn destroys cUSD for one selected asset; redeem destroys it for each asset’s proportional share, socializing a depeg instead of leaving the last holder with the weakest collateral. Idle reserves may enter fractional-reserve strategies and borrowers may draw through the Lender. cUSD staked into stcUSD receives harvested reserve and borrower income. If borrower health falls below its threshold, a grace period leads to permissionless liquidation: debt is repaid and delegated underwriter collateral is slashed at a time-growing bonus. Every leg depends on available liquidity, prices and privileged configuration.

Key facts

  • Canonical Ethereum cUSD proxy: 0xcCcc62962d17b8914c62D74FfB843d73B2a3cccC; separate stcUSD: 0x88887bE419578051FF9F4eb6C858A951921D8888.
  • cUSD has elastic supply: reserve deposits mint it, while asset-specific burn and proportional redemption destroy it.
  • As of 2026-09-05, current Fractional Reserves documentation lists USDC with an Aave V3 strategy; additional assets are presented as forthcoming.
  • Burn selects one backing asset at oracle value with dynamic fees; redeem returns the proportional basket with a fixed fee and spreads any reserve-asset depeg loss.
  • Documentation sets the minimum mint fee at 10 bps and caps it at 5%; authorized whitelisted users can bypass fees.
  • cUSD is the base dollar token; protocol yield accrues through the separate stcUSD staking position.
  • Borrowers require overcollateralized underwriter delegation; unhealthy positions enter a grace period and then permissionless liquidation of delegated collateral.
  • “Covered” means onchain underwriter collateral plus optional offchain guarantor agreements; it is not government deposit insurance.
  • Redemption can be delayed when reserves are fully utilized, and code requires enough available balance before transferring assets.
  • Oracles price mint, burn and risk; stale prices can stop mint/burn, while authorized roles can replace feeds and change staleness settings.
  • cUSD is UUPS-upgradeable: the published access check assigns upgrades and core configuration to a timelock, with pause and reserve powers also held by developer-controlled addresses.
  • The contract’s insuranceFund is an adjustable fee-recipient address, not proof of a regulated insurance policy.
  • Covered Agents S.A. operates the front end under Panama-law terms that disclaim warranties and grant no equity, dividend, bank-deposit status or unconditional company redemption debt.

Official links

Categories

Related coins

Frequently asked questions

What is the difference between cUSD and stcUSD?

cUSD is the reserve-backed unit used for minting and redemption. stcUSD is a separate token received by staking cUSD; it accrues eligible reserve-strategy and borrower income. Holding plain cUSD does not automatically deliver that yield.

Can cUSD always be redeemed immediately for one dollar in cash?

The contracts offer burn and basket-redemption paths into available reserve tokens, not a cash window at a bank. Cap’s own risk page says redemption may be delayed when reserves are fully utilized; output also depends on oracle value, fees, collateral prices and liquidity.

Why are burn and redeem separate?

Burn selects one supported asset and charges a dynamic fee that responds to reserve imbalance. Redeem returns a proportional slice of every reserve asset for a fixed fee, so a depegged asset’s loss is shared instead of pushed onto the last redeemer.

Is cUSD insured?

Cap uses “insured” for underwriter collateral that can be slashed and optional guarantor agreements between institutions. The insuranceFund variable receives protocol fees. Neither is the same as government deposit insurance or an unconditional policy payable to each token holder.

Who can change or stop cUSD?

The Ethereum token is a UUPS proxy. Cap’s published access snapshot assigns proxy upgrades, asset additions, fee parameters and major oracle changes to a timelock; a developer multisig can pause, change reserve settings and manage whitelists, and a developer EOA also has emergency pause access.

Does cUSD give a legal claim on Cap Labs or Covered Agents S.A.?

The token contract gives a code-based route to reserve assets when conditions are met. The published platform terms grant no share, dividend, bank-deposit status or unconditional debt claim against the company and broadly disclaim warranties and financial losses.

External trackers

Choose a tracking site for Cap USD: