Greg
Greg
Talking with @DylanTinianov we agreed the third way of rollbacking to the latest possible state would be best. This means after an update of an existing contract we roll back...
Consensus is to move back to generic event type ID `A.{address}.EVM.{name}` cc @ramtinms @m-Peter
The consensus was to just rollback special even type IDs for EVM, and use the generic type ID signature.
> @peterargue thanks a lot for this, btw do we have archive nodes still ? last time I tried to work on this I was failing at that. > >...
@bluesign Does this design seem safe to you?
Looking at this I don't think EIP 7702 can be used to achieve delegation of EOA to COA permanently since the contract code is only active during transaction. This means...
oh my bad, I mixed 3074 with 7702 I guess (yesterday wasn't my day). The 7702 as proposed to permanently set the code on EOA would work. What this means...
@jribbink yeah that's probably what got me confused yesterday. But yeah official reference is clear.
Just FYI still WIP, will share once I complete it.
Querying by scheduled transaction (callback) ID is definitely a valuable addition to our APIs. My concern is that users who observe on-chain executions will see events tied to a transaction...