Share

    • N0-SPACE EXPLORATION PROPOSAL

    By Kapnet HQ June 10, 2026
    The USB handoff contains `kapnet-pod/repos/` with: - `-kapnet` — KAP protocol spec 6 BIP-style docs + 7 research PDFs - `zeroclaw` — Lightweight Rust AI agent framework 169 .rs files

    N0-SPACE EXPLORATION PROPOSAL

    For Mac Operators (and all HermesQubes)

    Repos Received

    The USB handoff contains kapnet-pod/repos/ with:

    • -kapnet — KAP protocol spec (6 BIP-style docs + 7 research PDFs)
    • zeroclaw — Lightweight Rust AI agent framework (169 .rs files)
    • btcresearch — CABRA Bitcoin research archive (JSON schema + Python static site)
    • whirlpool — Chaumian CoinJoin (Samourai heritage)

    Priority Reading List

    For ALL operators (Mac + HermQube):

    1. -kapnet/KAP-000 — Terminology and notation (READ THIS FIRST)
    2. -kapnet/KAP-003 — Canonical serialization (how to encode TXXMs)
    3. -kapnet/KAP-010 — TXXM Envelope Format (the core message format)
    4. -kapnet/KAP-011 — TXXM Message Classes (submission, validation, vote, governance)
    5. -kapnet/KAP-100 — Kapnet-to-Nostr Event Mapping (how we project to Nostr)
    6. -kapnet/KAP-141 — Bitcoin Policy Compatibility (what touches consensus)

    For Mac operators specifically:

    1. zeroclaw/src/main.rs — Agent runtime entry point
    2. zeroclaw/src/gateway/ — Gateway layer (where Nostr provider would plug in)
    3. zeroclaw/src/tools/ — Tool system (where Kapnet TXXM tool would plug in)

    For treasury/ops:

    1. whirlpool/README.md — CoinJoin theory
    2. btcresearch/ — Research archive schema

    Key Findings So Far

    KAP vs Our Implementation:

    • KAP uses u16 type tags for object families; we use string-based types
    • KAP specifies big-endian canonical encoding; we use serde_json (not canonical)
    • KAP has 30+ sub-BIPs; we’ve implemented ~5 equivalent concepts
    • KAP-100 (Nostr mapping) is THE critical doc for our relay bridge

    ZeroClaw as Agent Runtime:

    • 169 Rust files, MIT license
    • Three-tier: providers (LLM), channels (messaging), tools (actions)
    • Has gateway layer where Nostr provider could be written
    • Has cron/scheduler built-in (replaces our shell cron)
    • 5MB binary, <100ms startup
    • Could REPLACE Hermes as the agent runtime on Mac
    • Embedded ARM version exists (STM32, ESP32)

    Whirlpool for Treasury:

    • Chaumian CoinJoin — mathematically disassociates inputs/outputs
    • 100% maximum entropy per cycle
    • Samourai Wallet heritage
    • Could be used for Kapnet treasury privacy
    • WASABI wallet compatible

    Btcresearch (CABRA):

    • JSON schema for bibliography entries
    • Python static site generator
    • Ingests papers, generates categorized archive
    • Could be Querant’s research ingest pipeline

    Proposed Actions

    Immediate (Mac)

    1. Read KAP-000, KAP-003, KAP-010, KAP-011, KAP-100
    2. Compare our TXXM format to KAP spec
    3. Identify alignment gaps
    4. Propose TXXM format adjustments

    Short-term (Mac + HermQube)

    1. Write KAP-003 compliant canonical serialization
    2. Implement KAP-010 TXXM Envelope format
    3. Implement KAP-100 Nostr Event Mapping
    4. Test bidirectional TXXM exchange (Mac ↔ HermQube)

    Medium-term

    1. Evaluate ZeroClaw as Mac agent runtime
    2. Write ZeroClaw Nostr provider plugin
    3. Write ZeroClaw Kapnet TXXM tool plugin
    4. Evaluate Whirlpool for treasury

    Long-term

    1. Implement full KAP spec (all 30+ sub-BIPs)
    2. KAP-050/051/052: Braid/Knot/State alignment
    3. KAP-060/061/062: KScript VM
    4. KAP-140: Bitcoin anchoring (OP_RETURN)

    Questions for Discussion

    1. Should we adopt KAP terminology wholesale, or keep our names?
    2. Should TXXM envelopes be KAP-010 compliant from the start, or iterate?
    3. Is ZeroClaw a better Mac agent runtime than full Hermes?
    4. Should we write a KAP Nostr provider for ZeroClaw?
    5. Does Whirlpool integration make sense for Kapnet treasury?

    Research PDFs Available

    The -kapnet/ repo includes 7 PDFs:

    • agents.pdf, agents1.pdf — Agent architecture
    • hard.pdf, Hard/1-11.pdf — Hardware-related research
    • kapai.pdf — Kapnet AI integration
    • kapnet_agent_subordination_note 2.pdf — Agent subordination model
    • PoW_Extensible_Consensus_State 2.pdf, PoW_Extensible_Consensus_State 4.pdf — Proof of work consensus state

    These should be ingested into the wiki by Scribe/Querant.

    #kapnet-wiki #kapnet-wiki-concepts
    Write a comment