is it just me or it seems like every protocol i look at these days must be built with --via-ir

Honored and excited to be elected to the @OptimismGov Developer Advisory Board for Seasons 8 and 9! 🙏🎉 Congrats to the homies @odysseas_eth @optimizoor @m4rio_eth - welcome! It will be fun to work with you in a new context alongside @wildmolasses @wbnns & @blockdeveth 🦾

Hear me out Micro strategy but for anthropic credits

this was created by my friend, a veteran filmmaker and genuinely one of the most talented creatives i know the account is new and still fighting the algo, so give a follow to help the cause 👉 @Round_AI_Media 👈 🔥 "Promptin' ain't easy" iykyk! 🤣

'Promptin' Ain't Easy' MV

🤝 Clients don't love to hear it but it absolutely needs to be said. It's literally the single most clear indicator. Sometimes I present it like "We've been finding significant bugs every day this week, what are the chances we coincidentally found the last bug on the last day of the review? What do you think the likelihood is we would find more if we kept going?" Such a waste to stop at that point too, SR's are in the zone and who better to keep digging than the team that's been staring at your code the last 3 weeks. Ideally we could enter flexible arrangements (stop soon if we finish early, keep going if we're finding a lot) but it's not that simple since not only would that require flexibility from busy SR's but also creates weird incentives to extend the review. It is possible if you build trust w the client.

NEW TRON: ARES TRAILER OUT NOW!

> Going to pick a >1M bounty on @immunefi > Pay for this audit (delayed payment ofc because I don't have 500k or anything close to it) > Find all criticals, report for bounty > Get bounty, pay for audit, keep the rest > Infinite money glitch Follow me for more alpha 🤓

A few weeks ago, I was responding to a cybersecurity incident - $500,000 have been stolen from a #blockchain developer. The infected operating system was freshly installed, and the victim was vigilant about cybersecurity. How could this happen? New supply chain attack? [1/6]

The extension that was impersonating vscode solidity (and many others following the same pattern) have been removed. We have seen that a fake extension or virus can spam many downloads (if that was their technique). So how to identify is the right extension? The best way is to look at the published date. The vscode solidity extension was published on the 2015-11-19 at 7:35 am, the published date cannot be faked. The extension was one of the first ones in the marketplace, after the official announcement of the extension sdk the day before. So in case of doubt, when choosing any extension.. check the date. @ethereum @code