Genesis

From OMXUS
Revision as of 14:58, 31 January 2026 by Maintenance script (talk | contribs) (Import OMXUS content)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Genesis in the context of OMXUS refers to the foundational design principles underlying the Human Existence Record (HER) and the OMXUS token—a form of cryptographic genesis that creates permanent, unforgeable proof of human existence.[1]

The term draws on both the biblical concept of creation and the blockchain terminology for an initial, irreversible starting point. In OMXUS, each human's verified identity becomes a kind of personal genesis block—a permanent record that can never be undone.

Overview

Traditional digital identity systems rely on centralized authorities: governments issue passports, corporations control login credentials, databases can be altered or deleted.[2] OMXUS inverts this model by making identity:

  • Distributed — No single point of failure can erase a person's record
  • Cryptographically bound — Mathematical proofs rather than bureaucratic assertions
  • Socially verified — Three humans vouch for existence, creating a web of trust
  • Self-sovereign — The individual controls their own proof, not an institution

The Human Existence Record

Template:Main

The Human Existence Record (HER) is the core data structure representing a verified human in OMXUS. Each HER contains:

Component Description
Public key Cryptographic identity for signing actions
Vouch signatures Three digital signatures from existing members
Content identifier CID linking to IPFS storage
Checkpoint hash Link to the global Merkle tree checkpoint
Metadata Optional fields: pseudonym, contact methods, preferences

The HER is designed to satisfy the self-sovereign identity principles articulated by Christopher Allen: existence, control, access, transparency, persistence, portability, interoperability, consent, minimization, and protection.[3]

Cryptographic Properties

Content Addressing

Each HER is stored using content addressing—the record's identifier is a cryptographic hash of its contents. This means:

  • The identifier cannot exist without the content
  • Any modification creates a different identifier
  • Verification requires only the identifier and the content

This approach is used by Git, IPFS, and other distributed systems.[4]

BLS Signatures

Checkpoint aggregation uses Boneh–Lynn–Shacham (BLS) signatures, which allow multiple signatures to be combined into a single short signature that proves all participants signed.[5] This enables:

  • Compact checkpoints even with millions of participants
  • Efficient verification of collective agreement
  • Detection of any attempt to modify historical records

Bitcoin Anchoring

Template:Main

Periodic checkpoints are anchored to the Bitcoin blockchain using the RGB protocol. This creates an immutable timestamp that:

  • Cannot be altered without controlling 51% of Bitcoin's hash power
  • Provides proof of existence at a specific time
  • Allows anyone to verify the checkpoint independently

The Proof Capsule

Every OMXUS participant carries a Proof Capsule—a portable bundle containing all information needed to prove their existence:

{
  "her": {
    "publicKey": "ed25519:abc123...",
    "vouchers": [
      {"signature": "sig1...", "voucherCID": "Qm..."},
      {"signature": "sig2...", "voucherCID": "Qm..."},
      {"signature": "sig3...", "voucherCID": "Qm..."}
    ],
    "created": "2026-01-15T00:00:00Z"
  },
  "checkpointChain": ["Qm...", "Qm...", "Qm..."],
  "ringPublicKey": "secp256k1:def456..."
}

This capsule can be:

  • Stored on a mobile device
  • Printed as a QR code
  • Embedded in a physical artifact
  • Backed up to any storage medium

Even if all other network infrastructure fails, a single surviving Proof Capsule allows its owner to prove their verified existence.

Survivability

The Genesis design prioritizes extreme survivability:

Social Replication

Because each person is vouched by three others, and those three vouch for their own networks, the identity graph ripples outward. Each HER is naturally replicated across multiple social connections.

Technical Redundancy

Records are stored in:

  • IPFS with CDN pinning
  • Institutional mirrors (libraries, universities)
  • Personal devices of participants
  • Physical backups (QR codes, printed records)

Minimal Recovery Requirements

The system is designed so that:

  • A single surviving mirror can reconstruct the entire checkpoint history
  • Any Proof Capsule can verify its owner's existence independently
  • No central authority is required for recovery

The Genesis Charter

The OMXUS Genesis Charter declares:

Template:Quotation

This statement reflects the project's core commitment: that identity should be a human right, not a privilege granted by institutions.

Philosophical Context

The Genesis concept connects to several philosophical traditions:

The design also responds to historical cases where identity erasure was used as a tool of oppression—from Roman damnatio memoriae to modern statelessness.[6]

See Also

References

Template:Reflist

External Links

  1. OMXUS Foundation (2026). "OMXUS Whitepaper". Section 3: Identity Architecture.
  2. Windley, P. (2005). Digital Identity. O'Reilly Media. ISBN 978-0596008789.
  3. Allen, C. (2016). "The Path to Self-Sovereign Identity". Life with Alacrity blog.
  4. Benet, J. (2014). "IPFS - Content Addressed, Versioned, P2P File System". arXiv:1407.3561.
  5. Boneh, D.; Lynn, B.; Shacham, H. (2001). "Short Signatures from the Weil Pairing". ASIACRYPT 2001.
  6. Arendt, H. (1951). The Origins of Totalitarianism. Chapter 9: "The Decline of the Nation-State and the End of the Rights of Man".