kkk

[kkk @komronjaan]

@TamayoNft Thank you, great guide!

[kkk @komronjaan]

Yesterday reported a bug on immunefi with Low severity, wanted to get my first payout. Later, team duplicated my report and closed. What matters that, dup report was critical. First bb critical, next one will be confirmed, inshallah

[kkk @komronjaan]

@KannAudits Applied!

[kkk @komronjaan]

@Al_Qa_qa Should return Sig_validation_failed, should not revert ?

[kkk @komronjaan]

@z0r0zzz thanks for an article, very informative. I guess correct prompt for the skill is very important. We need to analyse what prompts make AI work more efficient.

[kkk @komronjaan]

What is meaning of in-scope and OOS in bug bounty. if you find bug and its critical it should be paid the same amount as in-scope.

In both conditions blackhat can drain funds. I see in some posts whitehats telling "it was OOS but the protocol decided to pay some amount".

[kkk @komronjaan]

No more contests.

Its funny how judge invalidates bug by commenting “intentional design” where dozens of auditors showing PoC of contract drainage.

Not the first time.

[kkk @komronjaan]

@arsen_bt Defendor

[kkk @komronjaan]

Yesterday I was reflecting on expectations—how they shape our lives and what happens when we stop expecting anything at all.

When starting something new, we often imagine golden rewards and instant success. But over time, reality hits: every path is hard, every profession has its struggle, and being the best is far more difficult than it first seemed.

Take a student, for example. If he expects to be a great doctor by 30, he may feel disappointed if he falls short. But if he sets no rigid expectations, any progress by 30 will feel like an achievement. The same applies in smart contract auditing. Many newcomers, myself included, dream of private audits and high payouts. After a few contests with no findings—or common bugs already discovered by others—it can feel disheartening. The job is simply not as easy as it first appeared.

Unrealistic expectations often lead to stress, anxiety, and depression. I’m not saying you shouldn’t have goals or make plans. But expecting something grand from the start can harm your motivation. Instead, just keep moving forward—without expecting brilliance. One day, you’ll look back and realize how far you’ve come.

Positive thinking can shape outcomes. Here’s a video I found useful on how expectations influence our behavior: https://t.co/3X8TnFSTyN

Without expectations, even small wins bring happiness. Here are some quotes that stood out to me:

“Blessed is he who expects nothing, for he shall never be disappointed.” – Alexander Pope
“Expectation is the root of all heartache.” – William Shakespeare
“High achievement always takes place in the framework of high expectation.” – Charles Kettering
“Don’t expect things to happen. It’s better to be surprised than disappointed.” – Anonymous

Clear your mind, focus on the path, not the result. Use curiosity instead of assumptions.

But there’s something I still wonder: how do we truly let go of expectations? How do we stop thinking about the destination and learn to stay present in the flow?

[kkk @komronjaan]

@Cartwheel_Joe @immunefi One hoodie for me please

[kkk @komronjaan]

@sin1st3r__ Mashallah brother, more wins to come

[kkk @komronjaan]

@RaOne_0xDev @code4rena @SiloFinance Missed a few, but learned a lot

[kkk @komronjaan]

For me seeing the whole “picture” of the protocol during audit is very important.

I ask myself many questions about code. What is the logic of the project?
How does project earn money?
How does user benefit of using the project?
How do fees are managed?
What external integrations do in project?

After answering all the questions ai start an audit.

Without knowing main idea you can never find incorrect implementation.

[kkk @komronjaan]

@namx05 Did you add codehawks first flight eggstravaganza to your platform?

[kkk @komronjaan]

New day
New contest

Gotta learn something new, research, read reports, find bugs.

What a beautiful day to continue auditing.

[kkk @komronjaan]

Started experimenting to enhance focus

I noticed that at most I am spending 5-6 hours of deep focus during contests. As I researched and found that this range is average which is ok, 2 to 3 hours per day is not enough obviously. After 6 hours of focus my brain cannot accept more information. I tried so hard but sometimes I don’t even understand very simple sentence or a line of code.

I decided to divide my day into several parts, at first i was auditing from late morning till 5-6 pm nonstop, later in order to increase efficiency i added workouts before lunch which made 2 sessions of auditing, before and after workout. Great but still getting tired after 6 hours. Only quality of focus increased but time is the same.

Lets do math of focus per month. I usually don’t rest if there are ongoing contests. 30 days * 6 hours = 180 hours/month, 7.5 days of auditing.

Then I started searching for solutions, the result is using creatine everyday (for now 5g of monohydrate). Using creatine will help me (I hope) with endurance during training and give more efficiency to my “intellectual battles”.

if I can increase deep focus from 6 hours to 9, then per month it will be - 270 hours. Extra 90 hours or 3.75 days of auditing. Total of 11.25 days of full auditing. Which means extra half week of short contest. Planning to do this for several months. Lets see the result.

[kkk @komronjaan]

@DevDacian

[kkk @komronjaan]

By the end of the year should have 50 Highs & 50 Mediums found in contests.