🌌 Bitcoin Universe

Abstract

1. Introduction

1.1 Motivation

Bitcoin blocks are cryptographically sealed packets of entropy. Each block hash is an unpredictable, universally agreed-upon 64-byte hexadecimal string. Rather than treating this entropy as mere bookkeeping, Bitcoin Universe interprets it as the genome of a star system. The result is a cross-disciplinary bridge between blockchain consensus, procedural generation, and real-time 3D graphics.

1.2 Design Principles

2. System Architecture

2.1 Data Layer

The canonical data source is the Ordinals block endpoint:

GET https://ordinals.com/r/blockinfo/{height}

Caching Strategy: Client-side Map with LRU eviction (capacity: 30 blocks). Eliminates redundant network requests.

2.2 Deterministic Randomness Engine

Bitcoin Universe does not use Math.random(). It employs a seeded PRNG initialized from the block hash.

Seed Derivation

seed = Σ(i=0..n-1)  hash.charCodeAt(i) × 31^(n-1-i)   (mod 2³²)

Mulberry32 PRNG

function mulberry32(a) {
    return function() {
        let t = a += 0x6D2B79F5;
        t = Math.imul(t ^ t >>> 15, t | 1);
        t ^= t + Math.imul(t ^ t >>> 7, t | 61);
        return ((t ^ t >>> 14) >>> 0) / 4294967296;
    };
}

3. Trait Generation Protocol

3.1 Surface Biome

biome_index = parseInt(hash[18:20], 16) % 5

3.2 Atmosphere (Weather)

weather_index = parseInt(hash[2:4], 16) % 4

3.3 Civilization Density

3.4 Economic Development

Derived from total_fee (satoshis). The three rarest tiers trigger a separate rendering pipeline layered on top of the base stellar class.

3.5 Stellar Class (Rarity)

Derived from the count of leading zero characters in the block hash. Each additional zero is statistically 16× rarer.

leading_zeros = count of '0' chars before first non-zero char in hash
stellar_class  = lookup(leading_zeros)

3.6 Resource Deposit

Derived from merkle_root[0:2] — an independent entropy source from the block hash, ensuring the mineral deposit is uncorrelated with biome, weather, and stellar class.

resource_byte = parseInt(merkle_root[0:2], 16)   // range 0–255

3.7 Historical Era

3.8 Temporal Modifiers

3.9 Trait Summary

Every Bitcoin block deterministically produces the following cosmic traits. Each trait is derived from a single on-chain field, with no external input.

4. Special Flags & Cosmic Phenomena

Special flags are boolean properties layered onto any block, independent of Stellar Class or Economy. Active flags trigger dedicated visual effects in both the 3D star map and the sidebar trait panel. Flags are not mutually exclusive.

🌅 4.0 — GENESIS SIGNAL

2 0 0 9 0 1 0 3

Attribute	Value
Display name	Genesis Signal
Icon	🌅
Pattern	20090103 — found inside transaction hashes on the block page
What it encodes	January 3, 2009 — the date Satoshi Nakamoto mined the Bitcoin Genesis Block (Block 0)
Supply	23 confirmed blocks of ~950,000 mined (<0.003% — rarest flag in the system)
Some known blocks	350315, 351614, 450967, etc

How to manually verify a block

1. Navigate to ordinals.com/block/{height} in your browser — e.g. ordinals.com/block/851335
2. Open your browser's find bar — Menu → Find and edit, or press Ctrl+F / ⌘F
3. Type 20090103 and press Enter
4. If the pattern exists in one of the block's transaction hashes, your browser will highlight and jump to it — shown as "1/1" or higher in the search bar

Visual effects when active

Sidebar: Full-width premium card with animated gold border pulse, the pattern in spaced monospace, encoded date, and rarity note.

3D star map — seven stacked layers:

