Compote

We're LIVE in 30 minutes! 🔴 How did a fake job interview turn into a $6.3B theft? @mssteuer and @HalbornSecurity's @urruts break down the Binance hack. → teapawt.net/i/spaces/1aWbJrgOkooQo…

Join our X Space with @mssteuer and @HalbornSecurity’s @urruts on what really happened in the Binance hack. 📅 Thursday, November 5th 🕐 1:00 PM ET 📌 teapawt.net/i/spaces/1aWbJrgOkooQo…

Thank you to our 2026 SALT London Sponsor: @Casper_Network Full agenda is now available here: salt.org/events/salt-london-…

Reminder: Casper Forward comes with backup from @ChainGPT_Pad AI API credits, IDO consideration for the strongest projects, and co-marketing in front of VCs. Applications are open: → forward.casper.network

Join us Thursday, Oct 29th for a FREE live webinar covering crypto taxes, tokenization, market analysis & a look inside the new CryptoCharged research desk. Special guests from @Casper_Network & @countonsheep. Bring your questions! Register 👇 tinyurl.com/CCwebinar102926

Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified. The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far. Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete. As an immediate precaution, Binance has: - temporarily suspended deposits and withdrawals while security checks are completed; - revoked the affected address authorisation; - engaged law enforcement and blockchain intelligence partners to trace and recover funds. Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice. Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions. binance.com/en/support/annou…

ICYMI: We have revamped our website! - A new look at the standard - Better in-depth info on how it works - Solutions pages on who it benefits and how - Who is building on the standard already - and more... Have a look here: erc3643.org

Not every smart contract comes with a dApp. Now it doesn't need one. Introducing Interact (beta) on CSPR.live: read and call the entry points of any contract on Casper, straight from the explorer. No CLI. No scripts. No custom frontend. 🧵👇

This is craazy. I asked one of our PhD engineers to look into NEAR *Confidential* Intents wondering how they designed their system. Unredacted, word-for-word, this was his answer 😱😱😱 "Everything I found out about the privacy claims and confidential intents is so bad that it seems almost comical and I cannot believe what I am seeing. Apparently they run a completely separate instance of the protocol, which is called FAR (as an opposite to NEAR), and that has a permissioned operator set. The entire confidentiality claim seems to rest upon the fact that it is a permissioned chain and the nodes are trusted to keep things private, there doesn't seem to be any deep technology behind it and it also does not seem to be open source. The entities running the nodes are also not publicly known. I almost feel weird writing this because it is so absurdly bad that it feels like ... I don't know ... a simulation? I know the usual level of overpromising in Web3 but this is so many levels beyond believable that it still feels unreal."