Do you think it a solution to copy/emulate the post-snacks solution as done for Wasabi, for Coldcard firmware if there's going to be a post-coinkite moment? (not sure if this is possible wrt the signing of the firmware, fwiw.)

The worst drain exploit (1% coordinator fee) that Wasabi had was discovered internally and fixed (but not deployed quickly enough): https://github.com/WalletWasabi/WalletWasabi/pull/13191

I guess the bright side is that the damage was minimal, and the bug allowed an opportunity for coordinators to establish a history of trustworthiness (despite there being no inherent trust requirement in coordinators at the protocol level).

Kruw

> I'd particularly avoid things that sound like nitpicky self defense.

This is good.

> I'd be going out of my way to respond to people and attempt to be helpful.

If you're going down anyway? Only the most impactful things. Not to save you, but them. Which means do release the firmware. Do make sure people know about its existence once its there (and properly QA'd.) Do not waste time on individuals unless you have spare time, which I would doubt you'll have.

If there is any chance of being sued... legal will shut down some of that though, it's risky. Easy to make mistakes in comms that can be twisted and narrated against you in court. At least in my experience, legal will tell you to shut the fuck up, and if you need to vent, vent to them. At 10 grand an hour.

optimism

I've never had to do damage control/comms crisis management on a scale like this, so I suppose my talk is cheap. But if I was the person manning their comms, I'd be going out of my way to respond to people and attempt to be helpful. I'd particularly avoid things that sound like nitpicky self defense. This seems like it will just make people angry and distracts from the main goal right now.