Yes I know this site, but I'd like to understand how exactly this tree thing works, what the transactions look like, and how they solved mercury's problem of splitting and recommending the coin... is there any technical paper?

Could you point us to a technical reference / documentation / talk that explains how spark works? it's notoriously hard to find a full technical breakdown.

Looks like nostr:nprofile1qqsfe2xzm5nv5zwqp23zkys5wzlnq5wlkhad8gqnwkj8dmc07cw89ygpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqgnwaehxw309aex2mrp0yh8xtth9eshyaqr6ej9x is taking me more serious than most 😂 He’s building a bitcoin game slaying the fiat overlords. I need to get back to martial arts 😉

if you understand what this means and you can derive the formula yourself, I want to follow you.

Hi nostr:npub18hwpk5qep3ptnmzatq22ptwr9mth7ccrku56rdntwpxjxlkfyr2qrav8du any chance to have a POS on web?

cc nostr:npub168dqt5c8ue3uj8ynlk0lhwalnp7uy39lvzf9tm09wy3htxwmw7qq5nerj4

Other thing: I can't zap you.

Hi nostr:npub18hwpk5qep3ptnmzatq22ptwr9mth7ccrku56rdntwpxjxlkfyr2qrav8du I'm not a developer but I would like to know if is possible to generate a Spark address from a nsec, so every Nostr user would automatically have a Spark wallet? And if is possible to generate Spark Lightning invoices on nostr:npub1jugar2agq6369p0l86razavs9shj2p6pscxecevs8j94ap37hkqsjlfc28 SDK without having to have a server?

Thanks.

And what's the command that you constantly forget and have to google every week?

For some reason for me it's $ git remote -v

America’s story began with sound money.

Hard-working Americans saved their wealth in gold-backed money.

Today, Bitcoin carries that torch forward 🔥

There are four ways to create an invoice with a "decoy" node id:

- I used lnproxy.org to "wrap" my invoice so that instead of "my" node id appearing there, lnproxy's appeared there

- you can also toggle the "blinded paths" option in LND or Zeus Wallet. Among other things, that option replaces your node id with a dummy key

- you can also use TransLND or Valet Wallet, which have an optional feature where they will create a decoy pubkey for all of your invoices by pretending that your node is a routing node and the "real" recipient is a node it just made up

- you can also use Voltage or my Zaplocker software, which have an option to wrap all invoices so that all inbound payments to your wallet appear to go to Voltage's node or the Zaplocker server, even though they really get forwarded to the recipient

Also, it is worth pointing out that even without doing any of this, the public key in an LN invoice does not actually receive money, it is only used to sign communication messages.

As a result, it does not reveal which node it belongs to unless that node's network address and channels are gossipped via the LN gossip protocol, and that only happens if it is a routing node. A simple wallet with ungossipped channels does not reveal the network address of the node that controls it, so the pubkey in an LN invoice cannot be used by itself to find your node.

What a conclusion! I traced the XMR and identified its destination AND the total amount in that address on monero. nostr:npub14a6q6xvt4wuv0wpdpfr336e4fweldtu6np3ehpw55h83xuw2h2zsgyz6rn meanwhile, could not trace my BTC or identify its destination or the total amount in the channel where it ended up. Is XMR worse than LN after all?