How ✨I found a critical vulnerability✨ in @zora's ERC20Z contract via a little known Uniswap v3/v4 property When Zora put out this article: https://t.co/jOYLVP0kfd outlining their new protocol, I was intrigued and had to learn more From a high level, the system works by

the more i dig in, the more impressed i am by this exploit writeup soon

This episode provides a clear outline of conservatism against that of the left, and other right wing ideologies.  It also illustrates a way forward for our nation. Listening to "The Mirror, the Window and the Anchor: A Conservative Stand" at

yETH totalSupply and reported market cap after the attacker drained the pool and triggered an underflow to mint an astronomical amount of LP tokens 703 septendecillion, 437 sexdecillion, 853 quindecillion, 798 quattuordecillion, 36 tredecillion dollars

have been reading up on the recent @yearnfi yETH exploit. this is one of the most complicated exploits i've ever seen might writeup a simplified yet thorough breakdown. any interest?

something to consider here: the agents found 55.88% of vulnerabilities, but only $4.6m worth of exploited revenue. meanwhile there was >$800m of funds exploited in this timeframe so really they only managed to exploit ~0.6% of the total funds seems like agents are currently

"In just one year, AI agents have gone from exploiting 2% of vulnerabilities in the post-March 2025 portion of our benchmark to 55.88%—a leap from $5,000 to $4.6 million in total exploit revenue. More than half of the blockchain exploits carried out in 2025—presumably by skilled

anthropic researching ai smart contract security 👀

might have to increase my weekly rate over the winter to account for the opportunity cost of not snowboarding

most of the time when i review assembly, it ironically seems to generally have much less bugs than high level solidity not sure if this is just because devs that can write assembly write less bugs, or because assembly is more predictable

core solidity is gonna be so fun to audit

getting security reviews during the early stages of building is extremely underrated nothing worse than working for months before going to audit, just to be told that a redesign is in your best interest

looks like I'll be working on an amm/math ctf 🫡

what would u most like to see for my next ctf?

if the market degrades and i stop being consistently booked i will simply continue to accumulate skills and learn as much as possible

solution:

✨follow for more CTFs✨ i'm already getting started on the next one

here's the solution to the puzzle i posted a couple hours before the ctf, in case you've been wondering https://t.co/J6qpQWfEIU

this was inspired by this old post by @sw0nt. when I first saw this three years ago, I knew I had to build something with it https://t.co/f0jEtfDe1L

source code:

Onchain CTF Solution Writeup Let's break down the CTF and see how the solution was there all along Shoutout to @yum1n__ for solving first and taking home 0.1 ETH! The contract (source linked below) was a minimal proxy with two execution branches: SET_IMPLEMENTATION and

the solution to this was that each color corresponds to a 3 byte rgb hex value, e.g. the first color is #604980 -> 0x604980 if you retrieved the rgb hex value of each color, and lined them up in order, you'd get the contract bytecode