Skip to content

Skill provenance via blocktrails anchoring #183

Description

@melvincarvalho

Context

With the pay API complete (v0.0.105), JSS can now serve paid resources with NIP-98 auth, sat deposits, and token buy/withdraw — all anchored to Bitcoin via blocktrails.

A natural next step: signed, anchored skills for the agentic ecosystem.

Concept

Agent skills (SKILL.md / agent definitions) are evolving documents. Anchoring them to blocktrails gives:

  1. Verifiable authorship — author signs with Nostr key (did:nostr)
  2. Version history — each update is a state in a hash chain
  3. Immutable audit trail — Bitcoin anchor proves no retroactive tampering
  4. Paid distribution — premium skills behind /pay/* with provenance

A skill blocktrail profile might look like:

{
  "profile": "mono.skill.v0.1",
  "name": "deploy",
  "author": "<nostr pubkey>",
  "content": "<SHA-256 of SKILL.md>",
  "version": "1.2.0",
  "prev": "<hash of previous state>"
}

Each version update advances the trail on Bitcoin. Anyone can verify the full history.

Related

  • AAM (Agentic App Manager): https://aam.wtf/ — already does did:nostr signing for skills
  • Blocktrails anchoring would add the temporal provenance layer
  • JSS pay API could serve as distribution infrastructure

What this unlocks

  • Trust: not just "who wrote this" but "how has it changed, provably"
  • Marketplace: paid skills with Bitcoin-backed provenance
  • Audit: enterprises can verify skill supply chain integrity

Metadata

Metadata

Assignees

No one assigned

    Labels

    agenticIssues and PRs related to agentic / LLM-builder / agent-friendly use casesnostrNostr relay, did:nostr auth, NIP-relatedpluginCould be implemented as a plugin (#206); core/plugin line defined in #564

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions