Audit Wolf

Inspiration

The inspiration for Audit Wolf came from a simple idea — curiosity. I wanted to push myself to build something meaningful within the hackathon timeframe, while also exploring how modern developer tools could speed up the process. The thought of combining AI-driven assistance with my own development workflow kept me motivated. What started as an experiment quickly turned into a mission to create something practical, useful, and hopefully impactful.

What it does

Audit Wolf is designed to make smart contract auditing simpler and more accessible. The system analyzes contracts for vulnerabilities, performance issues, and best practices, while also generating insights and structured reports. The goal is to give developers a tool that not only helps them identify problems but also guides them towards better, safer code.

How we built it

The foundation of this project was built using Kiro IDE, starting from the MVP stage. Kiro allowed me to prototype, test, and iterate rapidly. Along the way, I explored a wide range of technologies and frameworks — some familiar, many brand new. I might not be an expert in all of them yet, but I can definitely say my technical vocabulary has grown a lot.

On the technical side, I experimented with:

• Kiro IDE for building and iterating
• Nx for modular architecture (though this didn’t work out as planned)
• Next.js, Supabase, and other supporting frameworks
• Debugging, testing, and using AI-powered assistance to refine the system

It was an exciting journey of learning by doing, with plenty of trial and error.

Challenges we ran into

The challenges were plenty. At first, I tried building the project entirely on Nx Framework. The result was a tangled system where nothing worked as expected, and file organization became nearly impossible to manage. After spending too much time in that maze, I made the tough call to scrap it completely and start fresh from scratch.

Another hurdle was with AI-powered bug fixing. While Kiro’s assistance was incredibly helpful most of the time, there were moments where it tried a couple of fixes and then suggested we “accept the errors as they are.” Of course, that wasn’t an option. I had to dig deeper, troubleshoot manually, and sometimes rebuild sections to get everything working smoothly.

These struggles, while frustrating in the moment, ultimately shaped the project into something stronger.

Accomplishments that we're proud of

• Successfully pivoting from a broken Nx-based model to a clean, working architecture
  
• Building an end-to-end system that can audit contracts and generate insights
  
• Gaining exposure to a wide variety of frameworks and tools within a short timeframe
  
• Turning setbacks into learning opportunities rather than roadblocks
  

What we learned

This project taught me that building something impactful is rarely a straight path. I learned how to navigate between frameworks, when to scrap something and start fresh, and how to work alongside AI tools without becoming fully dependent on them. Most importantly, I learned that persistence and adaptability matter more than getting it right the first time.

What's next for Audit Wolf

Audit Wolf is just getting started. Moving forward, the plan is to:

• Expand vulnerability detection with more advanced static analysis tools
  
• Add real-time monitoring for deployed contracts
  
• Improve the developer experience with richer reports and integrations
  
• Open-source parts of the project to involve the community
  

The journey so far has been challenging but rewarding, and I’m excited to take Audit Wolf to the next stage.

Built With

• bullmq
• express.js
• langchain
• next.js
• node.js
• openrouter
• postgresql
• puppeteer
• railway
• redis
• senderwolf
• sentry
• shadcn
• supabase
• tailwind
• typescript