The node (pub) subscribes at the relay for any of the supported kinds addressed to its nostr key. The nostr key isn't necessarily bound to the lightning key, it's just a wrapper, so it could have multiple, be in a round robin, etc
Alice, if her wallet supports CLINK, could request an invoice directly from your node via its noffer string (relay, key, pointer). You can sleep, as long as your node is real and online like an email server.
For wallets that don't support CLINK, offers are useful in web apps since bolt11 is the lingua franca... This makes it useful for webshops etc. The nostr transport also solves payer_data, like email, T-shirt size, SKU
It also removes the trust inherent to a lnurl bridge that could change the delivered invoice, and let's apps be static pages rather than a service.
Example, this is just html css and js, no server process:
https://pay.shockwallet.app/?noffer=noffer1qvqsyqjqxyenyctpxgukzwf38psnzve5vgcngdf3vvunjc35vdjnserpvgmnscfjvdjnxd33xdnrydp4vgukze3nx4skgcfnxsuxgctpxyunyeqprfmhxue69uhhxarjvee8jtnndphkx6ewdejhgam0wf4sqgrka4zlqr820wk9nkxsklfqfpy02vva0wtvzs8lkm7t424s5y75fchungtv
shocknet_justin / Justin (shocknet) ⚡
npub1xv…e64sa
2026-09-18 22:41:02 GMT
in reply to nevent1q…n022
Author Public Key
npub1xvtwx6tduaxnn9v3y7uasskl277achgu0tu2qncmc7hdsz6y2zyqce64saPublished at
2026-09-18 22:41:02 GMTEvent JSON
{
"id": "80ae175b5f8eb4fc2d705885caf5eccfd79b02f5e553b245e9e2f3e537b58d45",
"pubkey": "3316e3696de74d39959127b9d842df57bddc5d1c7af8a04f1bc7aed80b445088",
"created_at": 1789771262,
"kind": 1111,
"tags": [
[
"A",
"30023:16f1a0100d4cfffbcc4230e8e0e4290cc5849c1adc64d6653fda07c031b1074b:skU_qA4TXtjHX5sb3hq6n",
""
],
[
"E",
"40b8364bfa218531f7fbbe085c8ddcb3d03cce4e9b7c68d46b4af80f76bea984",
"",
"16f1a0100d4cfffbcc4230e8e0e4290cc5849c1adc64d6653fda07c031b1074b"
],
[
"K",
"30023"
],
[
"P",
"16f1a0100d4cfffbcc4230e8e0e4290cc5849c1adc64d6653fda07c031b1074b"
],
[
"e",
"0d7fddcb7b53134bd0daad3812852b2b9aed86c17801d3ba4fbda488447d4d67",
"",
"7286946a0e00a4861eb7547ee0a98d476ae2bdd359b32da6a24dc6efbedc1002"
],
[
"k",
"1111"
],
[
"p",
"7286946a0e00a4861eb7547ee0a98d476ae2bdd359b32da6a24dc6efbedc1002"
]
],
"content": "The node (pub) subscribes at the relay for any of the supported kinds addressed to its nostr key. The nostr key isn't necessarily bound to the lightning key, it's just a wrapper, so it could have multiple, be in a round robin, etc\n\nAlice, if her wallet supports CLINK, could request an invoice directly from your node via its noffer string (relay, key, pointer). You can sleep, as long as your node is real and online like an email server.\n\nFor wallets that don't support CLINK, offers are useful in web apps since bolt11 is the lingua franca... This makes it useful for webshops etc. The nostr transport also solves payer_data, like email, T-shirt size, SKU\n\nIt also removes the trust inherent to a lnurl bridge that could change the delivered invoice, and let's apps be static pages rather than a service.\n\nExample, this is just html css and js, no server process: \n\nhttps://pay.shockwallet.app/?noffer=noffer1qvqsyqjqxyenyctpxgukzwf38psnzve5vgcngdf3vvunjc35vdjnserpvgmnscfjvdjnxd33xdnrydp4vgukze3nx4skgcfnxsuxgctpxyunyeqprfmhxue69uhhxarjvee8jtnndphkx6ewdejhgam0wf4sqgrka4zlqr820wk9nkxsklfqfpy02vva0wtvzs8lkm7t424s5y75fchungtv",
"sig": "24148b2b56c99a44036fae328db39e45f8216e92ff366444f68379e5b2f43484b27528151d861bc170accf8a754fdee3a295fe384bb0bb95c532f53749a0b215"
}