Using Remix? The 1.19 release of Solidity (Wake) VS Code extension eliminates context switching. Write, test, and deploy – all in one workflow. Backed by @Optimism. How does it work? Thread ↓

RT @rektoff_xyz: guest lecture 11. fuzzing strategies with @TridentSolana. w/ @AckeeBlockchain, auditors behind @1inch, @LidoFinance, @Laye….

When READMEs document security considerations, the portfolio becomes a genuine asset. Juniors see features; professionals see attack vectors. And employers can tell the difference.

Pro tips for building in public:.• Use environment variables from day one.• Never commit sensitive data (even in history).• Add security disclaimers to learning repos.• Audit your own code before showcasing.

A developer's GitHub is their resume. But those learning projects? They're also a hacker's goldmine. Hardcoded keys, test wallets, vulnerable patterns – it's all there.

RT @WakeFramework: Your smart contract deployment just failed. Cost: $50K in gas fees. An attacker saw your transaction, calculated the ex….

4/ Get the latest version of @WakeFramework and try the newest printer with:. wake print contract-size. Read the changelog for the full details on Wake 4.20.

3/ Advanced filtering and analysis:. → Sort by runtime size, creation size, name, or file.→ Filter specific contracts with --name.→ Include libraries/interfaces with --all.→ Show full paths with --details. One command. Complete visibility.

2/ Visual clarity built in:. Simple visual indicators show if contract is under or over size limit. Clean table format shows:.• Contract names and types.• Runtime & creation sizes.• Percentage of limits used.• Summary of violations.

1/ Why this matters:. The EVM enforces strict size limits. → Runtime: 24,576 bytes (Spurious Dragon).→ Creation: 49,152 bytes (Shanghai). Exceeding these leads to a deployment failure. Wake users know exactly where they stand.

We've just released v4.20 of @WakeFramework with a powerful new contract size printer. Devs can now see contract bytecode sizes vs EVM limits at a glance, and whether the contract is hitting the 24,576 size limit before deployment. Thread ↓

RT @wattprotocol: We have lift off for @Solana's first universal liquid staking account. No more idle tokens. Only energized assets. @wa….

Happy 10th birthday, @ethereum!. Stay safe.

Read our full analysis and reproduction of the GMX hack to prevent this in your project:.

Pro tip: Map your protocol's state dependencies. If updating State A requires State B to be in sync, you have a potential vulnerability. The most dangerous bugs emerge from the gaps between your contracts, not within them.

The lesson? Security isn't additive – you can't just stack protections and assume safety. A holistic approach means understanding how your contracts interact as a system, not just securing them individually.

Complex protocols split responsibilities across multiple contracts for modularity. But when critical state (like price calculations) depends on synchronized updates across contracts, you've created a race condition waiting to be exploited.

Your reentrancy guards aren't enough when state is fragmented across contracts. The $42M @GMX_IO exploit taught us that traditional security measures fail when architectural decisions create hidden attack surfaces.

RT @ArbitrumDevs: These firms will play a key role in ensuring the security of builders and users in the Arbitrum ecosystem. Shoutout to t….

The developers who land the best opportunities are security-conscious from day one. Start building that muscle now. Your future self and users will thank you.

Every line of code you write today shapes your security instincts tomorrow. Start asking "how could this break?" with every function, every state change, every external call. Fuzz your code to find edge cases you can't think up.