Running bitcoin

Mozilla created Rust Microsoft uses Rust. Amazon uses Rust. Google uses Rust. Meta uses Rust. Firefox uses Rust. Discord uses Rust. Cloudflare uses Rust. The Linux kernel supports Rust. Memory safety, No garbage collector, High performance. Why isn't Rust the default choice for more developers?

Last night, three of my wallets were drained. I still don’t know exactly how this happened or what the attack vector was. Over the past week, we’ve seen multiple security incidents and vulnerabilities being discussed across the industry, including PHP-related security concerns and other potential exploits. I don’t know whether any of these incidents are connected to what happened to me. The amount involved is significant, and honestly, I’m struggling to process what has happened. I’ve spent years in this space, and experiencing something like this is absolutely heartbreaking. Right now, I’m trying to trace the transactions, investigate the affected wallets, and understand how my security was compromised. If anyone has experience with wallet drainers, compromised devices, malicious browser extensions, or on-chain investigations, please reach out to me via DM. Any genuine help in identifying the source of this attack would mean a lot.

Agree with you.

A hacked power meter could in theory leak a private key. So make sure to generate your own power

【速報】GMO、パソコン電源落とすよう呼びかけ news.jp/i/148762435443094372…

fear not the man who shills 1,000 tokens fear the man who shills 1 token 1,000 times

Hackers managed to steal authentication keys for devices made by @KeystoneWallet I don't understand one thing here however. During manufacturing, as part of the factory self test in initial boot you have the device generate & save a private key on its own, and take note of the public key. If you have private keys to be stolen, it means that *somehow* a copy of the key exists outside of the secure element on the device? If the manufacturing process involves each device's private key existing outside of the device, there's something that needs urgent improvement. Have the device generate the key and include its own public key as part of its self test report, not the other way around. xitter.cf/tayvano_/status/211475…

Credit default swaps of French government bonds. Scary Fasten your seat belts.

BLOOM USERS WENT TO SLEEP WITH $947,000. THEY WOKE UP TO ZERO. NOBODY CLICKED A LINK. NOBODY SIGNED ANYTHING. THEIR WALLETS DID IT FOR THEM I've been staring at the Bloom drain for an hour and I'm genuinely shook. this wasn't some guy connecting to a fake mint site. this was a trading bot thousands of us use every day. 9 users. 49 wallets. ~$947k in SOL. gone while they were asleep. let me walk you through it because the timeline is insane: > 00:59:45 UTC: THE KNOCK 1 lamport leaves the biggest victim wallet. a millionth of a dollar. a test. someone is checking if the door opens. > 01:02: THE ROLL CALL ten wallets send 0.001 SOL each to the same address. one every 2 seconds. like a machine taking attendance. by now the script knows exactly which wallets it owns. > 01:03:50 → 01:04:41: THE MASSACRE 47 wallets drained in 51 seconds. 1,636 SOL. 1,039. 1,021. 765. 640. 612. bang bang bang bang. every single tx signed by the victim's own wallet. paying its own fee. the wallets literally paid to rob themselves. > 01:28: HE COMES BACK FOR SECONDS he notices one drained wallet still has ~$49k in USDC but no SOL for gas. so this mf SENDS IT 0.02 SOL. tops up the victim. to rob the victim again. tries tiny 0.000001 USDC tests. it fails. that $49k never reaches him. cope. > 04:26: HE GETS DOXXED ON-CHAIN Onchain Lens posts his address. > 04:30:56: 4 MINUTES 46 SECONDS LATER all 9,408.21 SOL leaves in ONE transaction to a brand new wallet. he was refreshing X. of course he was. > AND THEN HE FREEZES 10+ hours. not one move. no bridge. no swap. no exchange. $947k sitting in one wallet in front of the entire timeline. > NOW THE FUNNIEST PART other scammers are dusting him from lookalike addresses. 7kY8qx…p8BQ is the hacker. 7kY82x…C8BQ and 7kY84Y…mMzQ are vultures. they're praying he copy-pastes the wrong one when he cashes out. scammers. robbing. the robber. Bloom says: third-party module, remote code exploit, no private keys leaked, 100% refund for all 9 users. glad about the refund. genuinely. but read that again: "no keys leaked" and yet 47 wallets signed their own drains in 51 seconds. if someone can make your bot sign whatever they want, does it even matter where the key is? I'm not touching a bot that holds my keys until someone explains which module, how long it was exposed, and who else ran it. tracehound rebuilt every tx of this. the drainer is being watched. the second those 9,408 SOL move, we'll all see where