RobChampion @Rob_Champ_

@federico_rivi @st3b1t @Albi_on_Air Oggi ho sentito che deve essere garantito il "diritto universale alla felicità " 🤣. Questa nemmeno a miss Italia la dicevano

@federico_rivi E soprattutto fan di Vannacci XD

@crypto_gateway Lo vendono già aperto o ci sono le istruzioni?

@federico_rivi Lo vendono già aperto o ci sono le istruzioni?

bitchat 2 is out now

Questa me la rigiocherò

Retro Coast @RetroCoast

a month ago

Voting is the adult version of writing a letter to Santa Claus

347 7K 39K 665K 2K

@st3b1t @m_crosetti In questo caso penso manchino semplicemente delle panchine

@Carlomrtz Rimarresti sempre ricattabile. Non ci potrebbe mai essere prova matematica che i dati vengano distrutti dopo il pagamento

Bitcoiners at a dinner party #dexter #bitcoin

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.

@st3b1t Lavorano con sistemi più o meno Legacy che comunque vanno gestiti

@giacomozucco Ti sei cagato addosso immagino

@Skoorbkaz @AnthropicAI Inevitable

- Government: "Nobody can compete with our currency." - Bitcoin: "I don't compete. I just exist." - Government: "You're too volatile!" - Bitcoin: "I'm 17. You're 55 and down 97%." - Government: "You're not backed by anything!" - Bitcoin: "I'm backed by math. You're backed by promises." - Government: "People trust us!" - Bitcoin: "Then why is your printer a secret and my ledger public?" - Government: "...You're not an economist." - Bitcoin: "No. I'm the audit."

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.

@BlockstreamJade also i think most bitcoiners don't realize in effectively all HWWs with (physical) SEs, the SE just verifies the PIN, and transfers the seed or master private key to an MCU. the MCU security isn't SE level. so the distinction is more academic than people are understanding.

ZEUS infrastructure is temporarily offline following a cybersecurity incident. The attack has been mitigated. We are keeping services offline while we conduct a comprehensive audit of all systems before restoring operations. **Customer funds were neither lost or at risk.**

Incredible video explaining the Bitcoin wallet hack

@federico_rivi Molto Cypherpunk..

@federico_rivi E se gli agenti decidessero autonomamente di convertire una parte delle stablecoin in ₿, considerandolo la riserva di valore definitiva? 🤖