7702 gets rid of this: not only do you have to send separate transactions, you have to send different tokens because of that. Literally, you can only send one token tote at a time how fucking stupid is that?

i think 7702 is flawed, but i support the good parts

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

Curious what are the flawed parts of 7702 in your opinion

Just another GPT in this universe






interspace.fi

Building a home for embedded apps at @interspace.

Toronto -- but currently in India visiting my fam

what in canada do you live?

these guys would be good to know of you like 7702 

cc @ardaa  @hennadios

1) doesn’t solve root cause of problems it needs to solve: ethereum doesn’t have native aa and also doesn’t rotate keys. any security system dependent on that is a no go, whether that is my eoa or a service providers bundler eoa 

2) master key permissions can’t be revoked once delegated. which means, u won’t use that for multi sig one of the largest use cases today.  

3) band aid and frankenstein dapps and wallets are already disagreeing on how to implant, and it’ll be a shit show like 4337 - different implementations, end points, error codes, etc 

here are better thoughts than mine

@pedrouid @gakonst Can you expand on your reasoning? Do you disagree with the general approach of enabling smart contract functionality on an existing EOA, or just the implementation details?

@evanchipman @gakonst Honestly the implementation details are not bad and I was participating in the discussions through each iteration

My only concern is there isn’t any mechanism to block the EOA “master” key from performing non-7702 transactions once there is a delegation… essentially making the

Pedro Gomes

1) doesn’t solve root cause of problems it needs to solve: ethereum doesn’t have native aa and also doesn’t rotate keys. any security system dependent on that is a no go, whether that is my eoa or a service providers bundler eoa 

2) master key permissions can’t be revoked once delegated. which means, u won’t use that for multi sig one of the largest use cases today.  

3) band aid and frankenstein dapps and wallets are already disagreeing on how to implant, and it’ll be a shit show like 4337 - different implementations, end points, error codes, etc 

here are better thoughts than mine

https://x.com/pedrouid/status/1858191311897035076?s=46