Eh no ack dom you dummy
Joined March 2015
- Tweets124
- Following353
- Followers26
- Likes6.9K
🤖 Made with AI
DURBIN WARNS CRYPTO “BUBBLE” COULD BURST AFTER VOTING AGAINST ADVANCING CLARITY ACT
Asked why Democrats opposed the bill, @SenatorDurbin said crypto could collapse “to the detriment of a lot of people” relying on it to build wealth.
Durbin said taxpayers must never be forced to bail out the industry and Social Security funds must remain out of crypto.
“If this whole approach blows up, seniors are going to find their future benefits at risk.”
a liquid escape hatch has emerged 🚀
No Ack Dom retweeted
It looks like ~4,000 BTC just moved from the Liquid Network bridge all at once with an OP Return saying, "we are whitehats. contact us on chain".
TXID:
c103de95817b43f2df635ec6f35ff126ca26a7c6d20570c4b01866b2b3e69a19
No Ack Dom retweeted
There is a critical vulnerability being actively exploited on BTCPay Server, which can result in the loss of funds.
Please update your BTCPayServer to 2.4.2 by going to Admin Dashboard -> Server -> Maintenance -> Update & verify the 2.4.2 version string in the footer.
If you are unable to update right away, turn off your BTCPay Server to prevent unauthorized access until you can update.
No Ack Dom retweeted
BULL is immediately shifting our priorities to resume the ability of BULL wallet users send receive Bitcoin payments over Lightning, as well as move funds between Liquid and Bitcoin. We are evaluating multiple options and are beginning the work right now.
Ae have been in constant contact with our very good friends at Boltz for years. We have been, and are right now, collaborating closely with their team. They are my brothers in arms and I fully support their decision to suspend their service.
Let me be clear: Bull Bitcoin is a member of the Liquid federation and can convert LBTC to BTC without a 3rs party. No BULL wallet user will have funds "stuck" on Liquid, that I can guarantee.
Our immediate action plans are all targeting the same goal: BULL wallet users will carry on sending and receiving Lightning payments and perform swaps between Liquid and Bitcoin. The only question are implementation details. We will figure it out.
Until a solution is implemented, Lightning payments and Liquid <> Bitcoin swaps in the wallet will be fail without explanation.
I will not let this situation linger. I will fix it, no matter what it takes. I will be buying my grocies with Lightning over the BULL wallet as soon as possible.
I won't lie to you, the situation seems pretty bleak. First, the Coldcard exploit. Now, a critical piece of Lightning infrastructure goes offline. We are undoubtedly on the losing end of the Token War. Attackers have been scoring major victories.
We are going to fight back. We will never surrender. I apologize for not giving more details. I have work to do.
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 🙏
No Ack Dom retweeted
IMPORTANT UPDATE: Using Slipstream to safely migrate funds off multisig wallets containing Coldcard(s)
Two levels of urgency, so you know where you stand:
• Migrate now: if your affected Coldcard-generated keys alone could meet your wallet’s signing threshold (e.g. a 2-of-3 with two Coldcard-generated keys). These are the wallets an attacker could realistically sweep.
• Migrate soon, no emergency: if you have only one Coldcard-generated key, below threshold. A single affected key can’t move funds on its own, but you should still migrate. If in doubt about how many of your keys were generated on a Coldcard, treat it as the higher-urgency case.
For our paid subscribers (automatic, coming soon):
The next Nunchuk mobile update will automatically route any transaction from an assisted multisig wallet containing at least one Coldcard through Slipstream, bypassing the public mempool. You won’t have to do anything but upgrade. We’ll announce when it’s live (currently awaiting Apple/Google review).
For everyone else, the manual method:
Use this if you’re:
(a) a subscriber who doesn’t want to wait,
(b) a free Nunchuk user with Coldcard in your multisig, or
(c) not a Nunchuk user but have Coldcard in your multisig.
Prerequisite: you’ll need a Slipstream code. If you don’t have one, DM us and we’ll try to get you one before you start.
(Paid users on the upcoming auto-Slipstream version can skip this manual method entirely and just broadcast in-app.)
If you’re a non-Nunchuk user, first import your multisig into Nunchuk: Add wallet → Recover existing wallet → Recover using BSMS file, wallet descriptor, or QR code.
Manual Slipstream submission method:
1.Paid users: ensure the Platform Key’s auto-broadcast is OFF (it is by default) so the transaction isn’t broadcast before you can submit it to Slipstream.
2.Create the migration transaction. Set the fee rate to at least Slipstream’s minimum (check the current minimum at slipstream.mara.com). Higher fee means faster confirmation.
3.Sign with your keys so the transaction meets the multisig spending threshold. Do NOT broadcast it in Nunchuk.
4.Get the raw hex: Transaction details → More menu → Copy raw transaction hex.
5.Go to slipstream.mara.com, submit the raw hex, and enter your Slipstream code. Note that the transaction might take longer than usual since Mara only has ~5-6% of total hash rate.
Why this helps, and its limits: we haven’t heard of any reported attack on a multisig containing Coldcard so far, but better safe than sorry. Note that the Slipstream method relies on trusting the MARA pool operators. In exchange, it keeps your migration out of the public mempool, closing the RBF-sniping window explained in the quoted tweet. It doesn’t eliminate risk, but for wallets genuinely at risk it meaningfully reduces it. For everyone else, a normal migration is fine.
Please share and retweet so this reaches as many affected people as possible.
Update: for impacted users whose Coldcard keys alone could move funds, broadcasting a migration transaction to the public mempool briefly exposes it to RBF-sniping while the vulnerable keys are in flight. We’re looking at adding an option to submit the sweep directly to a miner (e.g. Slipstream), bypassing the public mempool during that window.
Note that this means trusting the mining pool operator. Moving coins off spent addresses remains the priority. If you have any, move those to a fresh address first. Stay tuned.
No Ack Dom retweeted
Confirmed #COLDCARD bricked 💀
A rushed firmware hotfix introduced a critical failure: a transient STM32 TRNG error could permanently fault the RNG. Since it’s used before the PIN screen, affected devices to become effectively bricked.
github.com/Coldcard/firmware…
funds from one of these addresses has moved to @coinbase about 45 min ago. how do we get someone from coinbase to look into this?
stolen funds landed here: mempool.space/address/1N8knQ…
transfer to coinbase here: mempool.space/tx/23a84f33fe4…
all victim and attacker addresses suspected of being part of this 'wave 4' already confirmed in blocks are listed in this pastern pastebin.com/6AG9s0pP
No Ack Dom retweeted
IMPORTANT UPDATE: We just had our first confirmed loss of a Mk3 + 2 Word Passphrase.
Drained at 2pm Aug 2nd Australia Time - Roughly 17hrs ago.
@xueqinjiang here's a "bitcoin server" if you want to buy one. Link in the comments. 😀
No Ack Dom retweeted
For additional context I suggested to @JohnCarreyrou to speak with Blockstream cofounder Greg Maxwell who is legendary in his ability to debunk faketoshi’s, knew the code base intimately and Adam personally.
I believe phrased it as “if your thesis and evidence can survive 10m of talking with Greg I’d be shocked” and offered to connect him to Greg.
I just now confirmed with Greg that he had no requests for contact or comment from anyone at the NY Times.
Purposefully avoiding talking to people who can debunk your story narrative isn’t reporting.
How many former colleagues, cofounders of @Blockstream, investors in @Blockstream did you talk to in those 18 months ?
How many of them gave you long lists of reasons @adam3us isn’t Satoshi?
How many of his cofounders who worked with him day in and day out told you that after all their time with him they are more convinced then ever, that @adam3us is not Satoshi and that the game of Satoshi hunting is stupid and dangerous and carries real world consequences for the safety and security of people who fall under that gaze?
How many coders of Bitcoin who cofounded Blockstream with Adam did you talk with about Adam’s horrible Windows C++ coding experience and suggested coding stylometry was a better method of analysis and to compare coding styles and it would likely disprove your thesis?
How many people told you that they’ve known Adam for almost 30yrs, employed him, cofounded companies with him (including @blockstream) and have actually spent decades working with him think he satoshi?
Was it all a grand conspiracy while we struggled to raise capital, manage burn rates, find supporters and build a real business that Adam was secretly sitting on Satoshi ‘s stash of bitcoin play acting the entrepreneur in need of capital?
There’s a lot of stuff you left out of the article John that didn’t fit the story you wanted to tell and I have a recorded conversations with you to prove that.
Disappointing, but not unexpected which is why Adam clearly knew you were Satoshi hunting every time you met him (including Vegas) - because I told him you were chasing this story.
No Ack Dom retweeted
Hi. Professional C/C++ programmer here. The open-source code I can find written by Adam Back and Satoshi Nakamoto don't look remotely similar.
Back's code looks typical of academic Unix programmers who also hack their code to run on Windows.
Satoshi code was written by a professional Windows programmer who also wrote for Unix.
Stylistically, they look nothing alike. There's not enough time between 2005 when I can find the newest Adam Back and January 2009 when Satoshi published Bitcoin/0.1 to account for the change. Both are perfectly competent programmers, but stylistically, they are completely different.
The NYTimes tried to compare their English language in posts/emails. I'm compare their C/C++ language in their open-source code. The NYTimes merely points out they both use C++ as if that's another corroborating detail, when the actual code seems to disqualify Adam Back.
Bitcoin’s founder, Satoshi Nakamoto, has remained hidden for 17 years. A trail of clues — and a year of digging by our reporter, John Carreyrou — led us to a 55-year-old computer scientist in El Salvador named Adam Back. nyti.ms/4bXWC3V
@AnthropicAI can you add the ability to top up API credits using bitcoin? @KagiHQ does this and it makes life much easier for people living on a bitcoin standard. Kagi uses @OpenNode for bitcoin payment processing.
