Conversation
Rebased onto current master; spec only. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Value transfer operations, rail and status enums, targets, quotes, results, and status records now use the shared CDDL-style schema notation instead of TypeScript declarations. Constraint: Keep this branch scoped to NAP-VALUE. Confidence: high Scope-risk: narrow Tested: git diff --check Tested: rg found no TypeScript code fences or declarations in naps/NAP-VALUE.md
The value rail, target, quote, result, and status schemas now use Markdown tables instead of a CDDL-style block. The rail extension point and zap/LNURL target semantics remain unchanged. Constraint: PR #30 owns NAP-VALUE; keep this change scoped to that spec file. Confidence: high Scope-risk: narrow Tested: rg for cddl/typescript schema fences and type assignment patterns in NAP-VALUE Tested: git diff --check -- naps/NAP-VALUE.md
Open NAP proposal branches need reader-visible changelogs that track semantic spec changes without recording formatting-only migrations. Constraint: Changelog entries are one bullet per semantic commit-change. Rejected: Include schema-table or formatting-only commits | they do not change the spec contract or boundary. Confidence: high Scope-risk: narrow Directive: Keep future changelog entries semantic; omit changelog-only and formatting-only commits. Tested: git diff --check Not-tested: Rendered Markdown
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.
Summary
Adds NAP-VALUE, a shell-mediated value-transfer interface for napplets. It generalizes the zap-sending need from hyprgate/gui#5 beyond a NAP-PAY-only surface so future value rails can fit under the same runtime boundary.
Namespace
window.napplet.valueStatus
draftChanges
value.quote,value.send,value.status, and shell-pushedvalue.status.changed.zap,lnurl, or runtime-defined strings.relaylayering dependency for zap receipt publish/query paths.Downstream
Napplets submit value-transfer intent, not wallet credentials, NWC secrets, signing keys, direct payment backend access, or opaque payment payloads. Runtimes can support zaps first while preserving a generic value rail surface.
Reference
Changelog
2c56394- Introduced NAP-VALUE for shell-mediated value transfer.