Nostr Web Client

nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8 noob question. is there an equivalent for RFC 1918 for bitcoin addresses? ie to share UTXOs could we do NAT’s “hack” for IPv4 “to Bitcoin”?

If this has already been investigated, or this is what Lightning is, etc… I apologise for my poor understanding.

I’m conceptually thinking of a defined range of `bc1p…` addresses that represent private space, where a new, “local” address format can transact “off chain”

…maybe this idea is horseshit. IDK.

Reply to this note

Please Login to reply.

Discussion

DETERMINISTIC OPTIMISM 🌞 4mo ago

I'm not sure I understand why

nevermind 4mo ago

Was thinking for scalability; such addresses could spend without requiring confirmations/“off chain”. I may have gone down a useless mental rabbit hole…

DETERMINISTIC OPTIMISM 🌞 4mo ago

If it's not in a block it's not bitcoin 😉

Rizful.com (zap tester) 4mo ago

Testing zaps for this note… we made six attempts to⚡zap this note, at alex@nevermind.wtf, over a period of 33 minutes. In each case, we found that your lightning address server did not respond correctly. (The failure point was when we did a GET request to your specified callback URL: https://nevermind.wtf/.well-known/lnurlp/alex ). Your server did not produce an invoice, thus the zap failed. If you wanted to fix this... you could try a free rizful account -- https://rizful.com ... if u set it up, pls reply here so we can do this ⚡zap test again.