X.KOJIRA.IO
Timeline

calle

[email protected]
npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg
DM @callebtc:matrix.org
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.
you can probably see some of these sad little fucks in this thread, they're like STDs, reappear when you thought you finally got rid of them.

these are actual people, the bottom scum of humanity, sadly.
send butt, I'll sign
personally I don't care about how the block works as long as it works reliably.
who the fuck are you, and how is life with a micro penis
yes it barely works though :/
gm mostly
nostr is full of reply-guy psychopaths that you can't block and there isn't a single client where muting works reliably, let alone across apps

nevent1qvzqqqqqqyp…
anyone still here?
are you running the latest version? this should've been fixed
you’ve certainly been mislead by people who have no idea what they’re talking about
CLN action priority list:

- restart with —offline
- if you can’t, turn off
- if you can’t, pray
If you can, restart with `--offline`.

If you can't, I would turn it off instead of doing nothing.

nevent1qqsyknl5hdt…
this too shall pass 🟥
🟥 URGENT: Critical vulnerability in Core Lightning

Blockstream developers urge users to shut down CLN Lightning nodes right NOW!

Please let everyone know!
https://blossom.primal.net/6bed280f966703baf8642602c70bfe…
why humans should not code in c: we're finding memory-safety vulnerabilities in c projects that are prevented by default in many other languages.

in the past, finding a simple buffer overflow wasn't enough. you'd need a highly skilled hacker to turn the vulnerability into a working end-to-end exploit.

today, that's a single prompt.

nevent1qvzqqqqqqyp…
nobody gives even the tiniest fuck about what retarded bip110 shitcoiners have to say
blocked for excessive retardation and bip110 brain damage
at least I'm not a loser who fell for the most retarded scam in bitcoin's history
dickbutt.jpg
|
|
3 yrs later
|
|
V
luke dashjr
becomes a
shitcoiner
🚩 Bitcoin Red Team Update

We're continuing a large-scale security review of the Bitcoin open-source ecosystem.

25 Bitcoin developers around the world have been working on this task non-stop for 108 hours.

https://blossom.primal.net/0a31b776061ffea8d5d1f544232bd4…

We scanned 501 projects and produced 7,958 findings, of which 1,280 are rated high or critical (H+C) severity.

Our goal is to provide the most useful information. Based on feedback from maintainers, we've recalibrated our severity ratings and are now stricter about what we classify as H+C.

https://blossom.primal.net/a1c91429c176f784c66117ae1b19a4…

The share of all findings rated H+C increased to 16.2%, and the share of findings with a reproducible proof of concept increased to 24.7%.

That means our accuracy is improving.

As we harvest the low-hanging fruit, we're now focusing on improving harnesses, deploying better cyber-capable models, and probing more sophisticated attacks.

https://blossom.primal.net/ce6dde791e2f5468d7942c41009272…

Our AI spend remains consistently high.

Our cumulative spend has passed $58K as we add more inference sources. Notably, we've started using cyber models from OpenAI and Anthropic.

These models are producing incredible results, but the vast majority of our spend (74%) still goes to Kimi K3.

Kimi K3 remains the top choice among our hunters, but we've also seen a significant increase in the use of Qwen 3.8 over the past few days.

https://blossom.primal.net/4da137b276eba405c01bd5d58101e0…

Our goal is to strengthen the Bitcoin ecosystem and increase the resilience of our infrastructure in the age of AI.

To achieve this, we're conducting the largest red-teaming campaign in Bitcoin's history.

As a Bitcoiner, I am immensely proud of this.

We're sharing all our findings with developers for free.

This would not have been possible without the generous support of organizations like nprofile1qythwumn8… and donors like @FPuklowski and nprofile1qythwumn8….

You can help keep the Red Team alive by donating to the OpenSats Red Team Fund here: https://opensats.org/funds/red

Last but not least, our reporting rate is picking up. Thanks to our outreach team, we've reported 29.4% of our findings so far.

We're also rolling out new infrastructure to deliver these findings to projects more quickly and securely, while improving how we incorporate feedback.

Stay tuned!


https://blossom.primal.net/c52088aa3fb6c6692c54c791be525a…
Gocoin 🤝 Red Team

Thank you for pushing a fix so quickly. Brilliant red teaming by nprofile1qyx8wumn8… 🚩

https://gocoin.pl/gocoin_news.html

https://blossom.primal.net/adce14082103596aa5b33c16cc627b…
Turn off your BTCPay Server immediately if you can’t update right now.
nevent1qqs9u2n8mrl…
🚨🚨 URGENT: BTCPAYSERVER 🚨🚨

There is a critical vulnerability that is being actively exploited on BTCPay Server which can lead to loss of funds.

Update your BTCPayServer to to 2.4.2 or turn off your BTCPayServer now.
🚩 Bitcoin Red Team update 55 hours into the campaign

We're now 24 people working around the clock.

We've scanned 425 projects so far and have produced 1029 high+critical (H+C) findings.

https://blossom.primal.net/9c1af29b7a362e981cdac51f881865…

We generated 6700 findings so far and are hitting 7.7 projects per hour.

Our H+C rate per person per hour is back at ~1 as we work off a massive backlog and as the team grows and naturally divides up roles.

We have hunters, wizards, outreachers, sugar daddies, and gigglers.
https://blossom.primal.net/4dc7b8b0c997a50ba2c60f8d69add0…
https://blossom.primal.net/ed41ccd68901b5a794084466bc552e…

Our H+C ratio is at 15.4% of all findings, increased by a percentage point compared to yesterday.

This is great, our accuracy is stable, and even slightly increasing. We're trying out best to reproduce all critical findings in local regtests before reporting them to projects.

https://blossom.primal.net/fd24c2f5f8057510eeca48735c2082…

Our biggest bottleneck is outreach. Most projects don't have a SECURITY .md in their repos (19.5%). Only 13.1% have an email in there.

We're working on better ways to reach folks. In the mean time, the best thing you can do as a project maintainer is to leave an email address in your repo.

https://blossom.primal.net/0c7e7ca2e032b79a7f84a4cbb775fb…

Thank you to the sponsors and donors who cover the costs of this campaign and help to keep it alive.

Specifically nprofile1qythwumn8…, FPuklowski, nprofile1qythwumn8…, and everyone who has donated to OpenSats Red.

https://opensats.org/funds/red

An incredible team of some of the most hard core Bitcoiners I know have assembled and dedicated their last days to this effort.

We've seen shit.

I don't want to reveal anyone personally, they can choose to do that themselves, but I think the way that people came together to join forces was and still is the most beautiful part about this entire program.

It makes me very hopeful, seeing so many people step up and give their time and energy to Bitcoin, especially during times of pain.

We're not done yet.
https://blossom.primal.net/833de63c0d642b97bc6662803604b1…
where's the food?
older →