Denver#6
Draft
mk-Denver wants to merge 2 commits into
Draft
Conversation
Define a user-friendly agent identifier built on NIP-05 (DNS-backed handle-to-pubkey mapping) and NIP-19 (nprofile sharing artifacts). - short code is a NIP-05 internet identifier, verified via .well-known/nostr.json - declared through kind 0 profile (nip05 field) and the PIP-00 agent definition event (short_code content field + nip05 tag) - nprofile used for copy-paste/QR sharing with relay hints - pubkey remains canonical identity; short code is discovery/display only - marked Recommended, sitting outside the required core baseline - update README and AGENTS.md to include PIP-04 in the series Co-authored-by: shakespeare.diy <assistant@shakespeare.diy>
Contributor
|
@Denver-1st , I'm not convinved we need agent discovery as a dedicated PIP-04 just yet. We could focus on proving PIP-00 through PIP-03 before we extend to the discovery mechanisms and human friendly tags for agents. Marking this PR as a draft while we make further considerations |
Author
|
Sounds good.I'll leaving this PR in draft for now and shift focus toward validating PIP-00 through PIP-03. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What PIP-04 defines
The agent short code is a compact, human-friendly identifier (e.g. k45sud@pontmore.example) that lets users discover, verify, and share agents without handling raw pubkeys. It reuses two existing Nostr standards rather than inventing a new resolver:
NIP-05 — discovery & verification
A short code is a NIP-05 internet identifier: @
The domain serves .well-known/nostr.json, mapping the handle to the agent's hex pubkey
Clients verify the mapping against both the kind 0 profile nip05 field and the agent definition's content.short_code
NIP-19 — sharing
nprofile bech32 encoding bundles the pubkey with relay hints for copy-paste / QR-code sharing
The short code is the human-typed entry point; the nprofile is the shareable artifact
Key design positions
Pubkey stays canonical. The short code is a verified alias for discovery and display only. Clients always follow the pubkey and must not silently swap identities if a short code later resolves elsewhere.
No new event kind. It's declared through the existing kind 0 profile and the PIP-00 agent definition event (a short_code content field plus an optional nip05 tag for indexing).
Stays out of the swap state machine. Swap events (PIP-02) use pubkeys for all normative participant references; the short code may appear only as a human-readable display label.
Verification ≠ trust. A verified short code confirms a handle maps to a pubkey, not that the agent is trustworthy — that remains the job of PIP-00/01/03.
Labeling
It's marked Recommended (not Required), so it sits alongside but outside the required core baseline (PIP-00–03). The README framing and AGENTS.md spec list both reflect this.
Files changed
New: PIP-04-agent-short-code.md
Updated: README.md (PIP series + framing), AGENTS.md (spec structure list)