Getting increasingly bullish on just vibe-coding the important things in Lean. eg. see: github.com/Verified-zkEVM/Ar… blog.zksecurity.xyz/posts/en…

Assumptions Kill Systems. Bluethroat Labs is now live. bluethroatlabs.com

✨Introducing evmresearch✨✨ A knowledge graph of nearly everything I've learned about the EVM in the past six years The graph structure emulates the brain, exponentiating research speeds for both humans and agents evmresearch.io/

built a HyperEVM testnet explorer in light of purrsec's deprecation - hyperscan.sh/ any feedback/suggestions welcome! 🫡

1/ Side-channel attacks: when isolation isn't enough We've covered TrustZone, SGX, and SEV—all provide strong hardware isolation to protect secrets. But there's a catch: even when an attacker can't directly read your data, they can sometimes infer it by watching how the hardware behaves. Welcome to the world of side-channel attacks—the art of learning secrets without breaking the locks.

1/ Before jumping into vendor specifics, remember: a TEE isn't a strict blueprint—it's more like a set of guidelines. The Confidential Computing Consortium (CCC) lays out key security must-haves, without dictating the exact tech to get there. Any TEE solution needs to deliver these basics to earn the label.

Please. If you're building TEE protocols, DO NOT discount microarchitectural side-channel exploits. If your protocol grows to a point where it becomes viable to exploit, you HAVE to assume sophisticated attackers going after you. Do not ignore the bare-minimums. No early returns No trad string comparisons No data-dependent cache access patterns No conditional branching (on sensitive data) No time-dependent code No access patterns reveal (cache hit vs miss timings) No non-constant time crypto Please, nail the fucking basics of writing enclave code before going live and risking the hard-earned money of your users. PS: Not directed towards any specific protocol. Just a general observation.

great stuff ser 🫡 looking forward to more!

Crypto is… Desperate gamblers chasing their first bag. Investors funding the buildout of the global casino. Bankers hypnotizing the masses to collect their vig. …all meaningless and ephemeral without the cypherpunks, who defend the dream of encrypted and unstoppable cash.

saving this for a weekend read!

just made my first proper open-sourced contribution to an evm library - long overdue but better late than never! 🫡

feels good to be back to building after 1y of being stuck in corporate closed-source bs

where was @RareCodeAI when i was learning how to code, it's an absolute game-changer

hot take: coding without ai is still more fun

Our internal hackathon was a blast ❤️‍🔥 From AI creators to wellness tech to blockchain games, the Story team showed up in a big way. Ideas grow fast when people care - ship happens ;) Check out what we built ↓ story.foundation/blog/from-p…

new hack - creatine in my morning matcha, no more weird chemical tastes from drinking it alone

negates a bunch of "ai-web3" startups out there! 🫡

from personal experience, pls consider using at least one of these if you have anything 5 digits and above in hot wallets

New blog post is up: Coding a Rebase Token Rebase tokens (aka rebasing tokens) are quite common in DeFi, but there are surprisingly few educational resources on them. Therefore, we created a tutorial for how they work, how to create one, and the pitfalls of using them. Since it is easy to make a mistake when implementing a rebase token, we got our code audited. Thanks to @ChainLight_io @deadrosesxyz @PashovAuditGrp for donating some of their valuable time to help with this. We wanted to make sure not only that the code is correct, but that we included all the appropriate warnings that you can leverage when auditing a rebase token or a codebase that interacts with one. ChainLight published their audit, which is linked at the end of the article. You might learn something by reading it as well. You know where to find it.