CSAIS
IDEN
Transparency

How to check the evidence behind each incident, where the news comes from, and how close the machine and the public come to institution decisions.

Institution portal

Verify evidence

Enter an article link, the SHA-256 hash of its text, or an evidence ID. The system looks the article up among prepared evidence and shows its hash fingerprint and the incident it belongs to.

80 batches holding 65,736 evidence records; 22 batches awaiting anchoring.How evidence is recorded →Institutional attestation ↓

SHA-256 fingerprintThe 64 hex characters are drawn as an 8×8 grid. A single-character change in the article changes the whole pattern. This fingerprint, not the article text, is what gets anchored on-chain.
Found. This article is part of CSAIS evidence.Matched by ID. Text collected 29 Sept, 11:18 WIB.
Article
Florida says motor vehicle data breach tied to credentials stolen from officer’s personal device - The Record from Recorded Future News
Published
11 Sept, 14:00 WIB
article_uid
979094b237760d2ab6d33b33
SHA-256 of text
f46c3d7553d410ca9e919759214400207121edfb18cde9cbdd30456a9310372b
Evidence
e5a7c6287f3e4518fe4c6bb6Single sourceopen incident
Merkle batchbatch #5 · leaf 688 of 1,024 · created 27 Sept, 07:16 WIB
root9717309f0c17405d79c4cc9da7174366e5483c6a1b3d078fa446226fd70db3b1leaf hash9377b68e8d…760b13 · 10 sibling hashes
leaf hashroot
networkAnvil lokal · chain 31337 · block 10tx0xb1f4e98143047a35b896e8f45098097fdbfdf774b4162117117f990549a2c613contract0x5fbdb2315678afecb367f032d93f642f64180aa3Local prototype network on the CSAIS team's machine; it cannot be checked directly from the internet yet.
Merkle proof validanchored on Anvil lokaltext was collected after the batch; the batched copy still stands
Institution portal

Official decisions from BSSN, OJK, Komdigi, and Siber Polri

Each institution picks its account and signs in with a password, reviews the incident queue within its mandate, and chooses a decision with one click: confirmed, refuted, or partly/under investigation, with a reason. Every decision is signed with the institution's cryptographic key (EIP-712) without a wallet; confirmed and refuted decisions become official records booked into the Merkle ledger and anchored on-chain.

confirmedrefutedpartly / under investigation
BSSN
BSSNMandate: cyber incidents, vulnerabilities, vital information infrastructureQueue routed from technical attack types and agency victims
decisions signed with the institution key (EIP-712)
OJK
OJKMandate: banks, insurers, fintech, capital marketsQueue routed from financial sector and bank-customer groups
decisions signed with the institution key (EIP-712)
Siber Polri
Siber PolriMandate: online fraud, cybercrime, arrestsQueue routed from online, job, and investment scam types
decisions signed with the institution key (EIP-712)
Komdigi
KomdigiMandate: digital platforms, electronic system operators, hoaxes, contentQueue routed from platform victims and hoax-related articles
decisions signed with the institution key (EIP-712)
Principles
  1. 01Evidence is recorded as collected; institutional attestations are added afterwards, never as a gate.
  2. 02Absence of an attestation does not mean invalid; most incidents will never be reviewed by an institution.
  3. 03Attestations are append-only: newer ones supersede older ones and the history is kept.
  4. 04Institution keys are registered in the contract with rotation and revocation; note contents stay off-chain, their hashes on-chain.
Open the institution portalView pending incidents