pull down to refresh

They released early today (they are based in Australia):
They are using Spark to provide customers with a lightning wallet. Spark is trustodial (h/t @justin_shocknet) but they've also made the weird choice of making all customer balances and transactions visible via a public explorer as pointed out by @theinstagibbs.
This might not be a big deal if it were hard to determine a receiver's Spark address, but any bolt11 paid to a Spark customer reveals the Spark address. @benthecarman has cooked up a utility to doxx the Spark address from any bolt11 invoice paying a Spark customer.
What this means: if you use WoS (or any other wallet using Spark), anyone you give a bolt11 to (which you do when you want to receive money) will be able to view all of your transactions and your account balance.
Correction: some wallets using Spark (like Breez) do not expose the Spark address in the bolt11. However, given the public explorer and Spark address reuse, timing analysis can be used to deduce a wallet's Spark address and therefore its balance and history.
reply
Is it public too if you've only ever used it for LN transactions and no on-chain?
reply
20 sats \ 1 reply \ @ek 6h
This is about the new version of WoS that uses Spark. Did you use this new version?
The issue is that their lightning invoices include routing hints that can be used to reveal your spark balance
reply
I only update my apps manually and don't do it often. My version is 3.1.5.
reply
26 sats \ 0 replies \ @BeeRye 16h
thats pretty dumb, hope they fix it
reply
are older versions of WOS affected by this in any way, or is it just this new release ?
(i have some stray sats on an older WOS, dunno if i should move them and ditch it )
reply
just take them out, pref to some other LN wallet. Isolate the utxo if you're forced to use boltz to swap to on-chain and then either mix it or if it's enough (500k+), use it to open a new lightning channel and go from there.
reply
100 sats \ 1 reply \ @nichro 22h
Even funds on WoS in the old custodial mode will be moved to spark? I had the impression that'd be only if you activate self custody mode
reply
The question is: why would that stay around? I'd pre-empt in anticipation of the full migration out. I assume that this will take < year, but I may be wrong.
@remindme in 1 year
reply
i should add, i didn't ever sign in or anything to it, it's way less than even 100k sats, and i've only ever used it over LN, never on chain
reply
If you have another LN wallet, just send it there. Worst case send it to SN and spend it on zaps.
reply
The old custodial mode is not affected.
reply
This is awful, yikes
I tested out blitz wallet which uses spark and I was not impressed
I could never deposit or buy credits on SN using blitz
Edit: I should clarify. I tried to send money from blitz to SN via lightning. After 3 failed attempts I gave up
reply
they've also made the weird choice of making all customer balances and transactions visible via a public explorer
Since it's a fake L2, and not really Lightning, there's inherently a centralized server with telemetry. Can't make any privacy assumptions with this that you wouldn't make with an traditional custodian...
... but this seems even worse since the LARP effect of acting as a Bitcoin layer implies some publicly traversable records in a tree/shadow-chain.
I imagine they only made the explorer to front-run someone else making one.
reply
228 sats \ 1 reply \ @DarthCoin 8 Oct
Maybe now people will pay more attention to my warnings. I was always warn you about spark, to stay away.
reply
🧡
reply
Well that’s a deal breaker for me.
reply
Before I was affiliated with THNDR games and now they have switched to another wallet that is not available in my country. 😭 I miss Wallet of Satoshi when it could be used in THNDR
reply
Might stick with Coinos.
reply
if you use WoS (or any other wallet using Spark)
Meaning that this is not necessarily a WoS design choice, so much as a Spark design choice?
So this would also apply to wallets using Spark via Breez? If so, I'm even more surprised that I hadn't heard about this before.
reply
reply
reply
I don't understand the technology behind it. Is this a choice or is it an unavoidable feature of the protocol, much like how bitcoin block transactions are public?
reply
I was watching @moneyball's talk at bitcoin++ (05:25:04) and he talks about this a little (apparently it only recently became public knowledge).
When I inquired, it's not a technology limitation but actually an intentional policy decision by their NC...uh...I can't steelman the argument. They feel like it's disingenuous to users to not publish it because of the risk of a Spark Operator potentially publishing it
Also, I did a quick scan of @BTCsessions recent WoS tutorial and he doesn't mention this privacy trade-off.
Seems like Spark maybe might have wanted to make this design decision a little more clear to users.
reply
an unavoidable feature of the protocol,
It's not a protocol, it's a centralized exchange.
The server inherently needs telemetry to operate, this would be exposed by someone else had they not front-run it.
reply
133 sats \ 1 reply \ @ek 10h
Does the protocol require to reuse addresses like Breez SDK and Blitz wallet do?
This also seems to be the case for the SDK from Spark itself since I found this in their official developer guide:
Important Notes
  • The same wallet will always generate the same Spark Address
But not sure if that's a technical limitation of the protocol, or just a limitation of all existing SDKs and wallets.
Maybe this is a question for @benthecarman?
reply
You kinda have to treat them as separate now but they claimed they'll fix it by EOY
reply
107 sats \ 1 reply \ @k00b OP 8 Oct
It's either a choice or an oversight afaict. They are encoding the spark address into the invoice when they could, if they wanted, obscure it.
reply
Spooks be spookin.
reply
242 sats \ 1 reply \ @anon 8 Oct
deleted by author
reply
Buahaha exactly this
reply