Ethereum

Safe{Wallet} frontend infrastructure was compromised.

🥁 We need to reduce our dependence on centralized frontends!

We need more independent frontends implementations or, better yet, generative frontends. At least one signer should use a different frontend.

Bybit Hack Forensics Report
As promised, here are the preliminary reports of the hack conducted by @sygnia_labs and @Verichains 
Screenshotted the conclusion and here is the link to the full report: https://t.co/3hcqkXLN5U https://t.co/tlZK2B3jIW

Ben Zhou

Safe{Wallet} frontend infrastructure was compromised.

🥁 We need to reduce our dependence on centralized frontends!

We need more independent frontends implementations or, better yet, generative frontends. At least one signer should use a different frontend.
https://x.com/benbybit/status/1894768736084885929

idk about you but the bybit x safe situation makes me very bullish ENS as it would avoid address substitution attacks

IPFS CIDs + onchain signatures = safety

Need verification of the frontend code through CIDs anchored to the specific address.

You can see what that looks like here: https://t.co/zAkIUzxl0m https://t.co/5RPe0qcc68

Kyle Tut

A doodler and computerer. I like permissive/permissionless open source, smart contracts, p2p systems, room-scale VR, and NixOS.

shazow.net

Currently: WhatsABI

Haveeeeee you met Pinata?

https://x.com/KyleTut/status/1894793884552532097

I have! I'm a fan of IPFS-pinning local-first apps! callthis.eth.limo works this way too (though using IPNS and sadly not via Pinata this time).

But what's preventing an IPFS-pinned update from including the same compromised CDN build that the centralized deploy was using?

This is what independent implementations address.

Everyone is from somewhere. Cofounder and CEO of Pinata. https://www.pinata.cloud/