JohnnyTime 🤓🔥

9.8K posts

JohnnyTime 🤓🔥 banner
JohnnyTime 🤓🔥

JohnnyTime 🤓🔥

@RealJohnnyTime

Founder @ https://t.co/gcgrMm4Njh, JohnnyTime @ Youtube, Securing Web3 @ https://t.co/wJdpJyYcg0 & https://t.co/3d9aL8n5G8

Web3 Sumali Şubat 2012
1.4K Sinusundan12.6K Mga Tagasunod
Naka-pin na Tweet
JohnnyTime 🤓🔥
JohnnyTime 🤓🔥@RealJohnnyTime·
Smart contract security pays WELL. 💰 Top auditors make $500K+ per year 💰 Bug bounties can 10x that 💰 Even “mid” auditors make six figures BUT… Only if you actually put in the work. No shortcuts here.
English
14
26
316
26.1K
JohnnyTime 🤓🔥
JohnnyTime 🤓🔥@RealJohnnyTime·
Most losses don’t come from “genius” bugs. They come from boring mistakes: - missing checks - wrong units - unbounded loops - unguarded oracle assumptions Boring bugs still bankrupt protocols.
English
1
1
7
268
JohnnyTime 🤓🔥
JohnnyTime 🤓🔥@RealJohnnyTime·
The scariest part about delegatecall? It preserves msg.sender and msg.value. The victim thinks they're interacting with YOU. But you're running malicious code in THEIR context. It's identity theft for smart contracts. smartcontractshacking.com/attacks/call-a…
English
2
0
11
360
JohnnyTime 🤓🔥
JohnnyTime 🤓🔥@RealJohnnyTime·
How to steal millions in 4 steps: 1. Flash borrow 100k ETH 2. Dump on a DEX to crash price 3. Exploit a protocol reading that price 4. Repay loan, keep profit If step 3 fails, the loan never happened. Zero risk. smartcontractshacking.com/attacks/flash-…
English
4
4
49
2.7K
JohnnyTime 🤓🔥
JohnnyTime 🤓🔥@RealJohnnyTime·
“Most expensive hacks” shouldn’t be consumed as shock content. Use it as prioritization data. During an audit, your real job is attention allocation: - where losses cluster - which assumptions fail repeatedly - what attack paths carry the highest downside
English
1
1
12
420
JohnnyTime 🤓🔥
JohnnyTime 🤓🔥@RealJohnnyTime·
If your goal is to get sharp at exploits, stop sampling 20 techniques at once. Pick one technique. Study 10 incidents. Extract the repeated broken assumption. Pattern recognition beats trivia every time.
English
5
2
33
1.1K
JohnnyTime 🤓🔥
JohnnyTime 🤓🔥@RealJohnnyTime·
Weekend Challenge #8: What issue would you submit if you saw this in an auditing context, Mr. Hacker?
JohnnyTime 🤓🔥 tweet media
English
6
3
35
2.1K
JohnnyTime 🤓🔥
JohnnyTime 🤓🔥@RealJohnnyTime·
A safer workflow: - Use AI for enumeration: surfaces, threat ideas, edge-case prompts - Use humans for verification: invariants, exploitability, impact - Require evidence for every claim: code path + state transition + attacker capability
English
1
0
2
273
JohnnyTime 🤓🔥
JohnnyTime 🤓🔥@RealJohnnyTime·
AI can make auditors faster. It can also make them confidently wrong.
English
8
2
24
1.5K
JohnnyTime 🤓🔥
JohnnyTime 🤓🔥@RealJohnnyTime·
“Just run Slither” is becoming the new “just audit harder.” Use tools. Absolutely. But the biggest misses still come from: - invalid assumptions - missing invariants - dangerous integrations Scanners find patterns. Auditors find broken logic.
English
1
2
12
804
JohnnyTime 🤓🔥
JohnnyTime 🤓🔥@RealJohnnyTime·
28 AI audit skill files. 9 repositories. 28 scanned safe. 0 you have to pay for. The AI Skills Explorer is live and free.
English
0
1
13
1.3K
JohnnyTime 🤓🔥
JohnnyTime 🤓🔥@RealJohnnyTime·
The hard truth: You don’t become audit-ready by consuming more content. You become audit-ready with a repeatable system: - threat model first - invariants second - exploit paths third - mitigations with tradeoffs last
English
3
1
15
1K