Simulation Only

This demo demonstrates how a confidential proof-of-reserve system would respond to hypothetical undercollateralization scenarios, offering an alternative to transparent PoR where only a boolean solvency attestation is published onchain.

This is a simulation and does not reflect the actual state of wBTC reserves. The real wBTC reserves are completely fine. Live Chainlink PoR data is used as a realistic anchor, but in production this data would flow through a private custodian API directly into the CRE workflow via ConfidentialHTTP, never via a public feed.

CRE Powered Self-Healing Reserve

Live Dashboard // Chainlink Runtime Environment + Autonomous Recovery

A confidential alternative to transparent Proof of Reserve. In production, reserve balances flow from the custodian's private API directly into a Chainlink CRE workflow via ConfidentialHTTP. They never touch a public feed. The CRE workflow verifies solvency off-chain and publishes only a boolean attestation onchain. When undercollateralization is detected, an AI agent selects the optimal recovery strategy: direct Uniswap swaps for small deficits, or confidential dark pool execution via Chainlink Private Token Transfers for large ones, with end-to-end confidential settlement inside CCC enclaves where market impact matters. No human intervention required. This demo uses live Chainlink wBTC PoR data as a realistic simulation anchor.

1
Reserve API
Private custodian API feeds reserve data into CRE workflow
→
2
CRE Verification
CRE workflow privately verifies solvency off-chain via ConfidentialHTTP
→
3
Onchain Attestation
Boolean solvency result published to smart contract
→
4
Agent Detection
Monitors contract for undercollateralization events
→
5
Wallet Recovery
Autonomous swap and transfer via MPC wallet

Attestation Status

---
Contract ---
Check Frequency Every block (~12s)

Reserve Data

Total Reserve ---
Total Liabilities ---
Ratio ---
0% 100% 200%
Solvency Threshold

Demo Controls

Trigger scenarios to see the self-healing pipeline in action. The agent automatically selects the recovery mechanism based on deficit size. For smaller deficits, the system uses a direct wallet swap because speed matters most and public execution is acceptable. For larger deficits, it switches to the CCC path, where confidentiality matters more than raw speed. This tradeoff is the core idea behind the project: public recovery when the problem is small, and confidential recovery when market impact becomes dangerous.

Direct Wallet Recovery Initializing
Wallet
Step 1
💳
Check Balance
Waiting...
Onchain
Step 2
🔄
Swap
Waiting...
Transfer
Step 3
✅
Send to Reserve
Waiting...
CCC Dark Pool Execution Initializing
CCC Threshold
Step 1
🔒
Encrypt
Waiting...
Shielded
Step 2
📡
Submit
Waiting...
CCC Enclave
Step 3
🛡
Match + Transfer
Waiting...
CCC Attestation
Step 4
✅
Settle
Waiting...

Dual Recovery Architecture

When the CRE workflow detects undercollateralization, an autonomous agent selects the optimal recovery path based on deficit size. Small deficits swap directly onchain; large deficits route through a confidential dark pool where no one sees the order size, counterparties, or fill price.

Trigger a simulation above to see the recovery pipeline in action.

Direct Wallet Swap

Use Case Deficits < $50M
Execution Venue Uniswap (Public DEX)
Transaction Visibility Fully Public
Market Impact Moderate Slippage
MEV Protection None
Amount Privacy Exposed Onchain
Token Transfer Privacy None (Public ERC-20 Transfers)
Speed ~300ms
Complexity Low (3 steps)

Chainlink Confidential Compute Dark Pool

Use Case Deficits > $50M
Execution Venue CCC Compute Enclave
Transaction Visibility Boolean + Encrypted Hash
Market Impact Zero
MEV Protection Full (CCC + Threshold Encryption)
Amount Privacy CCC Threshold Encrypted
Token Transfer Privacy Full (CCC Private Token Transfer)
Speed ~2.2s
Complexity Fully Automated (4 steps + CCC)

