🛡️

VocalWitness

← Back to Square

Transparency Dashboard

Live • Updated in Real Time

Trust metrics, hash-chain health, disputes, and operator accountability

—
Sealed reports
—
Hash-chain
—
Open disputes
—
Upheld / Rejected

Dispute & Challenge Outcomes

Reputation feed
Loading dispute metrics…

Challenges that are upheld or rejected feed the reputation model (corroborations − failed challenges + longevity). Score writes should be server-enforced.

Focus Regions

Africa-first

Africa-first density strategy: seed real sealed reports in Nigerian cities first (Enugu + Lagos), then expand across the continent.

Enugu, NG Lagos, NG + more African cities
Enugu (sample)
— sealed
Lagos (sample)
— sealed

Fund Allocation (This Month)

Allocation breakdown loads when contribution data is available.

Prove It Yourself

Local · No upload

Hash any file on your device. Nothing is uploaded. Compare against the live chain head.

📁
Drop media or Evidence Pack
or click to choose
Offline: sha256sum file · certutil -hashfile file SHA256

Prove It Now

Local · No upload

Hash a file or paste a SHA-256 on your device. Nothing leaves the browser. This proves bit-integrity of sealed evidence against the public ledger head.

📁
Drop media / Evidence Pack JSON
or click to choose
Offline commands: sha256sum file · certutil -hashfile file SHA256
External anchor
OpenTimestamps daily root — not yet active. Planned: Bitcoin calendar + optional Base noticeboard.

Ledger Integrity & Application-Level Immutability

Operator Transparency

Once a record is written to the Forensic Ledger or the audit log, the application and database rules make it impossible for any user (or ordinary operator) to edit or delete it.

  • Firestore security rules explicitly forbid update and delete on the ledger collections.
  • Client-side SHA-256 hashing of media and content.
  • Hash-chaining of audit entries (each entry contains the cryptographic hash of the previous one).

Important clarification: This is application-level immutability. It is not a full public blockchain. The data lives in Firebase / Google Cloud. The rules and cryptography make silent changes extremely difficult, but the ultimate trust still rests on the operator’s honesty and the cloud provider’s integrity.

External anchoring (OpenTimestamps / public chain) can be added later for extra independent proof. Application-level immutability is already active today.

AI Detection Audit Logs & Appeals

System Accountability

Appeals here are for false-positive synthetic flags. Testimony challenges use a separate dispute flow (governance).

Media Hash Confidence Score Detector Status Action
Loading AI detection logs...

External Immutable Anchor

OpenTimestamps

Every day the platform publishes a Merkle root of newly sealed reports to the OpenTimestamps calendar network. Anyone can independently verify that the root existed at that time — without trusting Firebase or VocalWitness.

Loading latest external anchor…

Recent Testimony Challenges

Governance
Dispute ID Testimony Status Created
Loading challenges…
Data is fetched live from our transparent ledger.
Last updated: —