From a citizen's phone to the right responder — responsibly

1. Step 1

   Verify once

   The citizen verifies their identity through an authorized identity-verification process.

   • Verification is performed by an approved provider or authorized institution.
   • Government identity data is handled off-chain and never published.
   • The blockchain does not verify the government ID itself — it only records that a trusted verifier issued a credential.

2. Step 2

   Receive a privacy-preserving credential

   The citizen receives a verifiable digital credential or proof linked to their account or wallet.

   • The credential can prove: this is a verified person.
   • It can prove the person meets an age requirement.
   • It can prove the person belongs to an eligible geographic area.
   • It can prove the credential is active.
   • It can prove the person is not creating unlimited duplicate accounts.

   This works through selective disclosure: the credential answers narrow yes/no questions — like “is this participant verified?” — without handing over the underlying documents. Zero-knowledge proofs are the cryptographic technique that makes it possible to prove a fact is true without revealing the data behind it.

3. Step 3

   Submit a structured report

   A verified participant submits an incident report from the mobile device they already use.

   • Incident category
   • Approximate or precise location, depending on the incident
   • Timestamp
   • Description
   • Photo or video evidence
   • Urgency level
   • Optional follow-up availability

   Participants are never encouraged to confront anyone, enter dangerous areas or place themselves at risk. A report is information — not intervention.

4. Step 4

   Verify and prioritize

   Reports are assessed using multiple validation signals before anything is escalated.

   • Multiple independent reports
   • Time and location consistency
   • Reporter reputation
   • Evidence metadata
   • Trusted community validators
   • Institutional review
   • Duplicate detection
   • Automated anomaly detection

   Automated systems may help prioritize reports, but serious enforcement or emergency decisions should not be made solely by an algorithm.

5. Step 5

   Route to responders

   Validated reports can eventually be routed to the institutions best placed to act.

   • Emergency services
   • Disaster-response teams
   • Municipal authorities
   • Road and infrastructure agencies
   • Health responders
   • Approved humanitarian organizations
   • Participating community-response teams

6. Step 6

   Audit and improve

   Sensitive access and actions are logged so the system remains accountable to the communities it serves.

   • Access to sensitive data leaves a tamper-evident record.
   • Corrections and appeals are supported for people and institutions.
   • Independent review informs continuous improvement of rules and safeguards.

The identity and credential layers are described in depth on the Identity & Privacy page, and the rules that keep this model accountable live on the Safeguards page.