Pinned Tweet
🧵/1
There are already multiple free AI auditors for smart contracts
But there are almost none focused on blockchain / DLT systems themselves: clients, consensus, execution, bridges, mempools, state sync, resource accounting, and protocol logic.
I spent 7 weeks worth of ChatGPT Pro 20x tokens building DLT Auditor v1
Now I’m sharing it for free: github.com/RASHMOR1/dlt-audi…
🧵/5
The designs are not generic prompts.
Each one starts from a default audit design and is trained into a specialized prompt pack against a specific audit competition or target class.
The AI runs the design, compares its output with confirmed findings, studies what it missed, and refines the prompts.
That loop repeats until the design can find all, or almost all, of the confirmed findings.
1
2
517
🧵/6
This is only v1.
There is still a lot of work to do, and a lot of room for improvement: better designs, bigger corpus coverage, stronger validation, more target classes, and better reporting.
But I think this direction matters.
Wait for DLT Auditor v2.
Let’s raise the security bar for DLT projects and make this space safer together
5
432
DLT Fix Finder 🔍
github.com/RASHMOR1/dlt-fix-…
🧵\1
Turns Git history into a reusable corpus of vulnerability fixes for blockchain and distributed ledger (DLT) systems.
2
8
267
🧵\2
It’s a more advanced version of my earlier tool, GitFixFinder (teapawt.net/rashmor_eth/status/203…), which was focused on smart contracts.
DLT Fix Finder is built specifically for blockchain / DLT codebases.
G I T F I X F I N D E R
The Patch Historian
🧵 /1
I built Git Fix Finder — a tool that turns a repository’s git history into a corpus of real vulnerability fixes.
It extracts security-relevant patches and turns them into structured findings.
Essentially adding another source of real-world vulnerabilities for auditors and AI agents to learn from.
1
1
223
I’ve been experimenting with a different approach to AI auditors.
Most current AI auditors follow predefined pipelines (I wrote more about that here: teapawt.net/rashmor_eth/status/203…).
I wanted to make it more creative.
1
1
159
A different way of exploring the codebase, not a better checklist.
The results were inconclusive — it performed roughly in line with some other AI auditors. Some did better, some worse, but bug coverage wasn’t really the goal here, so it’s hard to measure this approach in a traditional way.
1
1
87
I’m open-sourcing it in case someone finds the idea useful or wants to build on it:
github.com/RASHMOR1/Self-Scr…
I think there’s still a lot of unexplored design space in how AI auditors should actually work.
1
86
1/🧵
Just shipped Just Another State Analyzer — a tiny tool that does exactly one thing: finding state and invariant inconsistencies in smart contracts.
It’s not trying to be a full AI auditor, and that’s 100% the point.
2
6
472
7/🧵
Not saying mine is better.
The real point is that tiny differences in approach and workflow can be enough to surface a bug another tool overlooks.
1
1
158
8/🧵
That’s exactly why I think open-source AI auditors complement each other — kinda like an audit contest. Different tools catch different things, and together they make protocols safer.
This release is just that: not a silver bullet, just one more useful lens.
github.com/RASHMOR1/just-ano…
1
164


