Skip to main content
Every Cargo vault issues its own permissioned ERC-3643 share contract, one per asset. Each behaves like an ERC-20 for balances and approvals, but every transfer is checked against an on-chain identity registry. The first is cvCOCOA, the Genesis Vault share.

Share Facts

Cargo vault shares are not ERC-4626 vaults. There is no deposit() that mints shares against USDC. New shares are minted only against collateral-manager receipts and sold by the Vault SPV through the auction contracts.

What Integrators Need to Know

  • Transfers Can Fail. transfer and transferFrom revert if the receiver is not a verified identity, or if a compliance rule blocks the transfer. Check eligibility before routing a transfer.
  • The Backing Rule. Total supply never exceeds receipted units in custody. Minting is guarded on-chain and requires a current collateral-manager receipt.
  • Pricing. Value positions at NAV from the NAV feed, not from a pool price. For lending, use the lower of reference NAV and hedge-market-implied NAV.
  • Pauses. The share contract and auctions can be paused by the pause guardian. Treat a paused state as “no transfers, no mints”.
  • One Share Contract per Vault. Treat each vault’s shares as a separate asset with its own NAV feed and lot registry.

Standard ERC-3643 Interface (Excerpt)

Events to Index

The exact ABI, decimals and addresses are published with each deployment on Contract Addresses and in Code Repositories.