Doxa’s Proposed Reserve Move Turns Stablecoin Minting Into a Cross-Chain Verification Pipeline

Doxa is proposing a new reserve architecture for DoxaUSD that separates how users enter the system from what ultimately backs the stablecoin. Under the forum proposal, users would still deposit ICP, but the protocol would treat ckUSDC as an intermediate settlement asset rather than the final reserve.

The proposed flow is ICP → ckUSDC → native USDC on an EVM network → USDY → Doxa Reserve → DoxaUSD. The key rule is that DoxaUSD should not be minted merely because ICP or ckUSDC has been received. Minting would remain blocked until the corresponding USDY position is confirmed in the reserve.

That makes the proposal less about swapping one token for another than about introducing a cross-chain state machine. Doxa describes stages including ICP receipt, ckUSDC acquisition, USDC redemption, USDC receipt, USDY acquisition, USDY verification, collateral verification, and final DoxaUSD issuance. A failed stage would keep the request pending or trigger a defined recovery path.

The architecture relies on ICP Chain Fusion as its control layer. ICP documentation describes threshold ECDSA as a way for canisters to derive and request signatures without reconstructing a private key, while the EVM RPC canister can query multiple providers and report whether their responses are consistent. In Doxa’s design, those capabilities would support an EVM reserve address controlled by a canister rather than by a conventional centralized custodian.

The separation also changes the accounting question. ckUSDC would represent the ICP-side settlement leg; native USDC would bridge settlement into the selected EVM environment; and USDY would become the defined reserve asset. The proposal says the reserve should be publicly auditable through an EVM address, token balances, acquisition and redemption transactions, DoxaUSD supply, and collateralization data.

USDY introduces meaningful constraints alongside its yield-bearing design. Ondo describes USDY as a yield-bearing token backed by cash-equivalent assets and says it is not a stablecoin. Its current product materials also state that access and minting or redemption are subject to non-US eligibility and other jurisdictional restrictions. Those conditions matter directly to Doxa’s proposed USDC-to-USDY step: a protocol-level transaction path cannot be treated as permissionless until issuer requirements, liquidity, contract interfaces, valuation, and redemption procedures are resolved.

The forum proposal acknowledges those open questions. It calls for oracle rules, stale-price handling, collateralization thresholds, whitelisted contracts, transaction limits, emergency controls, retry and refund procedures, and explicit DAO decisions on how yield would be treated. It also suggests starting with one EVM network to limit operational complexity, but does not establish a final production network in the material reviewed.

The safety boundary is therefore clear: Doxa is proposing to make reserve ownership and reserve verification separate, observable steps. The design could let ICP remain the user-facing and governance layer while USDY sits natively on an EVM chain. But until the implementation, issuer eligibility path, valuation model, reserve address, and governance controls are published and tested, this remains an architecture proposal—not evidence that DoxaUSD has already moved to USDY collateral.