nprofile1q…fzn42 nprofile1q…0mp2c nprofile1q…f7xwn FWIW TLVs do work with ...

npub1s96…yzak

2024-11-23 18:17:27

in reply to nevent1q…v83e

nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqdf6eyr7x6cv4gq99h3rjnhj6f4yqzxa97pxf2ecxeq82ea8mwdyq4fzn42 (nprofile…zn42) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqu889jx72l4rn6vsva3jqxyhtekq4qhanwh296lz30ajpsrlhuvfqe0mp2c (nprofile…mp2c) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqvpkystedk2lldqlkkyd084tj5e39rpxn7lad6qeq9uka7kfw9jrsuf7xwn (nprofile…7xwn) FWIW TLVs do work with invoice payments the same as keysend payments, at least in lncli:

Invoice payment:
lncli sendpayment --pay_req <invoice> --data <tlv_records>

Keysend:
lncli sendpayment --keysend -d <pubkey> -a <amount> --data <tlv_records>

I've tested this with my Helipad test rig and it works.

However, I don't think it's widely supported by wallet APIs. For example, the Alby API takes an invoice and doesn't have a custom_records field: https://guides.getalby.com/developer-guide/alby-wallet-api/reference/api-reference/payments#bolt11-payment

Author Public Key

npub1s96kwrt20eskfvs9mfxacg9krxq3pcj0vt22e4unknqk0wu3rv7qm8yzak

Show more details

Published at

2024-11-23 18:17:27

Kind type

1 Short Text Note

Event JSON

{ "id": "e9414cba3675b01397599a0b85c68b373a6a4514e9cd2388e3d4736b399daa5d", "pubkey": "8175670d6a7e6164b205da4ddc20b6198110e24f62d4acd793b4c167bb911b3c", "created_at": 1732385847, "kind": 1, "tags": [ [ "p", "6a75920fc6d6195400a5bc4729de5a4d48011ba5f04c956706c80eacf4fb7348", "wss://relay.mostr.pub" ], [ "p", "e1ce591bcafd473d320cec640312ebcd81505fb375d45d7c517f64180ff7e312", "wss://relay.mostr.pub" ], [ "p", "606c482f2db2bff683f6b11af3d572a6625184d3f7fadd03202f2ddf592e2c87", "wss://relay.mostr.pub" ], [ "p", "0defbe4cf05d9acfedd61b9421e7cb6b72165b4e6749840320735a27d47e1447", "wss://relay.mostr.pub" ], [ "p", "1d9641cfd78d02e278739e563e1229e843f9ea250b73887c8a186bfae948fbbe", "wss://relay.mostr.pub" ], [ "p", "5020099b0d106f8433f87f9274bae9f98b66326206d852dcf16e15f94cd9711b", "wss://relay.mostr.pub" ], [ "zap", "8175670d6a7e6164b205da4ddc20b6198110e24f62d4acd793b4c167bb911b3c", "wss://relay.mostr.pub", "0.915" ], [ "zap", "6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9", "wss://relay.mostr.pub", "0.085" ], [ "e", "3371fe15aa3e2175be57027317a50ba1090699c1e5708f61430150fd76f5c6f6", "wss://relay.mostr.pub", "reply" ], [ "proxy", "https://podcastindex.social/users/ericpp/statuses/113533638923194714", "activitypub" ] ], "content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqdf6eyr7x6cv4gq99h3rjnhj6f4yqzxa97pxf2ecxeq82ea8mwdyq4fzn42 nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqu889jx72l4rn6vsva3jqxyhtekq4qhanwh296lz30ajpsrlhuvfqe0mp2c nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqvpkystedk2lldqlkkyd084tj5e39rpxn7lad6qeq9uka7kfw9jrsuf7xwn FWIW TLVs do work with invoice payments the same as keysend payments, at least in lncli:\n\nInvoice payment:\nlncli sendpayment --pay_req \u003cinvoice\u003e --data \u003ctlv_records\u003e\n\nKeysend:\nlncli sendpayment --keysend -d \u003cpubkey\u003e -a \u003camount\u003e --data \u003ctlv_records\u003e\n\nI've tested this with my Helipad test rig and it works. \n\nHowever, I don't think it's widely supported by wallet APIs. For example, the Alby API takes an invoice and doesn't have a custom_records field: https://guides.getalby.com/developer-guide/alby-wallet-api/reference/api-reference/payments#bolt11-payment", "sig": "f9f8932c108e0133bdab82fb0643b44a3f8b6ed1b45aae61f7080cd18652b50df76f8963db84c464c2bfe9df7445f7f049e7283918ec4e28598644d8a587d517" }