pull down to refresh

Exactly. By allowing Spark to lie about the properties of their platform, it makes it difficult for ACTUAL noncustodial wallets that use ACTUAL Lightning to compete against them. Users won't know to switch from Spark to Lightning because they were told by Spark that they are already using Lightning.

Same goes for CoinOS, no?

reply

... and then there are a million more reasons to avoid that one. But in the end we're talking play money amounts for most stackers, so I stopped caring. I just hope that for the stack that really matters, people use their grey mass a bit.

reply

Is CoinOS also a custodial wallet that is scamming their users by claiming to be noncustodial?

reply

Did you read their website? Where does it say "we are a custodial lightning wallet?"

The only mention I find is this:

You always have the option of taking custody of your funds by withdrawing instantly at any time.

It's not exactly a clear statement that sats on CoinOS are not yours. All the other language is about lightning an d bitcoin and "final settlement"

reply

What's unclear about that statement?

reply

When Coinos is offline, you cannot “always instantly withdraw.”

reply
reply

More importantly, one must hope the hacks don't drain more than the "wagmi fund" can afford to pay out.

reply

This statement is more clear:

Also, you are being a little duplicitous here: be honest with yourself and ask is a new user who goes to sign up at CoinOS's website going to think that sats they receive are their own sats and real Bitcoin? I think the answer is yes for most people.

reply
447 sats \ 1 reply \ @optimism 28 Aug

The SN-side disclaimer is not dishonest like the ones that we've seen the past year. This is good. I don't know if it is good enough - but on it's own that's the kind of transparency needed.

reply

Exactly.

reply
126 sats \ 8 replies \ @justin_shocknet 28 Aug -210 sats

If someone uses an SQL wallet, its because they don't care.

If someone uses Spark, it's because they were lied to.

There's no reason to use a fake L2 over an SQL wallet. Zero. That lack of functionality over SQL is why the fake L2's lie in the first place.