Lots of talk on X about splitting the bill of a meal. Let me say this, if you’re dining with me, it doesn’t matter if you’re a woman, man, friend, family, or foe, I’ll always pay for the meal. All I ask is that you at least pretend to pay🤣 I’ll stop you anyway.
The Liquid hack negotiation is happening in OP_RETURN. So I turned it into a chat app.
Live, PGP-verified, with shared reactions, and a slot for the attacker's private key whenever he drops it.
https://t.co/jHxhz8WwCy
Still find it a bit surreal that you can pay for groceries with crypto at 137 SPAR locations in Switzerland. That runs on Open CryptoPay, which we built at @DFX_Swiss. Adoption isn't a conference demo — it's the checkout line.
@sethforprivacy My experience is limited to DeepSeek V4 Flash. However, I'm completely overwhelmed by it and have given up. Now I'm eagerly waiting to see what results you'll come up with. 😁
There is no rational reason to be relaxed.
It's only a matter of time before the first traditional bank announces that it is discontinuing all services because continuing operations is no longer feasible. 🌚
Update: Boltz will stay disabled until further notice.
Our API remains available to process refunds cooperatively. In any case, unilateral refunds will work, as they do not depend on our infrastructure.
Our support team stays reachable.
To be clear: this is not a response to a single incident. Over the past months we have seen a steady rise in automated, AI-assisted probing of our infrastructure, and we have dealt with several exploits. Each was contained, but the pattern is clear: attackers now iterate faster than a team our size can find and patch. In the past few days alone we saw a drastic acceleration, and we do not believe this asymmetry will reverse. After reviewing the results of our own recent security scans, we cannot responsibly re-enable Boltz swaps, especially as we are being actively targeted by what appear to be multiple resourceful groups while we race to deploy fixes.
What we are seeing is a major paradigm shift for Bitcoin services operating on an open source stack, and it needs careful analysis. Do not expect swap services to resume shortly.
To be explicit: no user funds were ever at risk. Boltz is non-custodial by design. And as a fully bootstrapped company, the losses were ours alone.
We don't know yet how things will continue from here, but we'll keep you posted as soon as we have had the time to catch our breath and make a decision 🙏
@Boltzhq Not that I expect an explanation—it's your decision to make. But why didn't the team decide to reduce liquidity to a small, reasonable amount?
@vikrantnyc After giving it some serious thought, I'd say the only truly sensible setup is a multi-signature arrangement using two different providers. Or a 2-of-3 setup using three different providers.
@vikrantnyc After giving it some serious thought, I'd say the only truly sensible setup is a multi-signature arrangement using two different providers. Or a 2-of-3 setup using three different providers.
If you're reaching the capacity limits of your Claude subscription, I recommend combining it with Grok.
Your Claude can delegate tedious, intensive tasks—like writing code—to Grok. Claude then reviews Grok's work. This way, you combine two completely different models and get the best of both worlds.
I have a report full of security issues of a software I'm working on.
Codex won't fix them because of Cyber guardrails
Fable won't fix them because of Cyber guardrails
Kimi K3 fixed them all. No restrictions, just gets the job done.
This will end badly for OpenAI & Anthropic.