pull down to refresh

I saw @theinstagibbs post this on X:

I wasn't familiar with what he was referring to, but later in the thread he says:

Aha! It's a Spark thing (again - #1020261). Having put some effort into trying to learn about Spark (#1020579), I'm surprised because this is first I've heard about its public-ness.

My feelings of surprise were strong enough that I decided to test it out.

  1. I downloaded Wallet of Satoshi and created a new account.
  2. Then I created a Bolt11 invoice for 21 sats and paid it from another wallet.
  3. I used decodePaymentRequest() to pull my new WoS node pubkey from the invoice.
  4. I went to Sparkscan and searched for the pubkey

This is where I got stuck. It did indeed find a wallet and displayed a balance, but the balance was listed as 0 (it reads 21 sats in my wallet).

So, either Sparkscan doesn't update very frequently or I did something wrong. I suspect the latter.

Anyhow, it seems to me that the verdict is out on whether this is possible (but given that instagibbs is much more skilled than I, odds are in his favor). I'm curious if anyone else wants to give it a try.

It's a Spark thing

It's a fake L2 thing.

Ark, Spark are both centralized exchanges... there's inherently a server, "coordinator", with full insight into everything.

Any ingress/egress via Lightning has 0 privacy because they're executing a swap for you (and taking an exorbitant fee).

They're surveillance tools and using scam narratives for distribution.

reply

We are going backwards. Huge fan of Lightning.
But how does this 'help' us?

reply

Lightning has massive onboarding barriers. Let's not kid ourselves.

reply

How does what help us? Fake L2's? They don't at all, they're self interested in generating swap fees. The virtue signals about helping users are just marketing.

reply

Not good. Non-custodial isn't that hard to use.
Hell I figured it out both on a phone and a node-in-a-box. That's imo what 'we' should focus on. Not this fake L2 stuff...

reply

Agreed, money is where my mouth is on this, hacking on Lightning.Pub as we speak.

reply

It's not the pubkey that you lookup. You need to look at the route hints to extract the spark address.

reply

ah, well perhaps that makes it somewhat better -- it's not as simple as plugging an easily identifiable string into sparkscan.

reply

Eh there's not much difference between calling something like decodeSparkPaymentRequest and decodePaymentRequest.

If someone in possession of one of your bolt11s wants to know your balance and transactions, they won't need new skills to do it - just the right tool.

reply

So bottom line what we're saying is that spark negates lightning privacy benefits - but we already knew that it wasn't comparable, right?

reply
171 sats \ 1 reply \ @k00b 8 Oct 2025

We knew it wasn't comparable to noncustodial lightning, but I assumed that Spark customers would retain the privacy of a custodial service. That is, I thought Spark would know about balances and transactions - not anyone curious enough to look. This is akin to Coinbase giving each customer a bitcoin address and forcing reuse.

reply
This is akin to Coinbase giving each customer a bitcoin address and forcing reuse.

Nice analogy, actually.

reply

In addition to @benthecarman's tool, there's also this

https://lightningdecoder.com/

reply

Always doing good work! I had mixed thoughts about spark but I thought it could be a tool for the masses but apparently not. Well not those who care about privacy

reply

Qué pena, debes revisar si la cantidad enviada era aceptable,no vaya a ser que si envías menos no se registra, dicho por experiencia

reply

deleted by author