What really happened with #coldcard It wasn’t an “AI hack”—it was a 2021 firmware bug. The vulnerability was introduced in Coldcard firmware 4.0.0 in March 2021: devices bypassed their hardware random number generator and fell into key generation via software, predictable, seeded with non-secret chip data.  The specific error is in libngu: the guard uses #ifndef MICROPY_HW_ENABLE_RNG, which only checks whether the macro exists, not whether its value is different from zero.  Result: anyone can reproduce the seed candidates offline and derive addresses to compare them with the blockchain—without touching the device.
The figure keeps growing in waves: from an initial 594 BTC to 1.082 BTC (1,196 addresses) on July 31, then 1.158 BTC, and on August 2 a third wave brought the total to ~1.367 BTC (~$89M) from 4,585 addresses;  today people talk about a fourth wave. Coinkite released an emergency firmware on July 31 for all affected models, but installing it doesn’t fix an already-existing seed.  You must generate a new seed and move the funds. #HackerAlert #bitcoin $BTC
#baby $BABY Not everything is upside and it’s worth saying out loud. Trustless Bitcoin Vaults are a new, relatively unproven cryptographic construct over time, and there is a risk of smart contracts in the connections to external protocols. None of that disappears no matter how good the architecture is. That said, @BabylonLabs_io it eliminates two of the vectors that have destroyed the most capital in the history of this market: the risk of centralized custody and the risk of bridges. Swapping known, catastrophic risks for limited and auditable risks seems like a reasonable trade-off. $BABY #baby
#baby $BABY Lo relevant of Trustless Bitcoin Vaults is not the narrative, it’s how they solve an old technical problem. Bitcoin doesn’t support native covenants, so building programmable vaults has always been the bottleneck. @BabylonLabs_io leverage BitVM3 and verified zero-knowledge proofs directly on the Bitcoin blockchain: the withdrawal is authorized only when the contract state on the external chain is cryptographically demonstrated. Everything is auditable, everything is on-chain. Peg-in times have dropped to about three hours and on-chain costs have been reduced several times. That separates an academic experiment from something usable. $BABY #baby #onchain
#baby $BABY Case study: I have BTC and need liquidity, but selling isn’t an option. With the Trustless Bitcoin Vaults of @BabylonLabs_io I can lock my Bitcoin in a self-custodial way and borrow stablecoins against that position via integration with $AAVE . When I repay, the collateral is released. The BTC never leaves its chain and no custodian touches it. It’s Bitcoin no longer being a passive asset without ceasing to be Bitcoin. Watch out for the risks: it’s a new crypto construct and there’s smart-contract risk in the spokes. But the direction is the right one. $BABY #baby
#baby $BABY For years, BTC had two paths: sleep in cold storage without generating anything, or wrap itself into a synthetic token and cross a bridge trusting a third party. The Trustless Bitcoin Vaults of @BabylonLabs_io break that false dichotomy: your BTC is locked in a Bitcoin script created by you, on the native chain, and can still support DeFi activity on other networks. No wrapping, no bridge, no custodian. The difference isn’t marketing—it’s architecture: whoever controls the keys is still you. $BABY #baby
#baby $BABY buy a little bit of this in order to be able to participate in this new mission of #Binance I think it’s a good opportunity to have a system that allows generating profits with Bitcoin $BTC because keeping them in custody without doing any work at least bothers me. However, I think it’s still worth asking whether the risk outweighs the benefit of keeping Bitcoin only in a hold state versus putting it to work in babylon; I don’t know what you think? @BabylonLabs_io
#Completa los 2 objetivos y gana hasta 5,000 USDT en premios. Reto de Mayo 2026 – Exclusivo para Afiliados LATAM https://www.binance.com/activity/trading-competition/LatamAffiliate0501?ref=LT1W9SKE$USDT
Hey everyone, I got liquidated. I had time and the order wasn't moving and it never dipped to close. In the process, I managed to go long and then short since I was keeping an eye on it and was able to recover a bit, but I lost more than half. The lesson is that memecoins are risky, and even if you have your liquidation order set far away, you can still get wrecked.