Direct Wallet Swap Recovery

For deficits under $50M, the agent executes a fast 3-step recovery using a direct onchain swap via Uniswap — simple, fast, and fully transparent.

When It’s Used

  • Deficit is below the $50M threshold
  • Market impact from the swap is tolerable
  • Speed of recovery is the top priority
  • No confidentiality concerns at this scale

How It Works

  • Agent wallet USDC balance is checked onchain
  • Swap routed through Uniswap V3 for best rate
  • Recovered wBTC sent directly to the reserve
  • Full transaction trail visible on Etherscan
💳
Check Balance
Verify agent wallet has enough USDC to cover the deficit amount.
⚠ Public
➔
🔄
DEX Swap
Swap USDC → wBTC on Uniswap V3 at market rate. Visible in the mempool.
⚠ Public
➔
✅
Send to Reserve
Transfer recovered wBTC back into the reserve fund to restore collateralization.
⚠ Public

Chainlink Confidential Compute Dark Pool Recovery

When deficits exceed $50M, recovery routes through a confidential dark pool powered by Chainlink Confidential Compute (CCC) — end-to-end confidential from encryption through settlement.

The Problem: Public Recovery

  • Large swaps on Uniswap move the market
  • MEV bots front-run recovery transactions
  • Competitors see exact deficit amount onchain
  • Token transfers reveal amounts and counterparties

The Solution: CCC Private Token Transfers

  • Order amount CCC threshold-encrypted (no single node can decrypt)
  • Vault DON re-encrypts inputs for assigned CCC enclave
  • Settlement via CCC private token transfer inside enclave
  • Onchain: only encrypted balance hash + boolean + attestation
🔒
CCC Threshold Encrypt
Deficit amount encrypted with CCC master public key. Threshold-shared across Vault DON — no single node can decrypt.
🔒 Threshold Encrypted
➔
📡
Submit to Pool
Encrypted request submitted to CREDarkPool contract. Contract stores encrypted blob — never sees plaintext.
🔒 Encrypted
➔
🛡
CCC Enclave Match + Transfer
Vault DON provides re-encrypted key shares. Enclave decrypts, matches orders, and settles via CCC private token transfer. Balances updated inside CCC enclave.
🔒 CCC Enclave
➔
✅
CCC Attestation
Enclave re-encrypts updated balance table. Onchain receives only: encrypted balance hash + boolean “recovery succeeded” + quorum-signed CCC attestation.
✓ Quorum-Signed

Dark Pool Recovery Failed

The CCC enclave could not fill the recovery order. The dark pool does not have enough pre-committed liquidity to match the deficit — the reserve stays undercollateralized until manual intervention or a retry.

What Happened

  • Deficit exceeded available dark pool liquidity
  • CCC enclave matching timed out after scanning all committed market makers
  • No partial fills — the dark pool is all-or-nothing to prevent information leakage
  • Order expired without settlement; deficit amount remains hidden

What Happens Next

  • Reserve stays undercollateralized — no automatic fallback
  • Onchain attestation still reads isSolvent = false
  • Manual intervention required: add liquidity providers or retry with different parameters
  • Privacy preserved — no one learned the order size or that the pool was insufficient
🔒
CCC Threshold Encrypt
Deficit encrypted successfully.
🔒 Threshold Encrypted
➔
📡
Submit to Pool
Encrypted order submitted to contract.
🔒 Encrypted
➔
✗
CCC Enclave Match
Timed out. Insufficient liquidity committed by market makers to fill the order.
✗ Timed Out
➔
✅
CCC Attestation
Skipped — previous step failed.
✗ Skipped

Recovery Strategies

Current Strategy ---
No recovery executed yet. Use the demo controls above to trigger a recovery simulation.

Event Timeline

Waiting for events...

Agent Metrics

Waiting for agent reports...

Agent Activity

No recovery actions yet.