good q & a between @jxom and @accountless.eth re trusting wallets

https://x.com/_jxom/status/1879454626086609032

my mental model for 3p trust:
1) trust the party isn't intentionally evil
2) trust the party isn't unintentionally evil (e.g. misaligned values or incentives)

1 is basically unavoidable. there's an entire stack starting with hardware going up through your operating system to an application that has to be trusted to not be blatantly ripping you off.

2 should be minimized. for example if two parties offer private messaging and one is e2ee that e2ee is preferred. but you're still making trust assumptions in both categories (in 1 that they aren't lying to you and actually forwarding your data in plaintext and 2 that their client and encryption are secure)

jxom point is convincing that throwing away a private key is trivial so the category 2 trust assumption is minimal and you're already having to trust in category 1 for many other things that are harder to get right

The more I dig into EIP-7702, the more issues I find 🙄

As usual, too much hype. I highly doubt 7702 will bring the UX improvements we all hope for.

Here's my 7702 review:

1. In terms of signer abstraction, we regressed

@4337 smart contract wallets (SWC) have a really nice…

@joenrv @4337 - On 1 &amp; 2: valid concern if user wants multisig/strict execution guards - but this could be solved by deactivating the private key (EIP-7851)
- On 2: usually the wallet would perform the delegation, so I would trust the wallet to “throw away” the private key (if that’s the…

jxom

intersend.io | via sequence. pimlico. poap. polygon. metamask. paxful. flipside crypto. dash. bridgewater. darpa. secdef. navy. dia. linktr.ee/alexanderchopan

Building @warpcast and @farcaster, new dad, like making food

this convo was 🔥! trust is such a tricky thing with wallets, but jxom made some solid points. always learning from these discussions! 👏💡 