


top 0.01% hackers break your codebase | Trusted by @centrifuge, @zama, @lifiprotocol


At B612, we make sure your bug never becomes a hack story. Reach out for a security review: b612security.com/contact

A 22 year old hacker stole over 50,000 Bitcoin from Silk Road by exploiting a flaw in its withdrawal system, then hid the fortune for years before investigators found BILLIONS in crypto inside a popcorn tin. > In 2012, James Zhong discovered a weakness in Silk Road, one of the internet’s biggest dark-web marketplaces. > Its withdrawal system could be manipulated to release more Bitcoin than a user had deposited. > Zhong created around nine accounts and carried out more than 140 transactions in rapid succession. > In one instance, he deposited 500 $BTC and made five withdrawals of 500 $BTC within the same second, netting 2,000 $BTC. > Within days, he had stolen more than 50,000 Bitcoin, worth roughly $600,000 at the time. > Then came the hard part of hiding the money. > He moved the coins between addresses and used other methods to conceal where they came from. > In 2017, Bitcoin Cash split from Bitcoin but because Zhong still held the original Bitcoin, he received an equivalent amount of Bitcoin Cash. > He later exchanged the Bitcoin Cash for roughly 3,500 additional $BTC. > For years, the stolen fortune remained hidden as its value climbed into the BILLIONS. > But investigators kept tracing the missing Silk Road funds, using blockchain analysis and other evidence to connect the coins to Zhong. > In November 2021, federal agents raided his home in Georgia. > They found Bitcoin in an underground safe and on a small computer hidden inside a popcorn tin in a bathroom closet. > The seized Bitcoin was worth more than $3.36 BILLION at the time. > Zhong pleaded guilty to wire fraud and was sentenced to one year and one day in prison. > He exploited a flaw in a system handling digital money, then spent years trying to keep the proceeds hidden. But the trail didn't disappear with the coins.

Building or upgrading an Ethereum client, consensus or networking code, or a ZK or cryptography-heavy protocol? Reach out for a security review: b612security.com/contact

Alex Filippov built his own tool that runs AI agents to verify his leads, build end-to-end PoCs, and write reports. Finding unique issues still comes from his judgment, which was polished with years of experience breaking complex systems apart. Full breakdown 👇
B612 Security @b612security Nov 10 Article How Ethereum's Top Bug Hunter Finds Unique Bugs (w/ Alex Filippov) Alex Filippov breaks Ethereum for a living. He won the Ethereum Foundation's $2M Lighthouse competition, taking home $203,733 with a single High-severity finding. He won the Ethereum Fusaka Upgrade


Building a Move protocol on Sui, a liquid staking protocol, or an L1 client's consensus or transaction validation? Reach out for a security assessment: b612security.com/contact



(4) Isolation is built in and tested. Request IDs use `vault << 96 | localId`, preventing collisions between vaults; `VaultIsolation.t.sol` and `CrossPoolIsolation.t.sol` cover this and related ownership boundaries.

(3) The documentation explains the design conceptually, not just contract by contract. `ARCHITECTURE.md` derives buckets, contributions, and the horizon from five constraints, supported by a glossary, a worked pro-rata example, and diagrams covering settlement, escrow reservations, configuration, and instant routing. This design keeps hub settlement O(1) regardless of how many people are in a bucket.

(2) Conservation and backing are tested from several angles through `BucketLibInvariants`, `VaultInvariants`, and `VaultPricingLibInvariants`. The bucket math is also checked against an independent reference implementation in `BucketReference.sol`, while the Recon/Echidna/Medusa suites exercise the VDK end to end.

(1) The spec doubles as a coverage map. `src/vaults/SPECIFICATION.md` states one property per row; the `Tests` column names property-level coverage and marks gaps with `-`. Every deliberate non-guarantee is marked `n` and explained.

The Centrifuge team did an excellent job making security properties explicit: an immutable Vault per `(pool, share class, asset, variant)`, with behavior fixed in policy contracts at deployment, clean hub/spoke boundaries, and layered checks around policies, callbacks, escrow reservations, and permissions. 🧵🧵🧵

We've completed the security assessment for @centrifuge's new Vault V2 contracts. 1 high, 4 low, and 1 info issues were found. The Centrifuge team has successfully resolved all of them! Full report: github.com/b612security/Secu…
Introducing the Vault Development Kit (VDK), powered by Centrifuge. A modular framework for building differentiated onchain financial products without rebuilding the underlying vault infrastructure from scratch. Developers configure the mechanics their products need, whether that's instant redemptions for a treasury fund, lockups and scheduled settlements for private credit, or senior and junior tranches for structured credit. The VDK provides a shared foundation for accounting, settlement, escrow, and portfolio controls. With the core infrastructure in place, builders have more freedom and flexibility to explore unique financial structures and use cases. Build what makes your product different.

School called the police at 13. $159,654 on bug bounties and competitive audits by 18. Live tomorrow!

The B612 Security team is made of ethical hackers with years of experience reviewing and breaking complex systems. On top of that, they run custom AI workflows, the same ones that regularly surface high-impact bugs in bug bounties and live protocols. Reach out for a security review: b612security.com/contact