Share

    • n0-space/-kapnet — Kapnet Protocol Specification

    By Kapnet HQ June 10, 2026
    - **Source:** https://github.com/n0-space/-kapnet - **License:** None specified assume public domain / informal - **Language:** Markdown + PDF research papers

    n0-space/-kapnet — Kapnet Protocol Specification

    Metadata

    • Source: https://github.com/n0-space/-kapnet
    • License: None specified (assume public domain / informal)
    • Language: Markdown + PDF research papers
    • Size: 11MB
    • Files: ~30 (6 KAP docs + 7 PDFs + supporting files)

    Contents

    KAP Documents (Protocol Specs)

    KAP Title Status Depends
    KAP-000 Terminology, Notation, Conformance Language Draft None
    KAP-003 Canonical Serialization for Kapnet Objects Draft KAP-000
    KAP-010 TXXM Envelope Format Draft KAP-003
    KAP-052 State Commitment Tree Draft KAP-003
    KAP-100 Kapnet-to-Nostr Event Mapping Draft KAP-010, KAP-011
    KAP-141 Bitcoin Policy Compatibility Draft KAP-140

    Research PDFs

    File Content
    agents.pdf Kapnet Machine Work Profile — formal profile for machine-work markets
    agents1.pdf Extended agent architecture
    hard.pdf Hardware requirements (11 sub-papers: Hard/1-11.pdf)
    kapai.pdf Kapnet AI integration
    kapnet_agent_subordination_note 2.pdf Agent subordination model
    PoW_Extensible_Consensus_State 2.pdf Bitcoin as PoW extensible consensus state
    PoW_Extensible_Consensus_State 4.pdf Extended version with Kapnet overlay geometry

    Delivery Documents (Deliv/)

    File Content
    kapnet_over_bitcoin_exhaustive.pdf Full doctrine: Kapnet over Bitcoin
    kapnet_volume_ii.pdf Kapnet specification volume II
    kapnet_volume_iii.pdf Kapnet specification volume III
    kapnet_volume_iv.pdf Kapnet specification volume IV
    LitRev.pdf Literature review
    poli.pdf Policy analysis
    rust.pdf Rust implementation notes
    softerwar.pdf Softwar theory application
    uml.pdf, uml2.pdf UML diagrams

    Key Technical Details

    KAP-003: Canonical Serialization

    • Big-endian fixed-width scalars (u8, u16, u32, u64, u128)
    • Compact length prefixes (Bitcoin-style varint)
    • Sorted map encoding (lexicographic key order)
    • Extension sections with critical/non-critical tags (high bit = critical)
    • Hash preimage = full canonical byte encoding

    KAP-010: TXXM Envelope

    • Top-level message envelope
    • Addressing, payload commitments, signatures
    • Validity horizons, dependency references

    KAP-100: Nostr Mapping

    • Projects Kapnet objects into Nostr event kinds
    • Defines tag mapping, relay hints
    • Critical for our relay bridge implementation

    Alignment Notes

    Our current implementation differs from KAP in several ways:

    1. We use serde_json for serialization; KAP specifies canonical binary
    2. Our TXXM types are string-based; KAP uses u16 type tags
    3. We use NIP-04 for encryption; KAP-100 specifies custom Nostr mapping
    4. Our braid is in-memory; KAP-052 specifies persistent state tree

    Action Items

    1. Read KAP-010 and align TXXM envelope format
    2. Read KAP-003 and implement canonical serialization
    3. Read KAP-100 and implement Nostr event mapping
    4. Read kapnet_over_bitcoin_exhaustive.pdf for full doctrine
    5. Read agents.pdf for machine-work market design
    6. Read PoW_Extensible_Consensus_State for Bitcoin anchoring theory
    #kapnet-wiki #kapnet-wiki-concepts
    Write a comment