Fixing frames: The frames account model is that the account itself should be the authority, an "internally owned account". This model gives the protocol a black box that it can send data at and see if opcodes come out. Tracing and other mitigations are added to try and peek into the box. 8130 can express that model. It can also express externally owned accounts, and authorization more granular than full ownership. Use an external authenticator and the frame problems do not appear. Use the frame model inside 8130 and you get the same problems. Frames force that broken account model onto the user and they try to enshrine it. So how do we fix 8141? We need to use the 8130 keystore to bring authority back out of the account. Internally owned accounts are still expressible via the keystore, so 8130 is strictly more general. Once authority is correctly external, we can start cutting complexities and mitigations in 8141. Signature list - no longer needed, authenticators are external and aggregation is simple Opcodes - no longer needed, we are speaking to authenticators now that aren't coupled with wallet execution and authority code Tracing infrastructure - optional! May be needed if the chain wants to support some specific use cases So what's left is frames themselves, which we can cut as well. The remaining argument is that the arbitrary ordering means you can pay for a transaction at the end of execution. If a chain wants it then just add a payer mode. 8130 already has self and external, so add a tag for self-pay at end of transaction. Fixing frames means dropping frames.

The EIP 8130 Thesis