𝗕𝘂𝗴 🐛 𝗶𝗻 𝗰𝗼𝗱𝗲 𝗯𝘂𝘁 𝘁𝗲𝘀𝘁 𝗽𝗮𝘀𝘀𝗲𝘀 𝗮𝗻𝘆𝘄𝗮𝘆?🤔 Well, most devs use Mock contracts in tests which btw have no/simplified logic that simply "returns" upon invocation. 👉 That test is passing 'cause you ain't actually invoking the buggy function😎

To you who's wondering how this applies, take this example:👇👇 𝗣𝗮𝗿𝘁𝗶𝗮𝗹 𝘃𝘀 𝗙𝘂𝗹𝗹 𝗹𝗶𝗾𝘂𝗶𝗱𝗮𝘁𝗶𝗼𝗻🧐 Multiple partial liquidations on a position do not yield same outcome as one full liquidation on the said position (in some cases).

Most aren't ready for this but😂: 𝗔 𝗿𝘂𝗻𝗻𝗶𝗻𝗴 𝗣𝗼𝗖 𝗱𝗼𝗲𝘀𝗻'𝘁 𝗺𝗲𝗮𝗻 𝗶𝘁 𝗶𝘀 𝗮 𝗯𝘂𝗴!

Managed to squeeze myself in here between some privates and well... We move 😎

#Vigilseek by L M sure makes it all cool. Even though much hasn't been integrated yet, I find it super great. 😎

Felt great auditing this one with Pashov Audit Group. (#cairo lang) . We move😎

"𝙏𝙝𝙚𝙧𝙚 𝙞𝙨 𝙣𝙤 𝙬𝙖𝙮 𝙩𝙤 𝙚𝙭𝙥𝙡𝙤𝙞𝙩 𝙩𝙝𝙞𝙨" is now a valid crit. Someone just thought longer. 🤢

We move😎

Tying bounties for the first time and I swear... 😩😩

This is an unsolicited candid advice for y’all diving into bug bounty: Don’t go on wide goose chase. Just focus on a single contract class. Like Perpetuals Consensus (DLT) bridging Anything specific Increases your odds of finding a bug Gives you experience in that niche

Yeay, My report has been triaged as a valid submission on HackenProof 😎 hackenproof.com #hackenproofed #bugbounty

They lied to you. Bug hunting is really hard.

That bug might not mean much if it's impact is not in scope🧑‍🦯

My brain every time I meet such: “I'm sure this works as intended”😭😭

A win is a win. We move😎

We move😎

When you finally see that bug 🪲that payed someone 5x your payout and now you feel dumb cause htf did you not spot that?😭😭

How ready are you for your first audit? Getting audited is a big milestone and preparing right makes all the difference. Join us by 3PM UTC today as we discuss what every builder should know before their first audit, from smart pre-audit habits to simple steps that save time and

When you can't escalate but you know damn well the judge didn't run the test💀