(16min 30sec) "Spark has a unilateral exit"
(19min 00sec) "Spark operator [...] may freeze funds until KYC is provided"

These to statements are contrary to each other.

There is NOT A UNILATERAL EXIT IF YOUR BITCOIN CAN BE FROZEN INDEFINITELY. Spark's continuous representations and marketing pushes to the contrary are a blatant and obvious lie.

This feels like a very dissatisfactory ending to this chapter:

source

"assured us" = trust me bro. it seems to me that the reality is that most convenience services bitcoiners use come with a risk of privacy leakage (unless you can prove that they can't leak anything) -- and you're safer if you act like they are giving it all to chainanalysis.

It's crazy that Bitcoiners still lack a bullshit detector. Lightspark is not here to help, they are here to extract.

Here is a response by the CTO and co-founder Lightspark, Kevin Hurley:

There's been a round of misinformation about Spark going around, so for the sake of setting the record straight, I'll briefly clear up a few things.

For one, unilateral exit has been around since the early days of Spark. Many developers and users have used it. This has been demonstrated many times both here on X and during the process of integration by developers. Unilateral exit also does not require the SOs to be online when a user wishes to exit. When a transaction is received, users can save the unilateral exit information and later use those pre-signed, valid L1 Bitcoin transactions at any time on Bitcoin. There are existing Github issues to expose unilateral exits in a more intuitive way in the SDKs, but unilateral exits themselves have been functional for a very long time. Unilateral exits do require CPFP - this is used to ensure that the expected value for an attacker is negative. The typical user would perform a cooperative exit, which does not require any on-chain funds and is an atomic swap of on-chain funds in exchange for Spark funds. Unilateral exits are generally reserved for a worst-case scenario and can be sponsored by an L1 fund provider if needed.

Second, the confusion around "Sparkcore". At Lightspark, we use a monorepo for our server code. This one service is called Sparkcore - the naming of which preceded the creation of Spark. Lightspark runs an SSP within this service. Our Lightning infrastructure uses both LDK and LND - both of which we contribute code towards. Sparkcore itself is not open sourced - that would mean open sourcing our entire server-side stack for every product we have built. The Spark network code, however, has always been open source - and that's the openness that matters, because it's the code that actually enforces the rules of Spark. The SSP is an optional, replaceable convenience role.

A recent post claimed that APIs used for other products are part of the SSP. We have many products, and we have never been shy about describing UMA, which allows regulated entities to exchange information to process transactions over Lightning. This is not a Spark product. The SSP does not hold your seed phrase (that should never leave your device), the SSP cannot freeze your funds, and the SSP isn't even a required role to use Spark - it is the interop layer between Lightning and Spark and helps do swaps for exact denominations of leaves. Running an SSP is something we have talked with many partners about. The client chooses which SSP they wish to interact with (if any) - we cannot control if a client talks to a new SSP.

Finally, privacy. I've discussed this many times in the past, so won't belabor the point again. Spark allows for transactions to be hidden from external visibility. As I've spoken about at length both here and at various conferences, we care deeply about making sure that there is true privacy, and we aren't satisfied with anything short of that. It's an ongoing effort to continue to further the research in this area.

I'll leave it with this. In the network our critics operate, the default payment path is one where the operator colluding with any prior owner can double-spend the current holder - their own docs say so. Receiving over Lightning means trusting that the operator deleted a key - their own docs say so. If you don't come online every 28 days, the operator can take your funds. In their founder's own words: "In theory it could steal it." The automatic re-issuance of expired funds promised in March 2025 still hasn't shipped. Their operator's liquidity costs scale with payment volume, which by their own admission "will translate into user fees." And there is exactly one operator - their own docs tell everyone else: "Do not attempt to run an Ark server in production (yet!)." Spark has three independent operators, exits that don't expire, and no flow where a single operator can take user funds. Users can judge for themselves.

Our users and the developers building on top of Spark care about bringing Bitcoin to more people. They value the ease of use and simplicity of Spark. They care that we have 3 independent SOs. They care that we are pushing for more and better functionality. And they value that we spend all of our time thinking about how to make Spark better each and every day. Ok, now back to building because that's what we do at Spark.

This feels to me like the community reaction to spark when wallet of satoshi launched with it #1020261 and to the frustration when some wallets using spark put a user's spark address in the route hints of a lightning invoice #1251232.

Spark's advertising could use a lot more clarity.

Spark can see all your transactions, and like any entity that can see all your transactions (isn't this true for many LSPs?) they can log what they see and compare them to other data to which they have access.

It may be fair to say that spark spies on you, but so does every other service you use. The only ones who don't spy on you are the ones who can't spy on you.

About time flags were raised. Marcus is duplicitous.

Funny cuz I asked this question on nostr just yesterday.

Seems like there's debate around whether the Sparkcore Chainalysis REALLY enters the equation on Spark but I think it's at least a coin flip whether that's true.

Imo it seems like Spark whether intentional or not risks being kind of like a stablecoin: still pretty centralized and vulnerable to censorship pressure and surveillance.

why has no one mentioned this is their UMA product which touches fiat.

not defending spark, cause fuck them, but facts are facts.

Darth was right again ?

Fake L2's are surveillance tools by design #754780

Pushed by communist NGO's
#1455980

Convenience is the trap
#1251383

The trap springs when enough users are on Fake L2's and support covenants, BIP110 psyop is part of this
#1509777

With covenants, fungibility is dead, regulated exchanges will only let you withdraw into covenants "for your protection" so they can claw back funds when they don't like where you sent them

If you think Lightspark raised over 100M to build a custodial wallet and call it not custodial you're on drugs.

Ark/Bark are the same exact thing so give them no quarter when they sling shit at Spark, they're just as guilty.

Like who is shocked by this?!? Honestly?

It’s spyware. Use real Lightning.

So cake wallet...what now ?

https://twiiit.com/matthewvuk2/status/2076344901478892028