Ethereum

Safe{Wallet} removed native ledger/trezor support.

@koeppelmann.eth is entering his @dwr.eth "opportunity for another client" era: https://x.com/koeppelmann/status/1896244047662231694

(I don't really disagree with either, I'm all for anything that actually results in more clients!)

@koeppelmann Users can still use the removed hardware wallets, and have to be able to else SAFEs would be bricked.  All this does is force users to now have another man in the middle of their transaction (browser wallet).

@MicahZoltu At this point we have to prioritize security over everything else - even metadata privacy. So I don’t see a wallet as another man in the middle but another layer that gives the user the chance to catch a mistake.

If you want different choices, everything is open source and…

koeppelmann.eth 🦉💳

Working on Farcaster and Warpcast. Longer thoughts at https://dwr.email

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

shazow.net

Currently: WhatsABI

Have you thought about building better safe support into callthis?

Pragmatism (Security) at OP Labs.
Prev: ConsenSys & Coinbase.

Attribs: Friendly, curious, introverted, mid-witted.
Chans: /eth-security /maurelian /stoicism




I’d start with only supporting approveHash(onchain signatures) or prevalidated signing (approving by call to execTransaction when msg.sender is an owner). 

And also make it easier to encode the data argument.

I have a little! It already has the Safe SDK to support being run in the Safe iframe.

I was trying to imagine what it would take to be a useful alternative Safe frontend altogether, but don't have great ideas yet. You got something in mind?