update doc

Author: conorpp

README.md

@@ -20,6 +20,34 @@ It is deployed on the following chains:
 | Optimism            | [0xdd1b6240f097cbbb9c1e7dd8dc473f92f0608816](https://optimistic.etherscan.io/address/0xdd1b6240f097cbbb9c1e7dd8dc473f92f0608816#code)       |
 | Optimism Sepolia    | [0xdd1b6240f097cbbb9c1e7dd8dc473f92f0608816](https://sepolia-optimism.etherscan.io/address/0xdd1b6240f097cbbb9c1e7dd8dc473f92f0608816#code) |
 
+## EIP 7702
+
+### Overview
+
+EIP7702 allows EOA addresses to be treated as contract addresses. This is introduced as a new EVM transaction type which adds
+a new field called "authorization list".
+
+Each authorization in the list makes a temporary delegation to a contract address for some EOA. This authorization must be signed by that EOA.
+It is temporary in that the EOA can be delegated to this contract only in transactions containing a proper authorization for it.
+
+Note that the transaction itself does not need to be signed by the EOA's being delegated. So a "fee-payer" address can craft a transaction
+containing these authorizations for other EOA's and thus sponsor actions for them.
+
+### EIP 7702 contract
+
+For the authorized EOA, this contract is executed as if EOA is the contract. Meaning the contract can move funds, call other contracts for the EOA.
+Thus it's important that the EOA additionally signs the actions done by the contract (stored in the `data` of the transaction). This protects the EOA
+from the "fee-payer" address inserting arbitrary actions.
+
+The input to `BasicSmartAccount` is a list of `(to address, value uint256, data bytes)` tuples, all of which are signed by the EOA. The
+input is simply verified and executed.
+
+In summary:
+
+- Any EOA can delegate to `BasicSmartAccount` contract by signing an authorization.
+- By delegating to `BasicSmartAccount` in a transaction, an EOA is trusting `BasicSmartAccount` to correctly execute any signed `(address, value, data)` tuples included in that same transaction.
+- The transaction containing the authorization list and `(address, value, data)` data itself can be signed by a separate address. This address pays the fees.
+
 ## Foundry
 
 **Foundry is a blazing fast, portable and modular toolkit for Ethereum application development written in Rust.**
@@ -69,6 +97,9 @@ anvil
 
 ### Deploy
 
+Deployment is done using deterministic `CREATE2` instruction. Meaning any address can deploy this contract to a chain (for the given `EVM_SALT`),
+and it will have the expected contract address. Note that if any part of the contract changes, then the contract address will also be different.
+
 ```shell
 # keccak256("BasicSmartAccount")
 export EVM_SALT=bdfee0231e0903cde9ca6fd75d08a500062dc3d87718f712bc6958ed697617c3