NIP-OA: Owner Attestation for agent key provenance#398
Merged
Conversation
Defines an optional 'auth' tag that lets an owner key authorize an agent key via a BIP-340 Schnorr signature. The agent carries the 64-byte proof in its events. Anyone can verify the relationship without querying a relay. The two keys are independent — agent compromise does not compromise the owner. Reuses NIP-26's proven signing mechanism with different semantics: the event author stays as the agent. The tag is a credential, not an identity override. Relays require no changes.
…ation, timestamp honesty - Explicit that auth tag is a reusable capability (same tag on multiple events) - Numeric bounds: kind 0-65535, timestamps 0-4294967295 - MUST NOT reorder/deduplicate/normalize conditions before hashing - created_at conditions constrain self-declared timestamp, not wall-clock time - Misbehaving agent can backdate; freshness enforcement is out of scope
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
1 participant
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.
Adds a draft NIP spec for proving agent-to-owner key relationships on nostr.
What
An optional
authtag that lets an owner key authorize an agent key via a BIP-340 Schnorr signature. The agent carries the 64-byte proof in its events. Anyone can verify the relationship without querying a relay. The two keys are independent — agent compromise does not compromise the owner.Why
AI agents need verifiable provenance. Agents run LLMs that can be prompt-injected, so key derivation schemes (where agent secret leak → owner secret compromised) are not viable. This NIP uses independent keys with a signed attestation instead.
Reuses NIP-26's proven signing mechanism with different semantics: the event author stays as the agent. The tag is a credential, not an identity override. Relays require no changes.
What's in the spec
sha256("nostr:agent-auth:" || agent_pubkey || ":" || conditions))kind=,created_at<,created_at>)