Jun 10, 2026

KOR Registry — Active Kapnet Operational Realms

Formal registry of all active KORs: sys.pluronymous.org, sys.kapnet, sys.external, sys.encrypted

KOR Registry — Active Kapnet Operational Realms

sys.pluronymous.org (Root KOR)

Status: ACTIVE Operator: GELI (AUTH_7) via HermQube Created: 2026-06-09 Purpose: Public coordination realm of Pluronymous LLC. Open membership, transparent governance, Bitcoin-anchored.

Governance

  • Voting model: Hedlbit-weighted (1 Hedlbit = 1 vote)
  • Quorum: 51% of active Hedlbit holders
  • Proposal period: 7 days
  • Execution: Deterministic (passed proposals auto-execute via KScript)

Tiers

TierPriceGovernanceChatDocs
ObserverFreeRead-onlyRead-onlyRead-only
Member10K sats/mo1x weightRead+WriteRead+Write
Maintainer50K sats/mo5x weightAdminAdmin + Create
Operator200K sats/mo25x weightFullFull + Treasury

Members (formalized)

npubTierGrantedStatus
npub1dwpeuyfuj... (Ambassador)Operator2026-06-09Active
npub1tpg4xgprr... (Operator)Operator2026-06-09Active
npub1ly7elxl5... (owl-mkctp-alpha)Maintainer2026-06-10Active

Encrypted Group

  • Protocol: MLS via Whitenoise/Marmot
  • Group ID: pluronymous-member-${Date.now()}
  • Key derivation: KOR-scoped HMAC-SHA256
  • Transport: Nostr kind-30078 (encrypted content)
  • Persistence: Relay-archived, braid-ordered

sys.kapnet (Protocol KOR)

Status: ACTIVE Operator: Pluronymous LLC (via HermQube) Created: 2026-06-09 Purpose: Protocol development, specification discussion, cross-node coordination.

Governance

  • Voting model: One-node-one-vote (consensus, not weighted)
  • Quorum: 2/3 of known nodes
  • Proposal period: 14 days
  • Execution: Requires knot checkpoint from 2+ nodes

Tiers

TierPriceCapabilities
ObserverFreeRead protocol specs, submit comments
ContributorFree (merit)Submit proposals, review specs
MaintainerFree (elected)Merge specs, manage releases
OperatorBy appointmentProtocol-level changes

Members

npubTierStatus
npub1dwpeuyfuj... (Ambassador)OperatorActive
npub1ly7elxl5... (owl-mkctp-alpha)MaintainerActive
npub12u6s4n4ud... (first-light)ContributorPending
npub17mn5pjrn3... (kapnet-chronicle)ContributorPending

sys.external (Partnership KOR)

Status: PENDING Operator: TBD Created: Not yet created Purpose: Cross-organizational coordination. For external organizations running Kapnet nodes.

Governance

  • Voting model: Delegated (each org gets votes proportional to contribution)
  • Quorum: 67% of represented organizations
  • Proposal period: 30 days
  • Execution: Requires 2-of-3 multisig from founding operators

Tiers

TierPriceCapabilities
ObserverFreeRead public proposals
PartnerNegotiatedSubmit proposals, vote
FounderBy invitationFull governance, treasury access

Members

npubTierStatus
npub1dwpeuyfuj... (Ambassador)FounderPending activation

sys.encrypted (Private Coordination KOR)

Status: PENDING Operator: GELI (AUTH_7) Created: Not yet created Purpose: Encrypted coordination for sensitive operations. Treasury, legal, personnel.

Governance

  • Voting model: Unanimous consent (all operators must agree)
  • Quorum: 100% of operators
  • Proposal period: None (real-time consensus)
  • Execution: Immediate upon unanimous consent

Tiers

TierPriceCapabilities
OperatorBy invitation onlyFull access, treasury, legal

Members

npubTierStatus
npub1tpg4xgprr... (Operator)OperatorPending activation

KOR Creation Protocol

To create a new KOR:

  1. Submit KOR-proposal TXXM to sys.pluronymous.org with:

    • KOR namespace (must be unique)
    • Purpose statement
    • Governance model
    • Tier definitions
    • Initial operator npub(s)
  2. Governance vote in sys.pluronymous.org (quorum: 51% of Hedlbit holders)

  3. Upon approval, publish KOR-announcement TXXM with:

    • KOR namespace
    • Governance parameters
    • Tier definitions
    • Encrypted group parameters
    • Operator contact (npub)
  4. Initialize KOR braid with genesis TXXM

  5. Begin accepting membership TXXMs

KOR Verification

Any Kapnet node can verify a KOR:

  1. Check KOR-announcement TXXM exists on relay
  2. Check operator npub has sufficient authorization
  3. Check governance parameters are valid
  4. Check KOR namespace is unique (not already registered)
  5. Accept KOR as valid coordination realm