Third-party verification

Every data point on this site carries three independent guarantees, kept strictly separate from each other.

1 · The fact is on the blockchain.

The txid, amount, block, and addresses are public record — verify them on any block explorer. The chain itself is the proof. We sign nothing for this.

2 · The interpretation carries a signature.

Our flow classification and entity labels are committed to with an Ed25519 signature. This proves authorship — Swiss Whale Intelligence stated exactly this — not correctness. You may disagree with our interpretation; the signature lets you hold us to what we actually said.

3 · Labels carry traceable provenance.

Only proof-backed sources — OFAC sanctions lists, cryptographically signed exchange Proof-of-Reserves, explorer-curated addresses — are frozen into the signature. Heuristic labels are shown live and left unsigned.

Trust roots in the public key published under this Swiss domain at /.well-known/swi-attest-keys.json. The file is an array; retired keys remain so old attestations stay verifiable.

attested_at is self-asserted — it records when we first signed, not when the transaction occurred and not a claim of temporal precedence over any other observation.

Live example — proof-backed attestation

The following is a recently-attested transaction where at least one address carries a proof-backed label (tier-1 or tier-2 source). Click to inspect the full signed assertion and run the verifier.

USDT · 0x67345d0133910b…f28036df

from: OKX Proof-of-Reserves, signature-verified (tier 1) · proof ↗
to: OKX Proof-of-Reserves, signature-verified (tier 1) · proof ↗

Inspect signed assertion & run verifier ↗

Verify a data point yourself

# pip install cryptography
python verify_attestation.py <chain> <txid>

The script fetches /api/attest/<chain>/<txid>, reads key_id from the signed bytes, looks the key up by id in the published array, and checks the Ed25519 signature over the delivered bytes — one standard library call.

Machine-readable endpoint

Every MCP tool result and alert permalink is attestable at:

GET /api/attest/<chain>/<txid>
→ signed_bytes_b64, signature_b64, key_id, assertion

Public keys ↗ · Methodology whitepaper ↗