**Background** EIP-7702 introduces a new transaction type, namely transaction type 4, to set the code of an EOA to a specific address, enabling EOAs to have smart account capabilities. The transaction introduced a new field authorization_list, which allows a transaction sender to set the code of multiple EOAs in one transaction, as long as the signatures provided are valid. ``` // newly added transaction field authorization_list = [[chain_id, address, nonce, y_parity, r, s], ...] // validation logic authority = ecrecover(keccak(MAGIC || rlp([chain_id, address, nonce])), y_parity, r, s) ``` **Problem** The behaviour of a setcode transaction decouples delegation setting (through authorization_list) from transaction execution. This means that there are situations where transaction reverts, but valid delegations are successful and not rolled back, and vice versa, where transactions succeed but delegations fail. Currently, transaction receipts only have an indicator of transaction results through status, but provide no information about the result of authorizations within the transaction. This means that the only way to determine the result of delegation is through the following steps: 1. `eth_getCode` RPC call with EOA address 2. Parse response to determine if the delegate is as expected This makes the process arduous and unnecessarily intensive, especially when handling large batches of authorizations. **Proposed Solution** https://github.com/ethereum/execution-apis/pull/640 To utilise an ordered list of uint arrays, to indicate success or failure of each authorization in the list. The indicator for success would be 1, and failures would be 0, following the same convention as the status field within the current transaction receipt structure. **References** https://github.com/ethereum/EIPs/blob/master/EIPS/eip-7702.md#behavior