
Resident & Security Researcher @cantinasecurity | Request an audit 📝 @ https://xitter.cf/t.co/i51slFowVa
Joined July 2017
- Tweets298
- Following94
- Followers136
- Likes2.5K
kodyvim retweeted
Glider Contest final leaderboard.
🥇 @ChaseTheLight99
🥈 @0xodus
🥉 @0xK42
Congrats, and thanks to everyone who submitted queries.
kodyvim retweeted
Three new queries approved.
@0xangky lags liquidation executed without health factor validation, allowing unsafe position closures.
@kodyvim_ flags contract logic that updates state via memory copy, creating silent data corruption risks.
@baptonic3 flags missing message origin validation in LayerZero V2 LZCompose, enabling cross-chain message spoofing.
Queries below:
kodyvim retweeted
Smart contract audits are expensive. Audit firms cost 20k-40k per week, often more.
I'm starting an initiative to offer subsidized audits through @birdseye_sec for bootstrapped and lightly-funded projects that don't have a huge budget for security.
DM me if you have a project that needs a security review but can't afford to pay market rates. My TG is in my bio.
No contract should be deployed un-audited. Please share with any projects you know that could benefit from this program.
kodyvim retweeted
Another Rare query approved.
@kodyvim_ earned $400 for identifying an NFT rewards claim flow lacking ownership validation.
Query below:
kodyvim retweeted
Building a secure protocol is not that complicated… you just need to:
- Incorporate security from the design
- Discuss and address every edge case
- Build a strong test case
- Get the code audited by strong auditors (preferably multiple times)
- Formally verify your code
- Develop an extra safe frontend
- Build a comprehensive and detailed emergency plan
- Carefully build a deploy script (and ideally get it audited too)
- Set up and manage a bug bounty program (including for the frontend)
- Closely monitor the contracts immediately after launch to ensure the configs are correct and the deployment hasn’t been attacked
- Perform a staged rollout, progressively increasing the limits
- Monitor the chain for suspicious activity
- Monitor every dependency that could break your protocol
- Maintain an external safe failure mode (e.g. pausing guardians)
- Properly manage governance
- Properly manage signer keys
And some other things
kodyvim retweeted
This Rare query was contributed by @kodyvim_ last week.
The finding is around missing access control in the UUPS upgrade flow.
He received $400 for the contribution.
Send kudos to @kodyvim_ in the comments section.
The Glider contest runs until Dec 31, with a $50,000 prize pool.
Query below:
kodyvim retweeted
Welcome back to Sherlock’s Vulnerability Spotlight, where we highlight an impactful vulnerability uncovered during a Sherlock audit.
This week, we have a Multisig Duplication Vulnerability.
It was uncovered by @0xShoonya, @thongtrungtran, @kodyvim_,
@captsparrowjac, @ZanyBonzy, @AmanKakar12, @boredpukar,
@bughuntoor, @shanb1605, @IlloySci, @jasonxiale, @dejiolaniyannn, @Rsam_eth, @hope_silver, @alkarin_, @MissKeishaSheFD and @zxriptor
on the @Mellowprotocol Flexible Vaults Contest 🧵
kodyvim retweeted
Cantina security researchers keep winning!
The Monad Airdrop Claim Portal is live
Claim your MON here: claim.monad.xyz
claim.monad.xyz
kodyvim retweeted
Curiosity, a beginner's mind, the ability to learn quickly and willingness to work hard is more powerful than you think.
These are the traits to thrive in tech today.
kodyvim retweeted
Keep Learning and Growing as a Security Researcher
Always try to improve by reading past exploits, mastering new programming languages, or facing challenges during the audits.
kodyvim retweeted
The right mindset for auditing isn’t about maximizing $$— it’s coverage.
By focusing on uncovering every issue, you’ll feel proud of your work, no matter the outcome.
Forget chasing EV; it can be discouraging when luck isn’t on your side. Focus on predictable goals instead.
kodyvim retweeted
Did you know that you can mark all the files in scope?
📌 Maybe, but it will take you too much time to do it manually.
Here’s how to do it in 5 seconds with 1 simple command!
kodyvim retweeted
Awards have been announced for the $15,000 Moonwell contest🤝
Contest:
🥇 @pontifex73 - $14,000
🥈 @ljjeth - $1,000
Judging:
@pontifex73, @0xInAllHonesty, @ljjeth, @kodyvim_ and IceBear all earned an equal part of the $1500 Judging Pool!
(1/2)
kodyvim retweeted
Few reflections on our @OpusMoney x @code4rena contest now that it's over:
Going into the contest, I felt pretty confident about our code. We spend a lot of time on reviews (design & code), have an extensive test suite, plus just before the contest started we wrapped up an audit with a traditional security firm.
Oh boy, was I in for a surprise.
The wardens revealed 4 highs (two of them really embarrassing that we should've caught 🙈) & 9 mediums. Needless to say, I'm very happy they did; they made Opus better. We've already mitigated all issues found and are working on bringing Opus to mainnet soon🤞
I'm now also a full convert to the open contest way of doing security audits. The ROI is just incredible. C4 is doing an amazing job at amassing talent from all over the world and giving them a venue to apply their skills in a fair way to the benefit of all involved parties. I noticed there are wardens that specialize on certain areas (MEV extraction, financial attacks, mechanism design, etc.) and thanks to C4 you can get them to asses your protocol. There's just no way a traditional firm can offer this level of scrutiny for the same money.
There's also a downside to the open nature of a contest. Anyone can submit, hence anyone does. We got a lot of obvious chatGPT generated submissions, a lot of low quality ones (reporting something when it's "works as designed"), etc. People are just incentivized to fill in everything in hopes of getting a reward. Note I'm not criticizing submissions of low severity issues, I agree with @sockdrawermoney here, there's value in those too. I'm just saying there's a lot of garbage. However C4 is doing a pretty good job at filtering that out during the screening process.
I'd also like to highlight 0xsomeone who was the judge on our contest. That guy is *amazing*. We were super impressed by his ability to grasp complexities of our protocol and navigate between the wardens' submissions and our comments. What a chad!
Finally, this was the first ever Starknet/Cairo contest on C4 so I was also curious how it will go. There was a 3 week bootcamp prior to our audit (thank you @omarespejel @barretodavid @robertkp13) and from what I can tell, it was worthwhile. Sure, there were people who treated it like EVM ("no check of caller address zero" etc.), but the best people understood the platform and tooling and submitted issues with a full PoC built using Cairo & Scarb. Great to see 🙏
So overall I'm very happy with the process and results it bore. I want to once again thank you to all the people involved, it's been a great experience.
🚨 4 High-risk findings
⚠️ 9 Medium-risk findings
💻 28 Wardens participating
The @OpusMoney report is here! Read all about the first Cairo and @Starknet based C4 audit here: code4rena.com/reports/2024-0…
kodyvim retweeted
Whether it's a contest, bug hunting, a firm , or private audit. In the end, you’re contributing to making web3 more secure and safer. Collective efforts bring sustainability.
kodyvim retweeted
We are proud to launch the #ThinkSui program, powered by @thrivecoinHq 🎉
ThinkSui is for the Web3 community, particularly for those who can build NFT collections, dapps or educate others about Sui - with a reward pool of $720,000 in #SUI tokens!
Read below to get started 👇
kodyvim retweeted
If you find a critical vulnerability in code audited by Hexens, we will pay 10K USD on top of your bug bounty.
We put our money where our mouth is.
We invite other audit firms to do the same.
🌀retweets welcomed
kodyvim retweeted
I did 50+ smart contract security audits in a year. Found 300+ bugs. A lot of clients became repeated clients & brought referrals. Now, working with great security researchers from the space, more security services are coming this year.
All reports:
github.com/pashov/audits























