fuzz755

@mamoud___ Faudrait que je commence je me fais peut être une fausse impression

@fuzz755 La syntaxe elle est ok je trouve je trouve pas du tout repoussant

Jme sens trop heureux ajd j'aime pas trop ca. Jvais ecrire quelque ligne de rust et laisser le compilateur me crier dessus parce que chui un bon a rien ca me remettra les idées en place tiens

@mamoud___ T’es chaud, j’aimerais bien m’y mettre mais ça donne pas envie quand je vois la syntaxe sans comprendre

@fuzz755 Boff pas trop

@mamoud___ T’en fais depuis longtemps ?

@fuzz755 Rien de bien special j'ai pas de besoin actuel qui requiert du Rust. Mais vue que j'aime beaucoup le langage jme fais des ptits challenges neetcode quand jme fais chier ( 100% usless mais ca me fait passer mon ennui)

Y’a des sénégalais qui peuvent me dire s’ils connaissent cette école ? itd-hub.com J’arrive pas à savoir si c’est une vraie ou un faux site

@CodeHawks @ZhivkoNiko40281 how long for judging please?

Announcing First Flight #58: NFT Dealers! Thank you to @ZhivkoNiko40281 for this submission and their commitment to Web3 Security 🙏 nSLOC: 253 Start date: March 12, 2026 Noon UTC Duration: 1 Week Get real auditing experience! Check it out! 👇 (1/2)

wtf is my problem i was 16

my oldest transaction on Ethereum... 🥲

just in case… obviously

I Saved Injective's $500M. They Pay Me $50K. I like hunting bugs on @immunefi . I'm decent at it. - #1 — Attackathon | Stacks - #2 — Attackathon | Stacks II - #1 — Attackathon | XRPL Lending Protocol - 1 Critical and 1 High from bug bounties (not counting this one) Life was good. Then I found a Critical vulnerability in @injective . This vulnerability allowed any user to directly drain any account on the chain. No special permissions needed. Over $500M in on-chain assets were at risk. I reported it through Immunefi. The next day, a mainnet upgrade to fix the bug went to governance vote. The Injective team clearly understood the severity. Then — silence. For 3 months. No follow up. No technical discussion. Nothing. A few days ago, they notified me of their decision: $50K. The maximum payout for a Critical vulnerability in their bug bounty program is $500K. I disputed it. Silence again. No explanation for the reduced payout. No explanation for the 3 month ghost. No conversation at all. To be clear: the $50K has not been paid either. I've seen others share bad experiences with bug bounty payouts recently. I never thought it would happen to me. I can't force them to do the right thing. But I won't let this be forgotten. I will dedicate 10% of all my future bug bounty earnings to making sure this story stays visible — until Injective pays what I deserve. Full Technical Report: github.com/injective-wall…

@CodeHawks @ZhivkoNiko40281 can't download my submissions, the md file is broken :(

@PatrickAlphaC will definitely not let a LLM manage my keys

1. Get a shitty intel NUC 2. 2TB SSD 3. Let LLM follow docs 4. Profit

@pashov Too early

@fuzz755 Why do you think some tools are not positioning to be part of CI/CD at this stage

How much do you think an AI audit scan should cost? Only honest answers, comment below.

@0xsadikbaba It will never overflow it’s EVM. There is not enough ETH in the world to make it overflow

Two major issues in this contract Unchecked deposit can overflow The deposit function uses unchecked when increasing the user balance. This removes Soliditys overflow protection and could cause the balance to wrap if extreme values are used. Broken balance logic the increaseBalance function lets anyone increase their balance without sending ETH. This means a user can artificially inflate their balance in the contract state without actually depositing funds. Contract accounting becomes unreliable Users can create fake balances The system’s business logic breaks Always ensure balance updates are tied to real value transfers and avoid unnecessary unchecked blocks.

Mettre un repo en privé par peur de se le faire voler… Un bon entrepreneur doit rêver de se faire voler son projet

my first submission for NFT Dealers on @CodeHawks

@pashov Of course, it should be part of CI/CD

@fuzz755 True. Would you do it always before pushing to repo sir?

@pashov It’s a bit awkward if an auditor has to scan code with AI, any protocol’s dev should be able to do it before pushing the code to the repo

@fuzz755 Are you okay with doing these "scans" yourself?

@pashov I only considered API costs, but they may be additional costs for service/servers/…

@fuzz755 Why not $0?