pull down to refresh
ah, well perhaps that makes it somewhat better -- it's not as simple as plugging an easily identifiable string into sparkscan.
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.
So bottom line what we're saying is that spark negates lightning privacy benefits - but we already knew that it wasn't comparable, right?
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.
This is akin to Coinbase giving each customer a bitcoin address and forcing reuse.
Nice analogy, actually.
In addition to @benthecarman's tool, there's also this
It's not the pubkey that you lookup. You need to look at the route hints to extract the spark address.