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. Full text not collected yet; the hash covers title and summary.
Article
Phishing con invitaciones falsas de calendario afecta a miles de organizaciones - Diario del Sur
Published
16 Oct, 22:56 WIB
article_uid
922e0b2936e1414ed0edb5fe
SHA-256 of text
none yet (text not collected)
Evidence
9c9244fada90b1c8646cc065Independentopen incident
Merkle batchbatch #80 · leaf 236 of 437 · created 17 Oct, 07:11 WIB
rootc5981ccb3ccedbce79b14911c4bf3186d24b894fd721b4debc54b60b7fe4d2d8leaf hashd38b30d2d0…ba391c · 9 sibling hashes
leaf hashroot
Merkle proof validawaiting anchoringcopy matches current data
On-chain
Not anchored yet: waiting for the next anchoring run on the local network
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