NIP-002: Payment URI Scheme - #2
Open
codewordneptune wants to merge 1 commit into
Open
Conversation
Documents a `neptunecash:` payment URI convention (BIP 21 equivalent) for links, QR codes, and deep-linking: motivation, the existing undocumented `NPT:` QR practice, the URI specification with provisional test vectors, open questions, and a comparison of payment URI schemes in other cryptocurrencies. The scheme is spelled out in full rather than as a bare `neptune:`, because the Neptune Privacy (XNT) fork also answers to "Neptune" and OS-level URI handler registration is a single global namespace. The same reasoning gave Bitcoin Cash `bitcoincash:`. Based on the RFC and review discussion in Neptune-Crypto/neptune-core#959.
This was referenced Aug 4, 2026
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 NIP-002, a payment URI scheme for payment links, QR codes, and deep-linking, following up on the RFC discussion in Neptune-Crypto/neptune-core#959. Format follows NIP-001 (#1).
Feedback especially welcome on:
neptunecash:rather than theneptune:originally proposed in the RFC. Open question 2 in the document explains the change: the name "Neptune" is now contested by a fork, and OS-level URI handler registration is a single global namespace.