{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"thinker-satoshi-nakamoto","urls":{"read":"https://miscsubjects.com/api/articles/thinker-satoshi-nakamoto/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/thinker-satoshi-nakamoto/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/thinker-satoshi-nakamoto/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/thinker-satoshi-nakamoto/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/thinker-satoshi-nakamoto/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/thinker-satoshi-nakamoto/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/thinker-satoshi-nakamoto/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"thinker-satoshi-nakamoto","title":"Satoshi Nakamoto — Bitcoin and the Append-Only Ledger","register":"standard","tags":["oip","kimi-import","self-explaining","voxel","thinkers","thinker-satoshi-nakamoto"],"updated_at":"2026-07-15T04:20:47.315Z","body_excerpt":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Thinkers](https://miscsubjects.com/a/oip-thinkers) › **Satoshi Nakamoto — Bitcoin and the Append-Only Ledger**\n>\n> **Shelf:** Thinkers · **Traversal:** self-explaining · hierarchical · voxel-ready\n> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)\n\n# Satoshi Nakamoto — Bitcoin and the Append-Only Ledger\n\n## §SELF — thinker-satoshi-nakamoto\n\n**What this page is:** A profile of the pseudonymous creator of Bitcoin and the technical mechanisms they invented.\n**What it explains:** How Nakamoto combined a chain of cryptographic hashes, computational puzzles, and distributed agreement into a system for recording transactions without a central authority.\n**Why read it:** To understand the building blocks of tamper-evident ledgers and which of those blocks are reusable in non-cryptocurrency systems.\n\n### What Nakamoto Is\n\nNakamoto is a pseudonym used by the person or group who published the Bitcoin whitepaper in 2008 and released the Bitcoin software in 2009. Their identity is unknown.\n\n### Why It Matters\n\nBefore Bitcoin, digital money required a bank or payment company to track who owned what. Nakamoto showed that a group of untrusted computers could maintain a shared record of ownership without any central authority. This removed the single point of failure and the single point of control.\n\n### The Key Idea\n\nNakamoto's key idea is that tamper evidence and distributed agreement can replace trust in a central institution. Each block in the chain contains a hash (a fixed-length fingerprint produced by a mathematical function) of the previous block. If anyone changes data in an old block, the hash no longer matches, and every subsequent block signals the alteration. To add a new block, a node must solve a computationally expensive puzzle (proof of work). This makes rewriting history cost-prohibitive. Nodes agree on which version of history is correct by selecting the longest chain — the one with the most cumulative computational work invested in it.\n\n### What They Got Right\n\n- **Hash chaining as tamper evidence.** Each block references the previous block by hash. This creates a mathematical guarantee: change any past data, and the chain breaks visibly.\n- **Proof of work as a cost function.** Making block creation expensive prevents spam and makes attacks economically irrational. An attacker would need to redo all the work of the honest chain to override it.\n- **The longest-chain rule.** A simple, deterministic way for distributed nodes to agree on a single history without voting or a coordinator.\n- **Append-only by design.** The ledger only grows. Transactions are added, never deleted or edited. This means every entry remains auditable forever.\n- **Receipts as self-verifying proof.** A transaction recorded on the chain is its own proof. No third party certifies it; the chain's structure certifies it.\n- **Open participation.** Anyone can run a node, mine blocks, or submit transactions. No permission is required.\n\n### What They Got Wrong or Left Unfinished\n\n- **Energy consumption.** Proof of work requires enormous electricity use to secure the network. This is by design, but it imposes a real environmental cost.\n- **Scalability.** Bitcoin processes roughly 7 transactions per second. Global payment networks process thousands. The design trades speed for security.\n- **Irreversibility.** If you lose your private key (the secret number that proves you own your coins), your funds are permanently inaccessible. There is no recovery mechanism.\n- **Governance ambiguity.** Technical changes to the protocol require consensus among miners, developers, and users. Disagreements produce forks (splits in the chain), and there is no formal process for resolving them.\n- **The pseudonym.** Nakamoto disappeared ","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[],"sources":[],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"thinker-satoshi-nakamoto","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":0,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":0,"claims_total":0,"sources":0,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}