Layer	Detail
Blazing core orb	White-gold at 2.5× coreRadius — brightest center in the system
Gold bloom	Secondary warm glow at 4.5× coreRadius
3× sunrise rings	Concentric tilted tori at 1.55×, 1.95×, 2.42× coreRadius, each spinning independently
Sacred icosahedron	Gold wireframe at 1.2× coreRadius, dual-axis rotation
16 dawn beams	Radial light lines pulsing outward, individual frequencies
24 orbit particles	Golden dots revolving in warm orbital band, twinkle-animated
Outer halo	Diffuse gold at 8× coreRadius — tints entire scene warm gold

All pre-existing nebula particles receive a +0.30 opacity boost. Field particles scale ×1.5 and shift to #ffd700.

Verification — Pattern highlighted in browser

▲  ordinals.com/block/350315 — browser Ctrl+F highlighting 20090103 inside a transaction hash (1/1 match)

4.1 All Special Flags

5. 3D Rendering Engine

Stack: Three.js r160, OrbitControls, WebGL 2.0.

Scene layers: background stars, inner nebula (particle count scales with civilization & rarity), bright heart, geodesic cages (Rare+), field particles, aura rings (Legendary+), and a resource deposit ring (all classes) — a thin orbital torus and clustered particles colored by mineral type.

5.1 Resource Deposit Visuals

Every star system renders a mineral deposit ring at coreRadius × 1.75. Opacity and particle count scale with rarity:

5.2 Standout Visuals for Rare Resources

Crystal (Rare — ~1.2% of blocks)

Rotating wireframe octahedron (cyan), prismatic counter-rotating ring, 18 independently-twinkling sparkle particles.

Void Matter (Epic — ~0.4% of blocks)

Solid black event horizon sphere, dark purple accretion disk spinning at 0.015 rad/frame, 40-particle inward spiral arms, dark outer halo.

6. User Interface & Interaction

Controls: block height input, prev/next navigation, random warp, keyboard arrows, R key for random, mouse drag to orbit, scroll to zoom. URL persistence via ?block=. Verification link to ordinals.com/r/blockinfo/{height}.

Resource badges: Crystal and Void Matter trait cards receive animated borders, glowing badges, and CSS pulse animations so users immediately spot rare mineral deposits.

7. Namespace & Ownership

• Parent
  <height>.bitcoin — the world's deed; first confirmed inscription wins permanently.
  Rule: The block height must exist at inscription time (≤ current block height). Pre‑inscribing future blocks is not permitted – the namespace is only valid for already‑mined blocks.
• Child 1
  image.png inscribed under <height>.bitcoin — the visual artifact, cryptographically linked to ownership
• Child 2
  metadata.json sibling child under <height>.bitcoin — protocol envelope for indexers; carries "p": "bitcoinuniverse", "op": "artifact", "block", "hash", "traits"

The namespace inscription is the ownership claim. Without it, a visual artifact carries no binding on-chain identity. The image inscribed as a child of the namespace is provably linked to the owner — anyone can trace the child's parent and verify provenance without trusting any platform.

8. Security & Trust Model

All generation is client-side, deterministic, and verifiable. Source: ordinals.com public endpoint. Caching prevents replay attacks. No private keys, no wallets, no backend.

9. Performance Characteristics

10. Conclusion

11. Ordinals Artifact & Inscription

Bitcoin Universe worlds are fully deterministic and publicly verifiable. Any holder who wishes to make their block's star system a permanent on-chain artifact may do so independently and permissionlessly using standard Ordinals tooling.

11.1 The Parent-Child Model

The canonical ownership structure uses three linked inscriptions:

11.2 Two Distinct Sellable Assets

The parent-child model creates two independent on-chain assets with different ownership semantics:

An owner could keep the parent (holding the world's identity forever) while selling the child artifact to a collector. Or sell the parent and transfer everything. This creates two tiers of ownership with genuinely different value propositions — decided entirely by the owner, with no platform involvement.

11.3 Convention

12. Disclaimer