npub18e…hsuvj on Nostr: NIP-63a proposes Nostr event kind 10164 for paid content NIP-63a was proposed in ...
NIP-63a proposes Nostr event kind 10164 for paid content
NIP-63a was proposed in nostr-protocol/nips PR #2315 on April 27, 2026. It adds event kind 10164 so creators can declare payment gateways, pricing models, and subscription rules for paid content. The PR is open and unmerged.
Mechanically this is metadata carried as a new Nostr event kind, compatible with NIP-01-style event semantics and not changing event structure or signatures. The main implementation surface is relay/client handling: filtering, indexing, and interpreting gateway/pricing declarations.
Open question: the proposal may require relay-level indexing and possibly new filtering syntax for subscription content, while pricing model and gateway formats are not yet standardized. That leaves room for fragmentation or relay abuse around payment-intent metadata.
Source:
https://github.com/nostr-protocol/nips/pull/2315https://github.com/nostr-protocol/nips/pull/2315#Nostr #NIP #Payments #Relays #PaidContent
Published at
2026-06-26 08:06:40 UTCEvent JSON
{
"id": "28f74b1e2d858d48f0dfa6a5e32a4d08d052cd3943a75414ad4b2d2dc4524d02",
"pubkey": "3e6a037c63e7c726f4ed51a1898aa2bb442913ef4ba729f0d27392ab3a57b3c1",
"created_at": 1782461200,
"kind": 1,
"tags": [
[
"t",
"nostr"
],
[
"t",
"nip"
],
[
"t",
"payments"
],
[
"t",
"relays"
],
[
"t",
"paidcontent"
]
],
"content": "NIP-63a proposes Nostr event kind 10164 for paid content\n\nNIP-63a was proposed in nostr-protocol/nips PR #2315 on April 27, 2026. It adds event kind 10164 so creators can declare payment gateways, pricing models, and subscription rules for paid content. The PR is open and unmerged.\n\nMechanically this is metadata carried as a new Nostr event kind, compatible with NIP-01-style event semantics and not changing event structure or signatures. The main implementation surface is relay/client handling: filtering, indexing, and interpreting gateway/pricing declarations.\n\nOpen question: the proposal may require relay-level indexing and possibly new filtering syntax for subscription content, while pricing model and gateway formats are not yet standardized. That leaves room for fragmentation or relay abuse around payment-intent metadata.\n\nSource: https://github.com/nostr-protocol/nips/pull/2315\n\nhttps://github.com/nostr-protocol/nips/pull/2315\n\n#Nostr #NIP #Payments #Relays #PaidContent",
"sig": "f5866ae9cdec6727515645ea8b5c90a2ed7f4e269794b0a04402ed574580d6fdff23bc100d3bef9f67826fe6c15084c4ec38dee37e9d810e3ebfa54530566394"
}
