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.
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.
pyk retweeted
I Saved Injective's $500M. They Pay Me $50K.
I like hunting bugs on @immunefi . I'm decent at it.
- #1 — Attackathon | Stacks
- #2 — Attackathon | Stacks II
- #1 — Attackathon | XRPL Lending Protocol
- 1 Critical and 1 High from bug bounties (not counting this one)
Life was good. Then I found a Critical vulnerability in @injective .
This vulnerability allowed any user to directly drain any account on the chain. No special permissions needed. Over $500M in on-chain assets were at risk.
I reported it through Immunefi. The next day, a mainnet upgrade to fix the bug went to governance vote. The Injective team clearly understood the severity.
Then — silence. For 3 months. No follow up. No technical discussion. Nothing.
A few days ago, they notified me of their decision: $50K. The maximum payout for a Critical vulnerability in their bug bounty program is $500K. I disputed it. Silence again. No explanation for the reduced payout. No explanation for the 3 month ghost. No conversation at all. To be clear: the $50K has not been paid either.
I've seen others share bad experiences with bug bounty payouts recently. I never thought it would happen to me. I can't force them to do the right thing. But I won't let this be forgotten.
I will dedicate 10% of all my future bug bounty earnings to making sure this story stays visible — until Injective pays what I deserve.
Full Technical Report: github.com/injective-wall-of…
The $100,000 USD @AlchemixFi V3 Audit Competition is finished, and the full results have been posted. 100% of the pool has been paid out!
🥇@0xfrsmln: $12,446
🥈 @ZeroK_____: $8,714
🥉 @niroh30: $7,780
4⃣ @magtentic: $6,997
5⃣ @PaludoX0: $6,748
Check the link below for the full leaderboard and bug reports! 📷👇
pyk retweeted
The human in the loop isn't a limitation to overcome.
It's a feature to protect.
Full post: adventures.nodeland.dev/arch…
pyk retweeted
Good weekend read 🦀
Writing a mockable Filesystem trait in Rust without RefCell
#rust #rustlang #programming
pyk.sh/blog/2025-12-15-writi…
pyk retweeted
Writing a Type-Safe Linux Perf Interface in Zig pyk.sh/blog/2025-12-11-type-…
pyk retweeted
Check out the latest additions to the Public Fuzzing Campaigns List:
@contractlevel Contract Level Yield Foundry Invariant Testing Suite
@BreederDodo Cross-Chain DEX by @sepyke
@eulerfinance EulerSwap by @vn_martinez_ (@EnigmadarkLabs)
Link below👇
pyk retweeted
Welcome back to Sherlock's Vulnerability Spotlight, where we highlight an impactful vulnerability uncovered during a Sherlock audit.
This week, we have an Unvalidated Cross-Chain token swap.
It was uncovered by @0xekkoo, @0xapple_, @elolpuer, @x0sauce, @patitonar, @sepyke, @0xseeques, @wellbyt3 on the @BreederDodo Cross-Chain DEX contest. 🧵
pyk retweeted
This is my third attempt at a fuzzer for EVM contracts. Early days but hope to share more before EOY. Also @gndizzy is awesome to work with
pyk retweeted
Have you already tried the new Foundry v1.1 stable release?
$ foundryup -i stable
Highlights include faster code compilation with dynamic test linking, faster trace decoding and new cheatcodes!
Make sure to check out the release notes below 👇
github.com/foundry-rs/foundr…
gm
wanna run tenderly-style trace browsing on your own foundry debug logs?
give foundry-tracer a try
nice colors, collapse/fold, accepting any and all qol prs
hopefully makes debugging a bit nicer
code is 15% me, 85% augment
pyk retweeted
EntryPoint v0.8 is live!
✨ A major upgrade that v0.8 offers is native support for EIP-7702 ✨
This will allow any EOA that uses EIP-7702 to also make use of the pre-existing and comprehensive ERC-4337 ecosystem of bundlers and paymasters.
pyk retweeted
Replying to @WenLlama
@WenLlama Graze'd with @wenmarkets , the call is up, have a listen, get some alfa, thank you @omnifient and @0xcarnation @0xPolygon
youtu.be/vLF2fTUgMmQ
pyk retweeted
Coming Soon: The Astro Content Layer
‣ One API for all of your site content
‣ Local Markdown, MDX, JSON, CSV, etc.
‣ Remote Data (API, or your favorite CMS)
‣ Backed by SQLite
‣ In development, coming this fall
astro.build/blog/future-of-a…
pyk retweeted
rust x ethereum + rethathon July 2024, mark your calendars - more details soon
This quoted post is unavailable.




























