ctrus

Really thankful for the opportunity @DevDacian. I enjoy auditing with @jesjupyter always, this time @auditor_nate joined us & it was really unreal experience. Dacian’s solace already flagged 54 findings on 2nd day of audit, it was overwhelming.. from 3rd day onwards @auditor_nate kept bombing chat with his tool’s findings. He has built an amazing tool too, gotta admit. @jesjupyter and I were manual, it took us around 8/9 days to understand the codebase… the fomo was so bad.. I mean there are already ~70ish findings(POTENTIAL) uncovered and its still 4th day of audit and youre just starting to get an idea.. It was a ~5500 nsloc codebase, we worked on weekends too because we simply couldnt afford to loose right.. slowly from there we started landing leads and validating Nate’s findings.. by the end of the audit we had 106 findings!!! One thing for sure I learned from this audit and it hit me real bad.. I simply cant keep working complete manual, its just not sustainable anymore, This might be my last audit as manual auditor, can’t believe it took me so long to understand where we are headed and I still ignored it given that the only reason I chose solana/rust back then was because of game theory and thats where the supply was low and demand was increasing fay by day in Q3 2024… I would see seniors posting niches were gonna be the new meta like sui+move, sui+aptos, rust+solana and I followed it simply and it worked. Now that it seems like manual + personal tools/agents are new meta and still sleeping on it is simply chopping tree with an axe when I have chainsaw available(I just need to lean how to use it) and everyone around me is using chainsaw..

Really thankful for the opportunity, I enjoyed the collaboration, amazing SRs. looking forward for more. I wish the team very best💅

July went well, completed 2 private audits with 5C,2H,4M,10L bugs uncovered, not really the best ev, but not so long ago, no firms even replied, thankful to those who gave me a chance, I'm grateful that I'm occupied with solana/rust work.... Portfolio 👇 github.com/ctrusonchain

@n1kh11L Only up

Bugs found: 7 5H 2M Payout: $345 Not the results I wanted, but enough to keep me going and motivated

@predictandpump @proxima424 @0xnirlin @amarfares_ thanks for referring me, again!

I concluded a private audit for @predictandpump last week — found 6 high/medium severity bugs. It was great working with @proxima424 and @0xnirlin. Wishing them the best for their protocol 🚀 📄 Audit report: github.com/ctrusonchain/c…

@Abhi_r812 Checked

Founded @arjuna_sec with a friend, focusing on Rust/Solana audits. Balancing uni + audits, planning to drop out soon. Just need 5 more contest results to back myself up! Waiting for the next solana/rust contest now! All the countless hours will start to make sense soon..🙏

@Abhi_r812 Opened

@ctrusonchain Bro your dm is closed

@Ajay___zay Sure

@ctrusonchain Can u dm me?

@shaflow01 @soon_svm @cantinaxyz Congratulations shaflow!

Participated in @soon_svm contest in @cantinaxyz. Thanks for this opportunity Found 2H/1M and got good payouts. I have written POC for each report. Learning from this contest: When there is a mixed language codebase, do not underestimate either party.

@joeljanx What happened to your yt channel

@cmichelio @J4X_Security Relatable

@J4X_Security whenever I read reports I first read the recommendation. For some reason, people are bad at explaining the issue in the description and by just looking at the recommended fix I understand the issue much faster.

I just realized that I subconsciously developed a small, helpful auditing technique over the last few months. I thought I should share it, as it might benefit some of you just getting into the field. Whenever I write an issue, I always start with the recommended mitigation. It seems counterintuitive at first, but the idea is that if I find a mitigation, it makes writing the issue easier. It's usually not worth reporting if I don't, as there is no way to fix it. So, it either makes writing the main part of the issue easier or saves you time, as you don't have to write anything at all.

@amarfares_ @armormadeofwoe Congratulations cats📈

teammate @armormadeofwoe went in for knee surgery and we still got 3rd if he gets another one done during the next contest, we might just take 1st lol

@HollaWaldfee100 I learned alot from them, used to stalk your account alot, the best one was 'if you know what's underflow, go look for it in code' no need to follow bottom up approach

@ctrusonchain Haha thanks, you know at some point I ran out of ideas and then it became harder to post and I stopped

Now that we have reached 100k, it's time to make a comeback. More bearish takes than ever before🔥

@0xT1MOH 3 months of pure learning: language, ecosystem, blogs, articles, past reports , failed jito and tensor miserably, 4th month: hoping for good results from 3 contests I participated in this "4th" month.

This aged well btw. What did your journey look like anon?

@0xT1MOH Congratulations mman

85 pomodoros. 10 days research. 6500 nSLoC. 5 days writing reports. 17 PoC. 0 invalids. 1st place. 100 points. LFG!

🚀 January Recap: - Audited 3 Rust projects: 1. Soon SVM on Cantina (10 days) 2. PumpdotScience on CodeRena (2 days, 3 bugs submitted) 3. Inclusive Finance on Cantina (bridge programs, 20 bugs submitted) Hoping for good results 🛐 #Rust #Solana #solsec #Audit