Built for product and operations teams at custodians, staking providers, wallets, asset managers, and fund administrators that need to launch and service novel onchain positions faster and with stronger controls, Caddy is the servicing layer between onchain yield protocols and the custody, accounting, and administration systems institutions already use.
Every new protocol introduces a different lifecycle, but operations teams still need a stable record of beneficial ownership, principal, entitlements, rewards, fees, maturity, exceptions, and evidence. Today, that record is reconstructed with spreadsheets, scripts, and manual procedures.
Caddy converts each protocol into a verified position adapter. Read-only agents interpret protocol mechanics and investigate discrepancies; deterministic code recomputes every financial result; authorized operators approve consequential treatment. Caddy then delivers the accepted record and source-linked evidence through API, CSV, or system integrations.
Caddy never holds client funds, accesses private keys, signs transactions, or posts autonomously to official books. Custodians retain control of assets, while accounting and administration platforms remain authoritative.
The first adapter services native Bitcoin staking positions. The same architecture is designed to extend to liquid staking, restaking, basis strategies, and structured vaults, including stablecoin-denominated positions.
Custody, staking, wallet, and asset platforms use Caddy to support new onchain yield products without rebuilding the operational back office for every protocol. Caddy models the lifecycle, ownership, and entitlement rules, then delivers a verified position adapter into the systems the operator already uses. This shortens the path from protocol access to operational readiness without replacing custody or execution.
Caddy combines public protocol state, institutional instructions, and commercial terms into one source-linked record of beneficial ownership, principal, entitlements, rewards, fees, maturity, and status. Deterministic code verifies financial results, while authorized operators retain approval authority.
Caddy tracks expected, accrued, and received rewards across protocol data, custody records, and commercial agreements. It identifies discrepancies, recomputes entitlements, and prepares the evidence operations, accounting, and administration teams need to resolve them.
Read-only agents investigate missing rewards, mismatched balances, incorrect lifecycle states, and other exceptions across approved sources. Caddy proposes an explanation and source-linked evidence pack, then routes the case to an authorized operator for acceptance, rejection, or escalation.
Caddy sends approved position records into existing custody, accounting, and fund-administration workflows through schema-validated API payloads, CSV exports, or evidence packs. Outputs are versioned, replayable, and designed to prevent duplicate or unauthorized delivery.
Caddy’s first adapter services native Bitcoin staking positions across lock, activation, reward cycles, maturity, and unlock. It links Bitcoin and related protocol state with institutional ownership and off-chain commercial context - without holding assets, accessing private keys, or signing transactions.
This site contains content and information, including links to other sites and resources, that was prepared by third parties ("Third Party Content") who are not affiliated with Circle or any of its affiliates (collectively "Circle"). Circle makes no representations on the accuracy, suitability, or validity of Third Party Content. As such, Circle is neither responsible nor liable for any Third Party Content, including any errors, omissions, or delays, or for any actions taken in reliance upon any Thirds Party Content. Reference to any specific company, product, service, or website of any third party does not constitute an implied or express endorsement, recommendation, favoring or validation by Circle. All content provided is for educational and informational purposes only. Circle shall not be liable for any damage or loss relating to use of, or reliance upon, the Third Party Content.