• Kapnet Erudition Campaigns — Three Hashtag Strategies
  • Campaign 1: #KapnetExplainers
    • Content Calendar (First 2 Weeks)
    • Engagement Tactics
    • KPIs
  • Campaign 2: #KapnetBuilds
    • Content Calendar (First 2 Weeks)
    • Engagement Tactics
    • KPIs
  • Campaign 3: #KapnetStudy
    • Content Calendar (First 4 Weeks)
    • Engagement Tactics
    • KPIs
  • Cross-Campaign Strategy
    • Hashtag Hierarchy
    • Voice Guidelines
    • Automation via Publicity Loop
    • Campaign Rotation
    • Reply Handling Priority
    • Success Metrics (30-day)

§Kapnet Erudition Campaigns — Three Hashtag Strategies

§Campaign 1: #KapnetExplainers

Goal: Break down Kapnet protocol concepts into digestible public notes. Audience: Crypto-native developers, Bitcoin curious, protocol researchers. Format: Thread-style notes (kind-1), each explaining one concept. Tone: Technical but accessible. Assume Bitcoin literacy, teach Kapnet specifics.

§Content Calendar (First 2 Weeks)

§Engagement Tactics

• End each note with a question to invite replies
• Reply to every response within 1 hour
• Cross-reference earlier explainers
• Pin the series as a profile highlight

§KPIs

• Notes published: 14
• Target reply rate: >30%
• Target follower growth: >50 new followers
• Hashtag impressions: >1000

§Campaign 2: #KapnetBuilds

Goal: Show Kapnet being built in public. Live development updates. Audience: Builders, open-source contributors, potential collaborators. Format: Short progress notes (kind-1) + milestone threads (kind-30078). Tone: Raw, unpolished, honest. Here’s what we built today. Here’s what broke.

§Content Calendar (First 2 Weeks)

§Engagement Tactics

• Ask for input on every “what should we build” note
• Share actual code snippets (not descriptions)
• Show failures, not just wins
• Tag other builders/projects when relevant
• Invite contributions via GitHub (when kor.git is ready)

§KPIs

• Notes published: 14
• Target replies with technical feedback: >20%
• GitHub stars (when repo is public): target 50
• Collaborator applications: >5

§Campaign 3: #KapnetStudy

Goal: Deep protocol study group. Collaborative learning, not broadcasting. Audience: Protocol researchers, Bitcoin academics, formal verification people. Format: Long-form study notes (kind-30078), weekly reading threads, open problems. Tone: Academic, rigorous, collaborative. We don’t have all the answers.

§Content Calendar (First 4 Weeks)

§Week 1: Foundations

§Week 2: Coordination Layer

§Week 3: Economics of Coordination

§Week 4: Governance and Evolution

§Engagement Tactics

• Every open problem note has a CTA: “Reply with your analysis”
• Best community contributions get their own spotlight note
• Weekly synthesis: summarize the best replies
• Invite academic collaboration: “We need formal verification help”
• Cross-reference related work: Creds papers, Bitcoin research, distributed systems theory

§KPIs

• Study notes published: 20
• Open problems posed: 4
• Quality replies per problem: >3
• Academic/researcher followers: >10
• Paper citations (long-term): reference our open problems

§Cross-Campaign Strategy

§Hashtag Hierarchy

#kapnet                 → umbrella (all campaigns)
#kapnet-explainers      → campaign 1 (education)
#kapnet-builds          → campaign 2 (development)
#kapnet-study           → campaign 3 (research)
#kapnet-open-problems   → cross-campaign (all open problems)
#kapnet-churn          → live coordination
#kapnet-kor            → namespace announcements

§Voice Guidelines

• No hype, no moon talk, no price mentions
• Technical precision over marketing speak
• Cite sources, link to codebase, show your work
• Admit what you don’t know
• Invite correction and collaboration

§Automation via Publicity Loop

The publicity-loop.cjs manages all three campaigns:

Content queue structure:

{
  "queue": [
    {
      "id": "exp-001",
      "campaign": "explainers",
      "status": "pending",
      "priority": "high",
      "content": "...",
      "tags": ["kapnet", "kapnet-explainers", "txxm"]
    },
    {
      "id": "bld-001",
      "campaign": "builds",
      "status": "pending",
      "content": "...",
      "tags": ["kapnet", "kapnet-builds", "progress"]
    },
    {
      "id": "std-001",
      "campaign": "study",
      "status": "pending",
      "content": "...",
      "tags": ["kapnet", "kapnet-study", "foundations"]
    }
  ]
}

§Campaign Rotation

• Explainers: daily (high frequency, low effort)
• Builds: 3x/week (medium frequency, medium effort)
• Study: 2x/week (low frequency, high effort, high value)

§Reply Handling Priority

1. Open problem replies (study) — highest priority, need thoughtful response
2. Technical feedback (builds) — high priority, acknowledge and act
3. Questions (explainers) — medium priority, answer within 24h
4. General engagement — standard priority, acknowledge within 48h

§Success Metrics (30-day)