I suppose it's the last comma. There is not supposed to be a trailing comma in strict JSON.
I suppose it's the last comma. There is not supposed to be a trailing comma in strict JSON.
I suppose it's the last comma. There is not supposed to be a trailing comma in strict JSON.
Hmm Craig@bitcoin-cats.ca seems to be OK as far as I can tell. JSON looks good. Maybe a problem with the upper case C in some clients?
You might also try the nostr.json generator by nostr:npub1s02jksmr6tgmcksf3hnmue7pyzlm0sxwarh7lk8tdeprw2hjg6ysp7fxtw
Got a tip and it is here for those interested https://opago-pay.com/en/product/opago_lightning_pos-terminal_gen1
and this is the Michael to talk to ... nostr:note1zq84vut0arwyglq2tuz8rtw3nm7ju9eykut8kmrfzm42yzfh3d6s5j75s2
OK, that makes sense. For now I only thought about UTXO consolidation for fee reduction but the privacy component is just as important.
What’s the reasoning not to consolidate everything to a single UTXO?
Never heard of it, be careful! Don’t put any seeds into an (unknown) app.
