🚨Solidity Devs - this awesome repository has 50 agents, 91 skills and 19 hooks for Solidity development, deployment, testing and security Built & compiled by a Uniswap Senior Engineer. Use this for higher quality development, MIT license🫡 github.com/ccashwell/evm-cor…

Math is solved.

1,100+ runnable EVM exploits — live on crypto.training We’ve crossed 1,100 fully runnable exploit PoCs on crypto.training/hacks. That’s not a list of write-ups or a folder of Solidity files that might compile. Each one is a self-contained, offline-reproducible Foundry PoC you can open in the browser and actually execute — historical DeFi hacks and high-severity audit findings reduced to faithful synthetics. I believe this is the largest public collection of runnable EVM exploits in the world. If you learn security by reading blogs, you get the story. If you step the bytecode, you get the mechanism. What makes the playground different Every hack page can load an in-browser EVM (no backend, no fork server required for the interactive path). The killer features: ✅ Opcode-by-opcode debugging — step, reverse-step, and jump through the real execution trace of the exploit, not a simplified animation ✅ Full EVM state at every step — stack, memory, storage, call depth, and program counter, in sync with the opcode you’re on ✅ Balances panel — watch native currency, ERC-20, ERC-721, and ERC-1155 update as money moves: who was paid, who was drained, at which step ✅ “Go to vulnerability” — jump straight to the blamed source line in the vulnerable contract (real @> lines preserved for audit findings) ✅ “Watch exploit live” — story beats that walk setup → trigger → harm, each tied to executed lines in the trace ✅ Labeled call tree — see contracts by name, not only bare addresses ✅ Same PoC offline — download the analyzer ZIP / registry package and run forge test with no network when you want the Foundry path What’s in the corpus ➡ Hundreds of historical DeFi incidents (the classic SunSec / DeFiHackLabs lineage and beyond) ➡ Hundreds of audit findings from AuditVault / contest reports — reduced to local-deploy synthetics that still demonstrate real harm ➡ One pipeline end-to-end: registry PoC → playground config → verified recording → page → analyzer ZIP Why this matters for auditors and builders ✅ Train on mechanisms, not just CVE titles ✅ Compare how the same bug class shows up across protocols ✅ Teach juniors with a debugger instead of a wall of prose ✅ Re-run and modify PoCs locally when you want to go deeper Open any page on crypto.training/hacks, hit the playground, and step the exploit yourself. Open source tooling: github.com/sanbir/evm-hack-a… Feedback, corrections, and new PoCs welcome. #Web3Security #SmartContractAudit #DeFi #Ethereum #EVM #SecurityResearch #OpenSource #Solidity #BugBounty

Earlier today we identified suspicious cross-chain activity involving rsETH. We have paused rsETH contracts across mainnet and several L2s while we investigate. We are working with @LayerZero_Core, @unichain, our auditors and top security experts on RCA. We will keep you posted as we learn more about this situation. Please follow only the official @KelpDAO handle for the updates.

#CertiKInsight 🚨 On 8 January 2026, @Truebitprotocol was exploited due to an overflow issue, resulting in a loss of ~$26.6M. To learn more about what happened, read our full analysis here 👇 certik.com/resources/blog/tr…