From @ethereumfndn's Solidity compiler team to protocol engineering at @monad, @mijovic988 has spent years deep in the systems developers depend on. At Devcon 8, he’ll explore what changes when AI writes the code and verification becomes the real source of trust. 🤖

Think you can read Solidity well enough to break it? The BuidlGuidl CTF. A set of Ethereum challenges where you exploit contracts to capture the flags. Each one teaches a real vulnerability class by making you find it yourself.

🚨 Beware of Solidity Pro: A Targeted Poisoning Attack on #Web3# Developers SlowMist Security Team has identified malicious activity in Solidity Pro, a #VSCode# extension targeting #Solidity#/Web3 developers. Historical versions under two publisher identities, helper-beeps and web3devtoolsx, were found to contain credential harvesting, remote payload execution, and remote VSIX update capabilities. Interestingly, these malicious capabilities disappeared from subsequent versions, while malicious source code and traces of the previous publisher remained in the repository. We traced the version history, publisher migration, and build artifacts, highlighting a key detection blind spot: Current-version-only detection may cause extensions with a malicious history to appear clean or low-risk again. This case highlights why #ExtensionSecurity# should go beyond a single file or version, incorporating version history, publisher changes, build provenance, and remote control planes. Read the full analysis 👇

“Europe’s solidity depends more than ever on speed and delivery,” argues the departing head of the Banque de France in a guest essay. The bloc is “robust, but not agile enough”, he warns

What should be the KPI every solidity compiler team should track that app builders care about? My shortlist: 1. Compile times speed vs solc 2. Solves stack too deep 3. Bytecode size vs solc 4. Security (bit vague) Btw have you tried out any of the new compilers? ---- The compilers: Solc The one we all use. Solc --via-ir ✅ production ready 😀 solves stack too deep ☹️ compile times 10x slow - so almost no one uses it Solc --experimental SSA-CFG ⚙️ experimental mode 😀 solves stack too deep Compile times and bytecode size - TBD. ❗️looking for people to try it out! solx 🛠️ building. By @NomicFoundation + @the_matter_labs 😀 solves stack too deep 😀 decent compile times + bytecode size! ❗️looking for people to try it out! solar 🛠️ building. By @paradigm Too early to tell but fast compile times and stack too deep problem is promised to be solved!

Bring your own agent 🤖 We're running the Human + AI Solidity CTF at Devcon 8. You and your agent get one hour to capture 12 flags. 🗓 Nov 3 · 3:15 PM IST · Workshop 1 room 🏆 $1K+ in prizes, thanks to @aztecnetwork. Want to add to the pool? DMs open