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

what do you think of Blumen?

Decentralized front-ends, with the domain managed by ENS and Safe + automatic replication of the IPFS distribution to multiple services

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

shazow.net

Currently: WhatsABI

what do you think of Blumen?

Decentralized front-ends, with the domain managed by ENS and Safe + automatic replication of the IPFS distribution to multiple services

https://blumen.stauro.dev

Presenting Blumen - self custodial, decentralized deployments. Powered by @ethereum, @ipfs, @ensdomains and @safe.

- No Sign up required: pass the API keys from providers directly
- Multi-provider: Supports @storacha and @filebase, more coming soon
- ENS: update your web3 name automatically
- DNSLink: Use your regular web2 domain to serve your IPFS site
- Powered by Safe: Update your names in the most secure way with a delegate + manager as Safe
- Open Source: all of the code is public on GitHub

Enter the decentralized web now

https://blumen.stauro.dev

building Stauro ❇ frontend dev at @ensdomains ❇
prev. @rainbow, @geniexyz, @fleek

here's a demo video of how it works

https://warpcast.com/v1rtl.eth/0x6932a1b6

I understand and agree

besides just the infra, the apps themselves have to be diverse, kind of like client diversity but for dapps specifically

for Safe there actually was a few, Eternal Safe for example

wdyt of having an index/aggregator of dapps or something like that?

I'm all for making it easier to deploy local-first frontends on IPFS/ENS/etc!

But keep in mind, deploying the same vulnerable code on IPFS would not make it safe from the vulnerability. 🫠

Independent implementations that don't share the same supplychain attack surface is what's important.

I'd take two totally separate implementations hosted in separate centralized servers over two identical implementations both on IPFS.