co-founder & cto @fluentlabsxyz, building @fluentxyz; prev. solution architect @ankr; contrib: @erigoneth, @chiliz, @bnbchain; mscs
Dubai, UAE
Joined November 2017
- Tweets332
- Following188
- Followers975
- Likes405
One compromised DevOps laptop shouldn’t be able to move $6.3B.
The signing plane must independently enforce ledger invariants, per-asset outflow limits, velocity caps and M-of-N approval above thresholds.
How can they operate without such basic security checks? Curious to see the postmortem.
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…
While everyone is panicking over OpenAI’s ETH claim, almost nothing changes for crypto security (for now). Subexponential SAT doesn’t break SHA-256 or ECDSA.
The real implication, if verified, is that decades of human mathematical reasoning missed a better algorithm. The bottleneck may be our methods, not computation.
Dmitry Savonin retweeted
Spoiler: Korea has motion
200+ people came to Consumer Crypto Day, played our game and left with surprises
Fun seeing everyone get this excited, thank you for coming ily
Coming to KBW this year?
Come spend a day with us talking consumer crypto
App demos, good convos and a little surprise at the end
Register here: luma.com/1j1oxie8
Fluent is already rWasmified? 🤔🤔
Ethereum is slowly moving toward what Fluent implemented years ago.
eips.ethereum.org/EIPS/eip-8…
Every week a new rWasm release, and now it's v0.7.0, which is massive:
- New wide-arithmetic extension that bumps performance for BLS up to 2x and EVM opcodes like EXP/MULMOD up to 5x
- Even better Wasmtime compatibility for AOT execution
Read more: github.com/fluentlabs-xyz/rw…
If you missed yesterday’s Fluent v1.5.0 release, here’s a quick recap:
- Enabled the new rWasm v0.6.0 with new ISA for all precompiles (~4–5x performance increase)
- Block production benchmarks reached 1 Ggas/s
- Lots of bug fixes and code improvements, more docs, better comments, improved EVM compatibility, etc.
- Adjusted gas accounting for several EVM-related precompiles
Find more here: github.com/fluentlabs-xyz/fl…
Love the idea behind EIP-8337.
TL;DR: EIP-8337 is designed to pre-verify EVM bytecode and store the verified representation, ensuring that execution can't go out of bounds. This makes execution much more efficient because there’s no need to perform bounds checks at runtime.
These bounds checks are one of the biggest bottlenecks for ZK proving and AOT compilation. That’s exactly why we built rWasm IR.
rWasm takes a very similar approach: verify the Wasm binary once, compile it into rWasm IR, and then execute/prove the verified representation much more efficiently.
This EIP could make it possible to support AOT compilation from EVM directly into rWasm, without maintaining a separate EVM runtime and without the extra execution overhead.
Read more about rWasm here: github.com/fluentlabs-xyz/rw…
By the way, rWasm v0.6.0 is here 🚀
- much better Wasmtime fuel accounting and corner-case alignment, targeting 100% compatibility
- fixed syscall handling type checks (optional, but nice to have)
- hardened memory, table & stack bounds with safer bounds checks
- isolated instance state, with rollback on failed initialization
- new rWasm logo
github.com/fluentlabs-xyz/rw…
Apparently, AI might be the bottleneck in tech right now.
It was supposed to make development dramatically faster. But it also made attacking software dramatically cheaper.
Before AI, growth was fairly natural: more users → more revenue → more engineering effort.
Now anyone can probe, exploit, and automate attacks at scale. Every new feature creates more surface area that teams have to defend.
Hard to accelerate a market when so much of the acceleration goes into mitigating the risks created by the accelerator itself.
Apparently a fly brain is only ~140k neurons and a few million sparse connections.
Which means, unfortunately, running actual fly brains on Fluent is technically reasonable.
We built blended execution for this exact purpose. Probably.
For the first time, scientists have mapped the complete brain and central nervous system of an adult male fruit fly — a key model organism in science. 🪰
Working alongside HHMI Janelia Research Campus and the scientific community, @GoogleResearch scientists and researchers used AI to combine millions of 2D images into 3D neural shapes, reconstructing a record-breaking 166,000+ neurons. This foundational map of the adult male fruit fly brain can help accelerate our understanding of the brain, and is a major milestone in neuroscience.
ALT Vibrant 3D digital reconstruction of a fruit fly brain against a white background, displaying a dense, intricate network of multicolored neural fibers and cell bodies in shades of blue, cyan, orange, and purple.
ALT A complex 3D visualization of a fruit fly brain, featuring a dense, symmetrical network of thousands of tiny, multicolored neurons and fine, interconnected fibers in shades of blue, magenta, orange, and green against a solid white background.
rWasm v0.5.0 is out 🚀
- fused i64 opcodes: 16-21% smaller bytecode
- interpreter up to 3x faster on real fluent contracts (erc20 2x, keccak 2.4x)
- jit call overhead 117 ns → 18 ns (6.5x)
github.com/fluentlabs-xyz/rw…
Dmitry Savonin retweeted
Since we’re heads down building our first consumer app, @printsxyz has taken a back seat from an eco building perspective.
But the reputation thesis is stronger than ever.
Every app we build emits reputation data that other builders will eventually be able to integrate into their own products.
Wait! EIP-7928 is especially interesting for Fluent. Because of rWasm, we have one execution boundary for the entire block STF, regardless of which VM is used.
A block access manifest lets validators/provers prefetch touched state before rWasm execution, reducing cold I/O stalls and preparing ZK witnesses in parallel.
eips.ethereum.org/EIPS/eip-7…
EVM execution is slowly becoming less sequential.
Block-level access lists are the interesting part of Glamsterdam: once state dependencies are explicit, clients can parallelize IO and execution instead of discovering everything at runtime.
blog.ethereum.org/2026/08/17…
Dmitry Savonin retweeted
Excited to have @fluentxyz be part of this. Blockworks data everywhere, B1s are the new S1s.
