Wake
@WakeFramework
Wake is a Python-based fuzzing and testing framework for Solidity. It helps you write safer smart contracts for @Ethereum dApps, faster. by @AckeeBlockchain
The EVM/Solidity Security Checklist is based on 200+ successful audits securing $180+ Bn in TVL. We now give it away for FREE (limited time only) to help devs and security researchers level up. To get it: ✓ Repost ✓ Comment: LIST We'll DM it to you (must be following).
Most developers write unit tests. Smart developers write fuzz tests. The difference? One checks a single case. The other explores thousands of scenarios you'd never think to test manually. Unit test: Transfer 1,000 tokens Alice to Bob. Pass or fail. Fuzz test: Transfer…
Unit test vs Fuzz test: • Unit: Transfer 1,000 tokens Alice → Bob • Fuzz: Transfer random amount (0-10,000) between random accounts Same assertion, thousands of scenarios instead of one case. Catch edge cases you'd never think to test ↓
Generic analysis tools scan everything. Slow. Noisy. Overwhelming output. Wake printers accept CLI arguments. Filter by contract name, inheritance depth, modifiers, libraries, external calls. Whatever you need for targeted analysis. Same tool. Different contexts. Fast…
Generic analysis tools are slow. You need to focus on specific contracts. Wake printers accept command-line arguments, enabling targeted analysis that adapts to your workflow. Here's how to add filtering to any printer: Thread ↓
One transaction. Permanent lockout. No recovery possible. This is what happens when guard removal detection fails in multi-sig systems. The Safe console becomes completely unusable. Every transaction reverts. The guard can't be disabled. Lcked out forever. The technical flaw?…
Perfect security setup. Multi-sig console protected by custom policy guard. Then one transaction locks the account forever. No recovery. No bypass. Wake's fuzz testing caught this before production: Thread ↓
A single wei rounding in the wrong direction cost Balancer $100M across nine chains. The vulnerability existed for years. Trail of Bits flagged similar rounding problems back in 2021. But the audit team couldn't definitively prove it was exploitable at the time. Marked…
The fuzzing evolution @jgattermayer describes is why we built Wake the way we did. Blackbox fuzzing finds the obvious bugs. Auditor-guided fuzzing finds the protocol-breaking edge cases that cost millions. The shift from "test everything randomly" to "target specific attack…
Just presented "State of Fuzzing: Closing the Circle From Machine to Human and Back" at DeFi Security Summit. The evolution of smart contract testing → from blackbox automation to auditor-guided fuzzing to AI-assisted workflows. Thread ↓
"$50,000 lost in a smart contract hack." This line hits different when you build security tools for a living. Every vulnerability we catch in Wake represents someone who won't have to endure this. Every graph-driven analysis that flags a reentrancy bug is someone who keeps…
Life has humbled me multiple times. - Nearly died at age 20. - Got scammed for 25k at 23. - Made money in crypto then lost it all. - Lost 50k in a smart contract hack. - Became a father (probably one of the most humbling and empathy expanding experiences you can have) We are…
Restricting self-destruction to creation transactions eliminates an entire class of attack vectors. But here's what most builders miss... On-chain data shows "minimal usage beyond create-then-destroy" because developers don't realize they're using dangerous patterns. This is…
𝗧𝗥𝗢𝗡 𝗣𝗿𝗼𝗽𝗼𝘀𝗲𝘀 𝗧𝗜𝗣-𝟲𝟳𝟴𝟬 𝘁𝗼 𝗨𝗽𝗴𝗿𝗮𝗱𝗲 𝗦𝗘𝗟𝗙𝗗𝗘𝗦𝗧𝗥𝗨𝗖𝗧 𝗳𝗼𝗿 𝘁𝗵𝗲 𝗙𝘂𝘁𝘂𝗿𝗲 TRON is rolling out TIP-6780, a major update that reshapes how the SELFDESTRUCT opcode behaves, and brings TRON fully in line with Ethereum’s EIP-6780. If you’re…
Autonomous contracts monitoring events across chains are powerful. They're also dangerous. The more intelligent your contracts become, the more attack vectors you create. Cross-chain triggers mean cross-chain vulnerabilities. Event-driven logic hides edge cases that manual…
Reactive Contracts (RCs) RCs redefine existing transaction flow by autonomously monitoring blockchain events & executing actions without direct input. Built on EVM, they use custom ABIs for solidity & leverage reactive nodes to create trustless transactions. Key features: ✅…
Shocking news warning! Some developers still write Solidity without real-time vulnerability detection. Wake's VS Code extension catches issues on every keystroke: • Access control flaws • Reentrancy patterns • Style violations • Logic errors Here it is ↓
United States Trends
- 1. #BaddiesUSA 31.3K posts
- 2. Rams 23.6K posts
- 3. Cowboys 91.6K posts
- 4. Eagles 130K posts
- 5. Stafford 10.5K posts
- 6. Bucs 10.5K posts
- 7. Baker 18.8K posts
- 8. Scotty 7,261 posts
- 9. #RHOP 8,476 posts
- 10. Raiders 58K posts
- 11. Stacey 29.5K posts
- 12. Todd Bowles 1,369 posts
- 13. Pickens 29.1K posts
- 14. Teddy Bridgewater N/A
- 15. #ITWelcomeToDerry 8,916 posts
- 16. Browns 104K posts
- 17. Shedeur 118K posts
- 18. Nimmo 19.3K posts
- 19. Davante Adams 2,331 posts
- 20. Chip Kelly 3,784 posts
Something went wrong.
Something went wrong.