pull down to refresh
207 sats \ 7 replies \ @Scoresby 9 Oct \ on: Stacker Saloon
If you saw the discussion from yesterday about spark addresses being publicly searchable (#1251215) and you wondered whether this was true for Breez when it uses Spark...
Apparently, Breez SDK does not expose Spark addresses:
source
reply
oh cool! It's interesting to see a little bit about their decision. From what @moneyball said in his talk at bitcoin++ (05:25:04):
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
It sounds like the reasoning is that in a world where there are many Spark Operators, users are vulnerable to this privacy leak if the operators choose to reveal the data or if they have a leak. So rather than have people lulled into a false sense of security, Spark chose to make it clear that your address is trackable.
It seems like this would have been okay if there had been a lot more communication about this as one of the trade-offs of using Spark.
It is still the case that Breez has access to all users spark addresses.
reply
fwiw, there's a proposal for blind statechain transfers
reply
by default"reply
Well that good wonder what the WOS guys doing?
reply