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

- not necessarily, you can forget the key and just replay the auth sig across chains, delegate to proxy and use the contract to handle upgrades. alternatively can store the privkey in cloud etc encrypted w enclave, nbd imho.
- unclear it matters, the ui will give you a preview over x-origin iframe, and your contract will have enough safety checks to ensure you don't get rugged. check secure payment confirmation web api if you really care about doing it non blind. 
- granted but not deal breaker, your contract can have multiple signers, need to be thoughtful about it but navigable, plus passkeys being pushed top down.
- session keys app/account interface is important to get right, see our work in porto for more: https://www.ithaca.xyz/updates/porto, and our WIP session key api which is still evolving: https://github.com/ithacaxyz/porto/tree/next?tab=readme-ov-file#keys

this is lame

“…you can forget the key and just replay the auth sig across chains, delegate to proxy and use the contract to handle upgrades. alternatively can store the privkey in cloud etc encrypted w enclave, nbd imho.”

we need native aa. everything else is a bad aid so engineers can chase scale 

smh

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

The same things I said to you on in Twitter and in DM. And as I asked there, what do you think of Pedro’s comments and replies to you here?

@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

cto & general partner @paradigm. ceo /ithaca. working with /rust on /ethereum. building /reth and /foundry. https://gakonst.com

The same things I said to you on in Twitter and in DM. And as I asked there, what do you think of Pedro’s comments and replies to you here?

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

and 

wen native aa, or keystore, or keystore rollup type solutions? 

all yall do is create more account types, standards, different endpoints that don’t match bc people don’t follow the standards 

and yet we keep having same problems and making it harder for  the user 

it’s a joke.

Why does signal protect our chats better than any wallet protects our assets. And why does one password make it easier to use my account instead of having to use 900 different wallets that I can’t use together

your thinking of what can be built seems to be linked to what exists in the market, that makes sense but you can also think beyond that -- you can do everything you ask for with today's tech, cross app, cross wallet etc. -- yes people won't follow the standards in a competitive pre PMF market that's also my point :) build stuff that works. your requirements are good and I think we meet all of them.