PegShieldDemo pathFollow a completed payout
CC3TESTNET
Parametric protection / CC3 testnet

When the peg breaks, proof pays.

Buy fixed protection for USDC. When two price observations meet your policy’s conditions, verified evidence unlocks your payout on Creditcoin.

No bridge. Reserves visible. Source chronology stays on-chain.

Capital is visible before the promise is made.

Every policy reserves coverage against accounted TestUSD capital. Direct donations, fees, and free capacity never disappear into a black box.

Accounted capitalN/ATestUSD · six decimals
ReservedN/Awaiting for first read
Free capacityN/Aavailable to reserve
PoliciesN/Atotal created

One clear product. One deterministic trigger.

The demo product is intentionally conservative and visibly labeled. Terms are fixed when created; a policy stores its own chronology. Values below are read from the live CC3 product when available.

Product 01

USDC depeg cover

Demo only

Pays fixed coverage after two independently verified in-window AnswerUpdated events remain below the threshold for the minimum duration.

SourceEthereum / chain key 3
Aggregator0xc9E1…fE9d7
Triggernot deployed
Premiumillustrative · 2.50%
Activationillustrative · 30 seconds
Minimum breachillustrative · 5 minutes
Policy purchase

Price a protection window

Approve the exact premium, then submit the simulated purchase from your CC3 wallet.

Maximum and premium are unavailable until the live product is read.
The beneficiary is stored at purchase and cannot be selected by a claim relayer.
Quoted premiumN/A

Connect a CC3 wallet to approve and purchase

Follow a completed payout.

A current v4 settlement on CC3 testnet. Explore each step without a wallet.

Recorded example · v4 policy 1 · step 1 of 4

Coverage purchased

Policy 1 reserved 100 TestUSD for the beneficiary fixed at purchase. The premium and payout conditions were locked on Creditcoin.

View the purchase ↗

Demonstration threshold: $1.00983312. These ordinary market observations demonstrate the payout mechanism, not an actual economic USDC depeg. TestUSD has no real monetary value.

Selected policy, from activation to settlement.

Track your coverage and check for a payout. A qualifying pair must occur during coverage and meet the minimum observation interval; the next oracle update time is not guaranteed.

No live policy loaded

Configure a deployment manifest to read purchase state from CC3.

deployment manifest pending

Activation window

Source events before activation are rejected even when the proof itself is valid.

activation is read from chain

Track qualifying observations

We check for two qualifying price observations automatically. The minimum interval is not a countdown to a guaranteed payout.

live claim state unavailable

Claimed or expired

Effects happen before transfer; expiry releases reserve after the grace deadline.

terminal state is not loaded
Your payout

Prepare your claim

Atomic claim

We find qualifying observations and prepare the evidence for you. Creditcoin checks your claim before you confirm a transaction in your wallet.

Advanced: inspect or upload proof files
Maximum 256 KiB. The artifact must use the pinned Ethereum aggregator and AnswerUpdated topic.
Must be a distinct later round and satisfy the product’s minimum observation interval.

Connect a CC3 wallet to simulate a claim

Three boundaries. No hidden oracle.

Attestcoin authenticates the source receipt; PegShield decodes one locked event; the pool applies immutable policy predicates.

01 / SOURCE

Ethereum + Attestcoin

Proof commits to the exact transaction, receipt, Merkle path, and continuity roots.

02 / ADAPTER

Authenticated log

One EVM-v1 receipt chunk is decoded; failed receipts and malformed topics never become observations.

03 / POOL

Reserve + payout

Chronology, replay, reserve accounting, and immutable beneficiary rules are enforced on CC3.

What the prototype trusts

Public protocol dependencies

CC3’s pinned BlockProver and decoder, Ethereum receipt data, and the underwriter’s deposited TestUSD capital. These addresses and hashes are locked in the repository.

What it does not trust

Relayer honesty or UI state

Anyone can relay a proof, but the UI cannot invent a breach. The chain verifies the event, timing, threshold, replay status, and payout state independently.