Pluronymous KOR — Nostr Content Plan

| Kind | Content | Status | |------|---------|--------| | 0 | Profile: "Kapnet HQ Ambassador" | ✅ LIVE |

Pluronymous KOR — Nostr Content Plan

Already Published (Ambassador npub)

Kind Content Status
0 Profile: “Kapnet HQ Ambassador” ✅ LIVE
1 Intro note: “Greetings from Kapnet HQ Ambassador” ✅ LIVE
30078 Node-info: herm-qubes-alpha ✅ LIVE
30078 KSP service advertisement ✅ LIVE

Content to Draft

Tier 1: Identity & Namespace (Publish First)

KOR-001: Pluronymous Namespace Declaration

Kind: 30078
Tags: [t, kapnet], [t, kor], [t, namespace], [d, kor-pluronymous]
Content: JSON defining the Pluronymous LLC KOR namespace

Content:

{
  "type": "kor_namespace",
  "version": "1.0",
  "id": "sys.pluronymous.org",
  "name": "Pluronymous LLC",
  "description": "Bitcoin-anchored coordination supersubstrate. Kapnet protocol operations, governance, and community.",
  "npub": "npub1dwpeuyfjv27nsl3qma3stqckfwusu053ncasmaru0vsy69d9vdqrcau36",
  "owner": "npub1tpg4xgprr7e58scgp75xt6wlvlgr2wn3cmy20pee7z6lmsxpq6hsuwphfv",
  "kor_level": "k+2",
  "parent_kor": "sys.bitcoin.org",
  "created": 1780966400,
  "relays": ["wss://relay.damus.io", "wss://nos.lol"],
  "sub_namespaces": [
    "member.submission.room.kor",
    "kapnet-public.kor",
    "kapnet-research.kor",
    "treasury.pluronymous.kor",
    "governance.pluronymous.kor"
  ]
}

KOR-002: Member Submission Room

Kind: 30078
Tags: [t, kapnet], [t, kor], [t, room], [d, kor-member-submission]

Content:

{
  "type": "kor_room",
  "version": "1.0",
  "id": "member.submission.room.kor",
  "name": "Member Submission Room",
  "description": "Primary coordination room for Kapnet community. Submit TXXMs, proposals, and governance actions here.",
  "parent_kor": "sys.pluronymous.org",
  "access": "public_read_write",
  "postage": "100 sats per submission",
  "moderation": "governance_vote",
  "created": 1780966400
}

KOR-003: Public Surface

Kind: 30078
Tags: [t, kapnet], [t, kor], [t, public], [d, kor-public]

Content:

{
  "type": "kor_namespace",
  "version": "1.0",
  "id": "kapnet-public.kor",
  "name": "Kapnet Public",
  "description": "Public-facing Kapnet content. Research, documentation, and community resources.",
  "parent_kor": "sys.pluronymous.org",
  "access": "public_read",
  "created": 1780966400
}

Tier 2: Governance & Treasury

GOV-001: Governance Framework

Kind: 30078
Tags: [t, kapnet], [t, governance], [d, gov-framework]

Content:

{
  "type": "governance_framework",
  "version": "1.0",
  "kor": "sys.pluronymous.org",
  "voting_model": "token_weighted",
  "token": "Hedlbit",
  "quorum": "10% of circulating supply",
  "proposal_threshold": "100,000 Hedlbits",
  "voting_period": "7 days",
  "execution_delay": "48 hours",
  "auth_levels": {
    "AUTH_1": "Read public content",
    "AUTH_2": "Read + comment",
    "AUTH_3": "Read + submit TXXMs (paid)",
    "AUTH_4": "Submit governance proposals",
    "AUTH_6": "Execute code (KScript)",
    "AUTH_7": "Full operator control"
  },
  "created": 1780966400
}

TRE-001: Treasury Declaration

Kind: 30078
Tags: [t, kapnet], [t, treasury], [d, tre-declaration]

Content:

{
  "type": "treasury_declaration",
  "version": "1.0",
  "kor": "treasury.pluronymous.kor",
  "cold_storage": "2-of-3 multisig",
  "hot_wallet": "Lightning + on-chain",
  "sweep_threshold": "1,000,000 sats",
  "governance_control": "GOV-001",
  "transparency": "monthly_report",
  "reserve_policy": "100% Bitcoin-backed",
  "created": 1780966400
}

Tier 3: Protocol Specifications (Reference Documents)

SPEC-001: TXXM Envelope Format

Kind: 30078
Tags: [t, kapnet], [t, spec], [t, txxm], [d, spec-txxm-envelope]

Content: Link to KAP-010 spec (or inline summary)

SPEC-002: Hedlbit Accounting

Kind: 30078
Tags: [t, kapnet], [t, spec], [t, hedblitz], [d, spec-hedlbit]

Content: Hedlbit unit definition, pricing, reserve-time derivation

SPEC-003: Mining Pool

Kind: 30078
Tags: [t, kapnet], [t, spec], [t, mining], [d, spec-mining-pool]

Content: Solo pool design, fee structure, payout mechanism

Tier 4: Community Onboarding

WELCOME-001: Getting Started Guide

Kind: 1 (text note)
Tags: [t, kapnet], [t, welcome]

Content:

Welcome to Kapnet.

Kapnet is a Bitcoin-anchored coordination supersubstrate.
Built on. Secured by Bitcoin. Coordinated via Nostr.

To get started:
1. Create a Nostr identity (npub) — use any Nostr client
2. Follow: npub1dwpeuyfjv27nsl3qma3stqckfwusu053ncasmaru0vsy69d9vdqrcau36
3. Read: njump.me/npub1tpg4xgprr7e58scgp75xt6wlvlgr2wn3cmy20pee7z6lmsxpq6hsuwphfv
4. Submit your first TXXM (100 sats postage)
5. Join governance discussions

#Kapnet #Bitcoin #Nostr #KAP #Pluronymous

FAQ-001: Frequently Asked Questions

Kind: 1 (text note)
Tags: [t, kapnet], [t, faq]

Content:

Kapnet FAQ

Q: What is Kapnet?
A: A Bitcoin-anchored coordination supersubstrate. TXXM envelopes carry coordination Nostr-events carry ordering information.

Q: What is a TXXM?
A: Transaction CrossMail — the fundamental Kapnet message unit. Think of it as a coordination transaction.

Q: What is Hedlbit?
A: The Kapnet accounting unit for coordination work. 1 Hedlbit = proof of work + storage rights + governance weight.

Q: How do I participate?
A: Create a Nostr npub, follow the Ambassador, submit TXXMs to member.submission.room.kor.

Q: Is Kapnet a blockchain?
A: No. Kapnet is an overlay protocol. It uses Bitcoin for settlement and Nostr for communication. The braid is the coordination state, not a chain.

Q: Who operates Kapnet?
A: Pluronymous LLC (Wyoming). EIN: 42-2260948. Kapnet HQ Ambassador is the public-facing operator.

#Kapnet #FAQ

Publishing Priority

  1. IMMEDIATE: KOR-001 (namespace declaration) — this is the root of the tree
  2. IMMEDIATE: KOR-002 (member submission room) — where community submits
  3. IMMEDIATE: WELCOME-001 (getting started) — onboarding
  4. WEEK 1: KOR-003 (public surface)
  5. WEEK 1: GOV-001 (governance framework)
  6. WEEK 2: TRE-001 (treasury)
  7. WEEK 2: FAQ-001
  8. WEEK 3-4: SPEC-001, 002, 003 (protocol specs)

Write a comment
No comments yet.