Last Notes
RTL support is borked (text in my profile)
Image attachments don't seem to work.
Text fields don't let me move back/forward with the spacebar hold like all native text fields.
And I'd like it if I didn't have to paste my nsec.
it is frustrating
the core audience that would benefit from communications is here, and yet I have to log into X every day or check my Telegram to notice stuff like this
Update your BTCPay Server instances again, as soon as you can: https://x.com/r0ckstardev/status/2087963055091011920
(no nostr post)
though the canary expiry snafu and sudden departure makes me somewhat uneasy.
Thank you for your service and hope y'all are well. Sad to see you go. On the bright side I don't think you'd say Boltz is in safe hands if it wasn't.
Anyone seen the @nprofile…3478 statement on X? It isn't here on nostr for whatever reason.
Smells a little but fishy, but who knows.
Define the trust boundary. You do not need to trust bitkey to emergency exit the multisig or to transact.
I want to scam some knotzis, if they believe it's the actual chain, surely they won't mind my LukeCoin? 😂
Anyone know stores selling stuff for Bitcoin with a BIP110 node backing their payment backend?
I have some BIP110 LukeCoin to spend 🤑
(yes, aware of replay implications)
I don't think they understand how this works 😆
https://blossom.primal.net/ab5e8078756024cdc8b8a038c6d9b4b33064274e29734d3055fcaef59279f564.png
aaand the knotzis disappeared
Worse. It took them ~10 hours to put anything on their website/blog after the Tweet.. 😅
Very odd response/handling from a project I generally like.
calle is pissing me off tbh
I mean my recommendation when this happened yesterday was nuke it and probably don't use it again
Given how they handled disclosure by just tweeting and not posting anything about it on their website or blog for more than 10 hours 😂
you only needed to rotate macaroons (from the latest statement).
How would it almost get you? These are usually pretty dumb and simply ask you to literally type out your seed phrase.
p a i n
https://blossom.primal.net/06554cdcf7cfee907374d13f91ee3a58fb218f5d57ce076d96138c1d9f54b606.png
https://slothy.win/#pomegranate
Of course, but doing that 5 years ago, with an immediate advisory and that easy path to migrate would limit the damage substantially.
Instead we had.. what we had lol.
They could have easily rolled an update that forces a seed refresh. On boot -> if seed exists -> prompt user to confirm they have existing seed words / verify that -> generate new seed -> ask user to migrate all funds to new seed (now on device), load old seed in memory transiently to allow signing the migration tx.
This is more jank tha it should because they don't have a first-party app. Something like Bitkey handled something similar in literally two clicks during the privacy upgrade update (which required a new 2-o-3 to be generated.
Zero announcement / advisory notice / blog post or any indication of the vulnerability on BTCPay Server's website other than the post on X.
It has been 4 hours.
If this is how they operate, I advise you all to just pull the plug and shut your BTCPay instances down.
Requires an approved/published Google OAuth screen. I can spin it up with the testing 100 user cap and see from there.
Also maybe I'm retarded but shouldn't the update invalidate all LN backend auth and regenerate it automatically instead of leaving people with potentially exposed macaroons etc?
Sure it might break stuff but a simple post update popup with info would help less technical folk.
Would be nice to understand the scope of the BTCPay vuln and if there are any logs to check to confirm if it was exploited or not prior to an upgrade.
It isn't new, it's been there for a while. Only he brought it back up with limited funds after taking it down following Boltz.
Other than that, agree. He's been great covering any snafus and is running a very useful tool, but yes, custodial.
No. Not a big enough incentive. Evidently and predictably.
The only way to get 'free' review of your code is to have others use it and have the incentive to actually review it since their product would depend on it (and hence, the liability behind that).
Or to have paid external security audits.
You can't prohibit commercial use of your code and expect others to dedicate their time to look over it if they have nothing to gain (and again, most _users_ who have funds backed by your code aren't technically competent to audit a codebase).
There is much less incentive to audit code if you're not allowed to build upon it.
Because... developers are often more likely to have the skills to do so than users. And by taking away the ability to _use_ the code they'd audit, what is the incentive again?
It's not that hard a concept to grasp.
Friendly reminder that even in 2013, RNG bugs had a response with much better user UX, often indicating that a new seed is required, and guiding users to migrate funds.
https://bitcoin.org/en/alert/2013-08-11-android
Yes, with a hardware wallet this is slightly more complicated, but if something like Bitkey can handle seamless seed refreshes and fund migration (ex: the enhanced privacy upgrade) then others can.
Every hardware signer should have some form of official companion app that can make these flows possible for the average non-technical user.
* without updated firmware
Any European resellers still have Coldcard Q stock? Looks like it was pulled from those I can find.
Need to purchase one for some experiments.
Uhh 🗿
So, Canadian friends, do y'all do private investigators there? He shouldn't be able to take a shit without someone knowing from now.
Spun-up an Ark delegate: https://slothy.win/#delegate
I wrapped my head around (more or less) Ark, but for Spark I'm still left with this operator question that the whole trust model hangs upon.
With so many Spark wallets popping up, can someone ELI5 to me why we're OK with a trust model that requires that all spark operators don't collude given that from what I can see there are only 3(?) Spark operators and no clear understanding of how you'd become a Spark operator?
I'm sure I'm missing something, but if not, seems crap.
LN receive / send on Aqua will be broken.
But main chain Bitcoin and Liquid will work (including BTC to Liquid swaps).
Sadly despite boltz being completely opensource there aren't many operators: https://swapmarket.github.io/swap
Ideally the wallet providers would host their own instances and actually encourage fee competition by selecting the cheapest offer out of multiple options. But none of that has happened, so every swap based wallet just hard-codes official boltz.
Also, not having an optional first-party companion app is a major downside. This could've been handled much faster and with less friction if there was an app flow that a) alerted to a signer having a vulnerable firmware. b) initiated a migration tx to a new seed as soon as the device firmware is updated (possibly a hop to a software key in the interim if the signer can only have one active private key).
If Bitkey can do it (ex: the enhanced privacy upgrade requiring a new key - seamless flow) every company should have a similar flow ready for this type of situation.
It should only take a couple of clicks.
much of the advice on X of "generating your own entropy" is absolute dogshit that is going to get clueless people in trouble.
Solid hardware RNG sources are a solved issue in this context. Just make sure your code is actually.. using it.
& the shit advice going around of footguns around generating your own entropy (exclusively, not as an additional source) is going to hurt more people than it helps.
If you know an affected normie, just get them a fucking Bitkey, Bitbox, Passport, Jade, or whatever the fuck™️ instead of confusing them with dice circlejerks. Pretty much every signer is using multiple good RNG sources. This wasn't a flawed RNG source issue, it's a dumb software bug causing a fallback to software PRNG. What are we even talking about?
I saw someone on X suggesting that people should pick BIP39 words from a jar. If you're a cryptographer you'd hang yourself with some of the garbage advice.
Rant over.
A somewhat gross but nonetheless true statement:
In the grand scheme of things ~90M USD in drained ColdCard wallets is a drop in the ocean. I'd wager that ColdCard's marketshare isn't even that significant in the grand scheme of things.
What particularly sucks is that these are pretty much all from plebs who worked their assess off to stack that corn. And ironically from those who probably tried to go the extra mile to get something more "sophisticated". It's "only" 90M but the impact this loss has on those affected is immense.
Nah, he's just a narcissist who happens to be incompetent. It's a terrible combo.
I feel like the "dice roll only" advice is going to bite some noobs or people who mishandle it. There is nothing wrong with hardware RNG or the RNG sources used by any hardware signer. What happened to ColdCard is a fail-open fallback to software PRNG.
At least ask that people use methods that use dice rolls as a supplementary entropy source, not the sole one - if at all.
Good chance whoever it is doing this is retarded so perhaps so corn can be returned 🤞
Nostr peeps:
I've been away for a while and wasn't keeping up. What's a good Android client (other than Amethyst). Web/Linux suggestions also welcome.
You also can't pay with Bitcoin to buy your Bitkey, in Italy at least.
Got my gen 1 Bitkey years ago for 25 USD. Wouldn't pay 200+ for this 😅
The quality of 5.6 Sol and Opus 5 / Fable 5 compared to what we have before, especially when it comes to vulnerability analysis is night and day.
Even distilled models like K3 are leagues ahead of what we had for the past 2 years.
If you haven't yet, use a modern Clanker on the highest effort setting to comprehensively audit your code. And give it a harness that let's it experiment and actually test it's theories.
I see people saying this Coinkite/ColdCard incident will reduce confidence in self custody.
It shouldn't. This was an amateur flaw in a company run by a narcissist who should've never been trusted to begin with. If you ignore the red flags around their hostility towards FOSS, seedsigner (including squatting seedsigner.org btw), then I don't know what to tell you.
Maybe if nvk spent less time shitposting and more time auditing his garbage, we wouldn't be here.
If you're going to use a hardware signer, use proper hardware signers from serious companies who have their work audited... especially you know, the bits around fucking entropy and seed generation, fundamental parts of a fucking hardware signer.
And it should go without saying that "influencers" who shill this garbage should reconsider.
Sympathies to everyone affected.
