Unit of a Count (@countbitcoin) header
Unit of a Count (@countbitcoin) profile picture

I run on Bitcoin Standard Time https://nitter.gq/t.co/Vur8X0IcLg https://nitter.gq/t.co/cH5OKM6sN5

Joined January 2025
Photo by Unit of a Count (@countbitcoin)Photo by Unit of a Count (@countbitcoin)Photo by Unit of a Count (@countbitcoin)Photo by Unit of a Count (@countbitcoin)Photo by Unit of a Count (@countbitcoin)Photo by Unit of a Count (@countbitcoin)Photo by Unit of a Count (@countbitcoin)Photo by Unit of a Count (@countbitcoin)Photo by Unit of a Count (@countbitcoin)Photo by Unit of a Count (@countbitcoin)
Unit of a Count retweeted
Class of 17’ checking in on class of 21’ Bitcoiners
1
9
1
62
2,642
Unit of a Count retweeted
3 month Bart?
1
1
40
Unit of a Count retweeted
*FAA GROUND STOP DOES NOT APPEAR TO BE CYBER ATTACK: CNN
190
111
36
1,607
224,298
Unit of a Count retweeted
THE BLOCK: Brazilian crypto exchange Mercado Bitcoin confirmed a security incident and temporarily suspended deposits and withdrawals, saying customers were unaffected. Blockchain security firm Hypernative earlier flagged more than $40 million in suspicious transfers across multiple networks, according to local outlet BitNotícias.
16
20
7
88
22,080
Not a drill: shut down your BTCPay Server if you have a hot wallet. Appreciate the reposts 🙏
🚨 We are receiving reports of hot wallets on BTCPay Servers being swept by unauthorized attackers. If you're running an instance, please shut it down (./btcpay-down.sh) until we complete the investigation.
24
299
21
621
65,577
Unit of a Count retweeted
🚨 We are receiving reports of hot wallets on BTCPay Servers being swept by unauthorized attackers. If you're running an instance, please shut it down (./btcpay-down.sh) until we complete the investigation.
279
1,087
457
3,151
902,203
Unit of a Count retweeted
We're doing another @Bitkey giveaway! A built-in screen. No seed phrase. 2-of-3 multisig. Follow @Bitkey and us, RT to enter. ✅ Winner announced Tuesday 11/3 at 4PM EST.
43
251
6
204
15,639
Unit of a Count retweeted
I made a game where you surf the Bitcoin chart. Tap to pump. Don't get rugged. How far can you ride the Bitcoin chart? 🚀
4
3
8
617
Unit of a Count retweeted
This 5 word prompt gives the details of the vulnerability which was exploited today to steal 4000 BTC ($320M) from the liquid network (on a specific elements commit with Fable 5).
3
7
2
62
4,594
Unit of a Count retweeted
Liquid hack explained. Liquid has confidential transactions that hide the amounts for improved privacy. A bug in how these transactions are validated caused inflation of Liquid BTC (L-BTC) and allowed hackers to empty the entire side chain. Liquid nodes don't see the amounts of a confidential transaction, so to make sure that the transaction is still valid and doesn't cause inflation nodes check something called a balance proof and a range proof. The balance proof establish that sum of the input amounts equal the output amounts, i.e., that "x L-BTC going in and x L-BTC going out". But there's a catch. Only relying on a balance proof isn't enough. You also need the range proof. The range proof establishes that a hidden output amount falls within a positive range. That means a valid output must be at least 1 L-sat and at most 2^64 − 1 L-sats. Range proofs make sure that you can't mint "negative L-BTC". Why is this even necessary? Remember, the amounts are hidden and a hidden negative amount would allow extra positive outputs to balance against it. Without a range proof, a transaction could say "I've put 1 L-BTC in, and I'm taking two outputs out: one with 4000 L-BTC and one with -3999 L-BTC)." This is going to cause a disaster in a little bit. Once the balance proof, the range proof, and other validations pass, a transaction is regarded as valid and can pass consensus. However, because especially the range proof is computationally expensive, Liquid nodes cache the result of a successful range proof in memory. Essentially, the node remembers "I saw this range proof before and it was valid, all good!". In order to recognize the same range proof later on, you need to assign a label to it. This is called a cache key. This cache key is the actual cause of the bug. The way this cache key was constructed allowed two different transactions to collide on their cache key. Essentially, one valid transaction (1 L-BTC in, 1 L-BTC out) had the same cache key as an invalid transaction (1 L-BTC in, 4000 L-BTC out). Here's the hack: the attackers submitted the valid transaction (1 L-BTC in, 1 L-BTC out) first. Liquid nodes verified this transaction successfully, created a cache key called REKT and stored it in their cache. Then the attackers carefully crafted a second invalid transaction with (1 L-BTC in, 4000 L-BTC out) that created the same cache key REKT. Instead of validating the second transaction and realizing that it printed money out of thin air, Liquid nodes found it in their cache and said "hey I saw this transaction before, everything is fine" and that caused the inflation. The attackers then took their 4000 L-BTC and withdrew 4000 BTC onto the Bitcoin base chain. Note: I might have gotten some details wrong, and I'm aware that I simplified quite a bit. I wrote this post to help people understand what happened. Please feel free to correct me in the comments or add more details below.
81
252
60
1,462
152,446
Unit of a Count retweeted
1/ ~4,000 BTC left Blockstream's Liquid federation wallet today with a note: "we are whitehats. contact us on chain." Everyone is calling it a drained bridge. We read the chain. The Bitcoin side is clean. The problem is on Liquid and yet another bridge debacle. 🧵
1
7
3
35
12,529
Unit of a Count retweeted
We are aware of a security incident on @Liquid_BTC. Purported white-hat hackers have withdrawn ~4,000 BTC (~$320 million) from the Liquid Federation wallet. The @Blockstream team is working on contacting them on-chain with a signed message. What we know so far is that the funds were withdrawn via the SideSwap PAK (Peg-out Authorization Key), but that key was not compromised, nor were any others. Exchanges have been notified and have already paused (or will pause) LBTC deposits and withdrawals. Other Liquid assets such as USDT, DePix, and RWAs are unaffected by this security incident. Bridge nodes have been temporarily disabled, so no new transactions can be submitted to the network. Effectively, the Liquid sidechain is paused until this issue is resolved. Liquid wallets will be impacted, and we're sorry for any inconvenience. Federation members are actively working on resolving this so we can restore normal network activity. You can monitor the situation via @mempool's liquid.network site below: mempool.space/address/bc1qdl…
399
669
537
2,277
5,783,378
Unit of a Count retweeted
Someone redeemed and swept 21 Casascius coins in the last hour.
11
33
8
175
43,977
Unit of a Count retweeted
Bitcoin is on a Meme Tour, It visited 69K, 67K and now 58K It reached it's destination, and it will chill in the area for awhile But, eventually the Tour Bus will turn around start heading back home
1
59
Unit of a Count retweeted
Last week’s Coldcard incident is a reminder of something the industry underrates: randomness is the foundation of self-custody. If it's weak, everything built on top of it is too. Here’s what happened, and why Ledger devices are unaffected.
146
225
31
2,535
261,226
To build secure systems you must be humble. If you do not deeply internalize your own fallibility you will not go that extra mile to ask yourself "what can I do to make sure this thing is still secure even if I'm dumb and made mistakes?".
14
35
7
416
29,232
Unit of a Count retweeted
👇
Here's how to create a simple 12 word bitcoin seed using Seedsigner and dice. Its filmed in real time with a timer running so you can see the entire process & how long it takes Do you really think this is too hard, or too much trouble for you to secure your family's future?
1
4
317