Radoslav Radev

⚔️ web3 auditor/dev | @0xPaladinSec | completed 65+ private audits (100+ overall) | developed 5+ defi projects | prev @Bonsai_DAO @rezolv_sol

[CD Security @CDSecurity_io]

🚨 Attention all Solidity dev teams - The ultimate Audit Preparation AI tool is here!

Fixing your entire audit preparation process in minutes instead of days for FREE.

Use it before your audit engagement and arrive fully prepared.

Fully open-source. Link in the comments👇

[Lee | 33Labs @33audits]

v1 of the @uniswap CCA audit agent is live on GitHub.

It catches the Critical integration bug we found in our recent audit of an auction built on CCA and a lot more. Tested it against a few scanners currently getting buzz on X, which currently miss the critical.

CCA configs are deceptively dangerous. Tick spacing, decimal accounting, a bunch of nuanced gotchas that are easy to miss if you haven't gone deep on the spec. This agent catches most of these CCA-specific bugs so you can fix them before your code ever hits an auditor's IDE.

Btw, I don't think any of these scanners should be a replacement for your auditor; a better framing is to think of them as dev tools. Run it early, catch the low-hanging fruit, and let your auditor focus on the stuff that actually requires a human.

Personally, I'm way more bullish on domain-specific scanners than generalized ones. Less context upfront leads to better results. That said, you can absolutely pull from this and add it to your current workflow to train your favorite agent.

https://t.co/yymC9i1YTY

[p4y4b13 @p4y4b13]

Had a great time auditing with fellow auditors @ret2basic and @radev_eth. We uncovered some cool bugs. Thank you @Slavcheww!

[Slavcheww @Slavcheww]

My thoughts on Move codebases after auditing a few last month with my team at @SBSecurity_.

- It’s surprisingly hard to find truly professional Move auditors who understand the language and the specifics of each Move chain, along with the main integrated protocols/libraries.

- The ecosystem is still young, but many products aren’t copy-paste from other chains. A lot of genuinely new ideas (at least from what I’ve seen).

- Documentation, APIs, and reference material around MoveVM are often incomplete. You end up relying on threads and discussions across different communities to validate behavior and assumptions.

- The language itself is relatively easy to learn.

Really grateful to have found one of the best auditors in this space - someone with deep experience across multiple topics who can cover everything end to end. Huge thanks to @ret2basic @p4y4b13 @radev_eth 🙏

[frescofresh @fresco_io]

Given that this protocol was just previously audited by a tier 1 firm, we have found some very impactful findings, that were missed.

The SR I am auditing with is surgical, this dude is GOOD and found some great things, and the boss man found a very impactful finding, that dude is an EXPERT. This is a damn good audit!

This is a very talented team on this audit, this is a damn good service and performance!

[Radoslav Radev @radev_eth]

@amaanbiz @nQ_Swap Dev: https://t.co/ScZYyE3Umt
Security: https://t.co/Lif9PjJD9E

[Lee | 33Labs @33audits]

a while back i wrote an article on some security-related nuances when building Uniswap v4 hooks. never shared it publicly but this ended up leading to me finding two high vulnerabilities in various private audits i did

https://t.co/e6jYjAuWcd

[Lyuboslav Lyubenov @LuboslavLubeno1]

We ran a blind, empirical test on most AI audit agents in the web3 space, using real contests.

The results?
Most tools missed critical flaws, drowned users in false positives or fail to run at all.

Thread 👇

[SBSecurity @SBSecurity_]

A security researcher we recently worked with was amazed by our work ethic 👀

He said:

“You grasp the code extremely fast. I like how you discuss every question in detail in your internal chat & everyone’s involved. And how smoothly everything else is divided among the team.🤝”

[Radoslav Radev @radev_eth]

@FynCas Podcast

[Radoslav Radev @radev_eth]

@FynCas AI

[Kris Paladin @MaslarovK]

How can you be sure a product is going to be successful?

In web3 this is mainly proven by investing in security.

Our friends at @max_apy refactored their code after their first audit with @rezolv_sol and requested another one after that, just to be sure their users are safe.

Turned out they were right to do so.

Here is the report 👇
https://t.co/2IzaIyyv8E

[Radoslav Radev @radev_eth]

@FynCas ONE

[Radoslav Radev @radev_eth]

@FynCas DAISY

[Radoslav Radev @radev_eth]

What our clients say about us ✅

[Radoslav Radev @radev_eth]

If you're auditing a protocol and can't find a way to steal all the funds or lock them forever, you're probably not looking hard enough.

This is the mindset we at @rezolv_sol brings to the table.
Because real security means thinking like an attacker - before one does.

[Radoslav Radev @radev_eth]

Actually the more I spend time with successful people the more I realise that the "FUNDAMENTALS" are the important ones.

- consistency
- discipline
- self control
- organisation
- proactivity

If you want to succeed at anything, just improve these "FUNDAMENTALS".

In web3 security, these aren’t just buzzwords - they’re what actually catch vulnerabilities.

[Radoslav Radev @radev_eth]

🚨 DON'T SKIP THIS POST 🚨

🤔 Ever wondered how to search for bugs effectively?

Here are two Proven Strategies you DON'T know:
$Strategy 1: Start looking where user input processed (try to trigger unexpected behavior)
$Strategy 2: Start looking where bad things can happen (and craft your input such that you trigger the bad behavior)

What are your strategies during an audit?