What Creditcoin can read
Deployment
Claims
A claim asserts that a set of source-chain events is complete. Every member was verified by the Block Prover on the way in, so it cannot be inflated; the bond is what stands behind the assertion that nothing was left out.
Watch
This is the part that has to be real. The sweep below runs in your browser, against independent public endpoints, using the same code the watcher daemon runs. If it finds an in-scope event a sealed claim does not contain, one proof breaks the claim and pays you half the bond.
Borrow
The whole underwriting, from this page: bind your Ethereum address, build the two claims, wait out their challenge window, open the line. Same contracts the scripts use, your wallet, real bonds.
Audit the attestors
Everything above trusts one thing this page has not checked: that the header Creditcoin attested is the header Ethereum actually has. The precompile will not say — it answers how far a chain is attested, not with what hash. The indexer publishes the hash, so this asks Creditcoin what it signed and asks independent source-chain endpoints what is really there, and compares. A mismatch here would mean the attestors signed a block that does not exist.
Both Creditcoin networks are audited, not just the one these contracts sit on. Creditcoin Mainnet attests Ethereum mainnet under chain key 1 — the same number that means Sepolia on testnet — by a different set of attestors, and it is checked against Ethereum rather than against testnet.
Credit
Nothing bridges. The history stays on Ethereum, the credit is issued in CTC on Creditcoin, repayment happens back on Ethereum, and only proof crosses.