Preetam | QuillAudits π₯·π
@raopreetam_
Followers
9K
Following
25K
Media
640
Statuses
5K
Co-founder @QuillAudits_AI | 7+ yrs, 1400+ clients secured | Core Contributor @Wach_AI | Building AI Adversaries @QuillAI_Network
π¦πͺπΊπΈ
Joined April 2014
Focussing on infrastructure gaps that are holding back the entire ecosystem rather than trying to build the next big application : ). Most problems stem from the fact that building secure, complex applications is still incredibly difficult. $500K - Advanced AI-assisted analysis.
if you had $1.3m to deploy to ethereums biggest problems/opportunties, what would you spend it on?. asking for a friend.
0
0
10
0
2
0
RT @Wach_AI: No blind dates. Just verified tokens. Now live on @baseapp and @farcaster_xyz : the dating mini-app for tokens. Profiles > vβ¦.
0
18
0
This creates virtuous cycles:. β’ Better judge experience β more experienced judges participate. β’ Faster results β protocols prefer these contests. β’ Higher quality competition β researchers improve faster. β’ Cleaner reputation β attracts better participants. Higher.
Probably the biggest reason contests are flooded with low-quality and AI-generated submissions is that participants have no skin in the game. It literally costs nothing to spam a contest with hundreds of of junk findings. And the cost is paid elsewhere:. - by judges drowning in.
2
0
9
RT @QuillAudits_AI: One of the best ZK education learning library if you want to get started in 2025. We're not biased. .
0
1
0
The privacy space has been dominated by cryptographic maximalists who prioritized perfect privacy over usable privacy. They built solutions for people who wanted to disappear completely, not for people who just wanted reasonable financial privacy. The actual privacy market is.
Onchain privacy hasn't reached product-market fit because the product wasn't right, not because the market is not there. The product (past onchain privacy solutions) wasn't right primarily due to:. 1. Lack of zero-compromise privacy. Privacy cannot come at the cost of access to.
2
0
8
RT @QuillAudits_AI: . @Paycio_Global π€ @QuillAudits_AI!. We're excited to announce that we've commenced a comprehensive smart contract secuβ¦.
0
2
0
gMove. Sui and Aptos are hitting that growth phase but most security firms are still treating Move as a "nice to have" skill rather than a core competency. The Move audit market is one of those "obvious in hindsight" specializations that most auditors completely missed. Move.
I just realized I've been booked every month for the past 6 months with Move audits. Started a 2 week Sui Move audit and the client already approved + extended for another week to cover the rest of their codebase. Proof that demand for Move isnβt slowing down anytime soon.
1
0
10
RT @0xReactive: Today We're Introducing The BUIDL With REACT Campaign: A Fast-Track to Mainnet. This is a developer focused initiative desiβ¦.
0
78
0
As someone who has been running a security for 7+ years, here's some alpha on how to boost this:. Remember that security audits are essentially trust purchases. Projects aren't just buying your ability to find bugs, they're buying confidence that you won't miss the bug that costs.
The best way to get projects to do a security audit with you if you are a solo auditor, small team or a company is through referral. This is why you need to make sure to build good relationships, be resourceful, helpful and deliver on your promises. Also, know how to ask for itπ«‘.
2
0
13
We're in this brief historical moment where LLMs are powerful enough to be genuinely useful but adoption is low enough that using them well creates real edge. In 12 months, everyone will be using LLMs for security research. Right now, you can build systematic advantages while.
Let this be your final call. If you're still on the fence with using LLMs in your security flow, please for the love of God, start using it NOW. It's an incredible tool, extremely powerful BUT in specific ways. You have to learn to wield it to get the maximum possible value.
0
0
8
Web3 security is the perfect field for this mindset because:. β’ Mistakes cost millions, so deep analysis is actually valued. β’ You can't just run automated tools; you need creativity. β’ You're modeling human incentives, not just code behavior. β’ New protocols mean new.
Should you get into web3 security? The real nature of the job. A little reflection on a Saturday afternoon. Software security, specially the current state of smart contracts' security, is a weird chimera of a philosophical and technical job. Even in the future of the industry,.
1
0
9
Crypto's Architectural Peacocking. Developers add layers of abstraction not because they're needed, but because simple solutions feel "unprofessional.". Classic examples:. β’ Proxy patterns when direct upgrades would work fine. β’ Complex inheritance hierarchies instead of
0
0
6
RT @W3X_NW: π Exciting news for Web3 X Incubation Program participants! .@QuillAudits_AI is offering up to $20,000 in credits to leverageβ¦.
0
4
0
It's about founder-market fit vs founder-founder fit. Web2 founders build for markets. Web3 founders build for other founders. One approach scales to billions of users. The other scales to thousands of crypto natives who already agree with you. Web3 founders have somehow.
web2 founder: i will cold call 500 fortune 500 CEOs and get them to sign up. web3 founder: i will run an NFT campaign, create a gated discord, and then i will make them play a game before they sign up.
0
0
3
The meta-skill is essentially adversarial thinking, you're always asking "how could this break?" or "where's the inefficiency?". What's fascinating is the career incentive structure:. β’ Auditing: Steady income, reputation building, but capped upside. β’ MEV: Unlimited upside,.
Weekend realization: The skills for MEV and auditing have a 90% overlap: deep protocol knowledge, gas optimization, and the ability to read raw calldata. The only difference is what you do when you find something. One gets you a report, the other gets you a profit.
1
0
6