alpharush
@0xalpharush
Followers
9K
Following
3K
Media
113
Statuses
3K
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.
3
4
51
What became of IDL standardization? There is a forum discussion from 2023 and it looks like anchor’s latest format is not widely adopted.
1
0
2
Generate videos in just a few seconds. Try Grok Imagine, free for a limited time.
1K
2K
10K
RT @tayvano_: @Cachorroexausto @deadrosesxyz No it’s not blurry. It doesn’t matter what other people do it matters what you do. If you cho….
0
1
0
I should not have to login to see issues on cantina or solodit.:man-standing:.
4
2
48
Any retrospective on why beaconfuzz did not find the pectra lighthouse issue?.
2
0
10
Find out what compiler flag incantations are necessary to fuzz rust with LibAFL, and save yourself some pain.
New blog post: An Intro to Differential Fuzzing in Rust, by @nl_gripto & @anarcheuz. It walks through building a pure-Rust JSON fuzzer from scratch, then extending it into a differential fuzzing harness capable of surfacing consensus bugs.
1
1
20
The date is a coincidence but I am thinking about this again.
Not the solution people like to hear, but the way to repeatably build high assurance software is to follow repeatable practices during development. Everything else is downstream of that.
1
0
10
Contests are funnels for the audit firms attached to them and fellowships are inexpensive non-compete agreements for contractors. One of the cost levers was open-source development and public research which is now diverted into cheaper, content-mill marketing.
1
1
32
The solidity compiler continues to be a bottleneck to execution improvements in addition to stifling L2 experimentation as has been discussed in the past. For example, it’s still not possible to use eofcreate in the latest release.
0
0
1
This does suggest that large, future EVM changes should include integration testing at the app level as well IMO.
1
0
3
Seen a lot of exaggeration about the changes required to migrate code — which is opt-in. I think it’s fine to critique the upgrade as not worth the risk, lacking essential features, or solving issues at the wrong part of the stack, but at least rigorously engage with it.
The team prepared valuable input to the discussion on @solidity_lang libraries "compilation to EOF" issues. It's worth reading and decide if it's complicated or easy.
1
0
7
RT @samlafer: There's been a lot of discussion around zk(E)VMs lately. Good moment with everyone VM nerd-snipped to discuss FPVMs (fault pr….
0
1
0
Noticing a lot of what looks like LLM GitHub bots lately. Or maybe people really do create superfluous rationales with headers for PRs….
1
0
5
The trade-off in the security space isn’t about how the persons are organized or compensated, it’s whether the orgs will compete to make themselves irrelevant by improving freely available tech and sharing research.
0
2
11
My intuition was it would have a lower memory footprint but also captures “more rare” entries.
0
0
3
This is an interesting result and demonstrates the value of effective benchmarking. Echidna has used PC coverage since its inception but edge coverage is a staple following AFL’s innovative approach. Sam Alws did a great job getting it over the line.
Medusa's new branch-based coverage outperforms PC-guided fuzzing in benchmarks, while revert reports make debugging contract failures straightforward. Find bugs faster with less effort.
1
2
17