Eggiiks 🐸

Are you a better AMM designer than me? @bqbrady and I built a challenge that lets you prove it Create your own dynamic-fee AMM and submit it to get onto our leaderboard Link in 🧵👇

We set out to examine effective latency in ethereum & rollup-boost, uncovering how compression affects both client-to-node latency and vice versa, pinpointing the primary bottlenecks and practical solutions to mitigate them. 1/9 - A quick overview tadpole-labs.ai/articles/compr…

Bridge & Swap to @world_chain_ in a single flow🔄 Now supporting routes from over a dozen EVM chains. 👇

Hermes 🤝 Ink Use Hermes to bridge and swap in one seamless omnichain flow to tokens on @inkonchain, the high-performance, DeFi-native L2 unleashed by Kraken, built on the Superchain.

a new TEE blockchain exploit just dropped. surprise! next time someone tells you a TEE can be used in web3 use cases to ensure integrity or honesty of nodes, send them this post. TEEs are web2 tech. cryptography is web3. here’s some notes showing how messy this gets: voltpillager: hardware undervolting attacks on intel sgx with a $30 tool: zt-chen.github.io/voltpillager/ glitching the amd secure processor: github.com/PSPReverse/amd… older tea stains / past scandals: from today: arstechnica.com/security/2025/… sgx fail: sgx.fail badram: badram.eu in short, past tee disasters: foreshadow (2018 speculative-exec leaks), voltpillager (2021 $30 undervolting sgx break), secret network (2022 research showed extracting the sgx consensus seed lets you decrypt past private txs), badram / sev glitches (2024 cheap memory-aliasing attacks on amd), battering-ram & wiretap (2025 cheap interposer attacks against ddr4 sgx/sev-snp). yet people still have the audacity to call TEEs “the future.” they are not, and saying this is hurting our industry.