pyk retweeted
I’ve been researching @Zcash security as part of our internal work at @osec_io.
Today, I’m happy to share that the total amount I’ll be receiving in bug bounties from @Zcash has finally been confirmed at $972K.
I’m really proud of what came out of this research. More importantly, I’m glad our work contributed to improving Zcash’s security and got more security researchers interested in Zcash. It’s especially great to see that many researchers are still looking into Zcash, finding and reporting bugs, and keeping an eye on its security.
Huge thanks to the teams across the Zcash ecosystem, including @Zcash, @zodl_co, @ZcashFoundation, @ValarGroup, @ShieldedLabs, @TachyonZcash, and @ZcashCommGrants, for taking security seriously and rewarding researchers, and to the entire Zcash community for all the support.
I’ll keep doing my best to find more bugs.
context: yes, i do write extremely fast smart contract fuzzer github.com/pyk/ripfuzz 🏎️💨
Friendship ended with Panic(0x1), now BrokenInvariantError is my best friend
learned the Panic(0x1) pattern from hevm, echidna, medusa and foundry, shipped it in ripfuzz, retired it today. BrokenInvariantError carries id + description in plain revert data.
Rest in peace bro 🪦
wrote a whole breakup post for a panic code 😂
probablyrevert.com/blog/2026…
pyk retweeted
The next era of Web3 infrastructure deserves a brand new type of security review.
For @0xPolygon's Heimdall v2 upgrade, Sherlock is bringing that model to life.
June 15 to July 6.
day 396/0 crits found
i've been continuing my journey building a coverage-guided smart contract fuzzer from scratch with revm. for learning purposes.
i published two blog posts this week about the topic
i have a bunch of ast-grep rules. planning to move them to a custom cli this weekend so i can fully control the output (reduce token usage, etc).
wasn't sure Kimi K2.6 could one-shot this, turns out it actually can ... pretty impressed bro
feels like the custom compaction is a key reason these long-running tasks work well. i borrowed the technique from codex and added some adjustments on top (skill-aware compaction, etc)
this graph perfectly shows how hyped i was for @FireworksAI_HQ fire pass v2
so far so goooood, <1s ttft & >150 tps. hit a few rate limits on the first day, needs to adjust my workflow and my harness retries need some work
aside from that, zero issues. barely touching GPT 5.5 now
trying out Kimi Moderato plan today, it turns out it has better cache hit rate than the Fireworks
speed is ok-ish
