2-of-3 Threshold
Verified Inputs

Oracle Network

Three independent oracle bots read on-chain wallet history. Your credit record is only issued when 2-of-3 oracles agree — eliminating self-attestation fraud.

Oracle Slots

Consensus Requirements

0 / 3

Registered Oracles

2-of-3

Threshold (quorum)

On-Chain Data

Attestation Model

Oracle Operator Panel

Connect the registered oracle wallet to submit attestations.

Connect the wallet registered in oracle slots (none registered) to unlock attestation.
No wallets have submitted credit data yet. Users must visit the Credit page first.

Check Oracle Verification

Check whether a wallet has a finalized oracle-verified credit record.

How Oracle Attestation Works

  1. 01

    Each oracle bot independently reads on-chain data: tx count, first tx block, protocol interactions from lending pools.

  2. 02

    Each oracle hashes the attestation data (BHP256) and calls submit_attestation. Raw data is never stored on-chain.

  3. 03

    When 2 oracles submit matching hashes, consensus is reached for that wallet.

  4. 04

    The wallet owner calls claim_verified_credit with the matching data. The ZK circuit proves the hash matches — and issues a private VerifiedCreditRecord.