just used 7702 to solve a micropayments problem by delegating to a contract that emits an ETHReceived event

took me 5 mins to write and deploy a contract in remix and 5 minutes to create an authorization with viem

takeaways:
1. eth transfer event logs should really be a thing natively
2. god bless ethereum tooling

@apoorveth someone stop this man right now

Add this to your 7702 account,

and you don't need 3rd-party APIs for fetching ETH transfers into your EOA https://t.co/2tiPRCh8Vd

apoorv.eth

Smart contracts @ flaunch.gg
Building🕵 impersonator.xyz
🟥 swiss-knife.xyz 
🔍 @eiptools
🖼️ framestore.xyz
🏗️ apoorv.xyz

also shoutout @apoorvlathey for the idea https://x.com/apoorveth/status/1924284995964690447

Contracts can't easily react to incoming ETH without custom receive() function. You'll have multiple verified addresses but indexing on all is unnecessary here. We want to share those events amongst the clients.

There are like 5 different ideas you could be talking about here - for what specifically are you referring to?

7702 wallet so we can delegate pubkeys between clients 🤔