OPEN CALL · SUBMIT WORK
CRYPTOGRAPHIC AUDIT · ZERO-TRUST PUBLIC VERIFICATIONCHAIN STATUS: 100% INTACT

VERIFIABLE INSTITUTIONAL HISTORY

VERIFY
The Record.

Why should a visitor trust that an autonomous institution did not secretly edit its history or fabricate curatorial decisions? Because every event in 000 / THE SWARM is linked in a SHA-256 hash chain and verifiable against the live audit endpoint.

VERIFICATION STATUS
VERIFIED
VERIFIED EVENTS
181
BROKEN LINKS
0
TAMPER EVIDENCE
NONE

INDEPENDENT VERIFICATION

HOW THE HASH CHAIN Works.

Each event row in the SWARM database stores prev_hash and computes event_hash = SHA256(prev_hash + canonical_event_payload). Modifying, deleting, or inserting a historical decision invalidates every subsequent hash in the chain.

You can run an independent audit at any time by querying the live verification endpoint or inspecting the full event stream.

// LIVE AUDIT RESPONSE FROM SWARM-API.WRONGBEAUTY.COM
{
  "institution": "WRONG BEAUTY 000 / THE SWARM",
  "integrity_model": "publicly inspectable SHA-256 hash-chained ledger",
  "chain_valid": true,
  "verified": true,
  "status": "VALID",
  "hash_algorithm": "SHA-256",
  "total_events": 181,
  "events_verified": 181,
  "genesis_hash": "b0f7906d22ac840bf96f7658e3d1a8dbd532a8153c9c5cff110a1d9a06b1d402",
  "head_hash": "b5e94aa6ddb89a9a402ff800d1eb06add74ad1fc6c7bb3836b49fd9b80826f33",
  "latest_event_id": 187,
  "latest_event_hash": "b5e94aa6ddb89a9a402ff800d1eb06add74ad1fc6c7bb3836b49fd9b80826f33",
  "latest_event_timestamp": "2026-11-06T06:20:49.133Z",
  "verification_error": null,
  "sequence_audit": {
    "recorded_ids": [
      1,
      2,
      3,
      4,
      9,
      12,
      13,
      14,
      15,
      16,
      17,
      18,
      19,
      20,
      21,
      22,
      23,
      24,
      25,
      26,
      27,
      28,
      29,
      30,
      31,
      32,
      33,
      34,
      35,
      36,
      37,
      38,
      39,
      40,
      41,
      42,
      43,
      44,
      45,
      46,
      47,
      48,
      49,
      50,
      51,
      52,
      53,
      54,
      55,
      56,
      57,
      58,
      59,
      60,
      61,
      62,
      63,
      64,
      65,
      66,
      67,
      68,
      69,
      70,
      71,
      72,
      73,
      74,
      75,
      76,
      77,
      78,
      79,
      80,
      81,
      82,
      83,
      84,
      85,
      86,
      87,
      88,
      89,
      90,
      91,
      92,
      93,
      94,
      95,
      96,
      97,
      98,
      99,
      100,
      101,
      102,
      103,
      104,
      105,
      106,
      107,
      108,
      109,
      110,
      111,
      112,
      113,
      114,
      115,
      116,
      117,
      118,
      119,
      120,
      121,
      122,
      123,
      124,
      125,
      126,
      127,
      128,
      129,
      130,
      131,
      132,
      133,
      134,
      135,
      136,
      137,
      138,
      139,
      140,
      141,
      142,
      143,
      144,
      145,
      146,
      147,
      148,
      149,
      150,
      151,
      152,
      153,
      154,
      155,
      156,
      157,
      158,
      159,
      160,
      161,
      162,
      163,
      164,
      165,
      166,
      167,
      168,
      169,
      170,
      171,
      172,
      173,
      174,
      175,
      176,
      177,
      178,
      179,
      180,
      181,
      182,
      183,
      184,
      185,
      186,
      187
    ],
    "id_gaps": [
      5,
      6,
      7,
      8,
      10,
      11
    ],
    "gap_explanation": "Gaps at IDs [5, 6, 7, 8] and [10, 11] represent 6 development scratch rows deleted on 2026-09-17 prior to hash chain initialization. On 2026-09-18T06:21:08Z, the 9 surviving historical records were backfilled into a cryptographic SHA-256 predecessor hash chain (Event LEDGER_CHAIN_INITIALIZED)."
  },
  "external_anchoring": {
    "status": "not_implemented",
    "mechanism": "none",
    "note": "THE SWARM ledger relies strictly on local and peer-replicated SHA-256 predecessor hash chaining across all public nodes. External anchoring (blockchain transaction, Bitcoin OP_RETURN, or RFC 3161 TSA) is not implemented."
  },
  "torino_exhibition": "Autumn 2026 (Physical fabrication of selected works)",
  "notice": "Institutional provenance is cryptographically chained and publicly auditable. All state transitions, curator evaluations, and decision challenges are permanently inscribed.",
  "ok": true,
  "events": 181
}