diff --git a/.github/styles/config/vocabularies/default/accept.txt b/.github/styles/config/vocabularies/default/accept.txt
index c30eb78f..e063a40e 100644
--- a/.github/styles/config/vocabularies/default/accept.txt
+++ b/.github/styles/config/vocabularies/default/accept.txt
@@ -286,4 +286,6 @@ v1
viem
zkLink
zKyoto
-wei
\ No newline at end of file
+wei
+Pectra
+Ithaca
\ No newline at end of file
diff --git a/assets/diagram-7702-approach-1.png b/assets/diagram-7702-approach-1.png
new file mode 100644
index 00000000..2ad34e75
Binary files /dev/null and b/assets/diagram-7702-approach-1.png differ
diff --git a/assets/diagram-7702-approach-2.png b/assets/diagram-7702-approach-2.png
new file mode 100644
index 00000000..5af894a2
Binary files /dev/null and b/assets/diagram-7702-approach-2.png differ
diff --git a/assets/diagram-7702-approach-3.png b/assets/diagram-7702-approach-3.png
new file mode 100644
index 00000000..e06f6767
Binary files /dev/null and b/assets/diagram-7702-approach-3.png differ
diff --git a/pages/advanced/_meta.json b/pages/advanced/_meta.json
index 897bfb75..e7d3241c 100644
--- a/pages/advanced/_meta.json
+++ b/pages/advanced/_meta.json
@@ -29,6 +29,7 @@
},
"erc-4337": "ERC-4337",
"erc-7579": "ERC-7579",
+ "eip-7702" : "EIP-7702",
"passkeys": "Passkeys",
"-- Safe CLI": {
"type": "separator",
diff --git a/pages/advanced/eip-7702/7702-safe.mdx b/pages/advanced/eip-7702/7702-safe.mdx
new file mode 100644
index 00000000..d1533cdf
--- /dev/null
+++ b/pages/advanced/eip-7702/7702-safe.mdx
@@ -0,0 +1,57 @@
+import { Callout } from 'nextra/components'
+
+# Safe and EIP-7702
+
+EIP-7702 does not specify how to initialise the storage of the account but only gives a way to set the code of the account. This means that the account will be created with an empty storage, and the user will have to set the storage manually.
+
+Existing Safe contracts cannot be used with EIP-7702, because of following reasons:
+
+- Delegating to Safe Singleton or the Proxy contract will expose the EOA account to the risk of front-running during setup.
+- In its current implementation, the Safe Singleton contract does not let itself to become an owner meaning that after delegating to the Safe Singleton, the EOA account cannot sign Safe transactions and will need to keep another private key to do so.
+
+## Possible approaches
+
+### Modified safe proxy
+
+This approach uses the [SafeEIP7702Proxy](https://github.com/5afe/safe-eip7702/blob/main/safe-eip7702-contracts/contracts/SafeEIP7702Proxy.sol), a proxy contract derived from the [Safe Proxy](https://github.com/5afe/safe-eip7702/blob/main/safe-eip7702-contracts/contracts/SafeEIP7702Proxy.sol) with the following changes:
+
+- The constructor of the `SafeEIP7702Proxy` contract has the additional `setupDataHash` parameter, which is the hash of the `setup` function call data. Thus, the address of the proxy contract also depends on the `setupDataHash` and not just the Singleton contract address. The proxy contract uses this hash to verify that the `setup` function parameter values are unchanged during the initialization of storage.
+- The proxy implements the `setup` function, which calls the `setup` function of the `singleton` contract and has additional logic:
+ - Set the storage slot 0, that is, the address of the singleton in the EOA storage.
+ - Verify that the `setupDataHash` equals the hash of the `setup` function call data.
+
+This approach has a gas overhead as a new proxy contract has to be deployed for each EOA account, as the `setupDataHash` may be unique for each user. However, using this approach, users can use Safe\{Wallet\} with minor modifications and import the EOA account as a Safe account.
+
+
+
+Follow the instructions here to use this approach to set code in EOA: https://github.com/5afe/safe-eip7702/tree/main/safe-eip7702-contracts#execute-scripts
+
+### Modified safe singleton
+
+This approach uses the [SafeEIP7702](https://github.com/safe-global/safe-smart-account/blob/feature/eip-7702/contracts/experimental/SafeEIP7702.sol) contract, a derived version of Safe Singleton that overrides the `setup` function and reverts when called. Instead, the contract's new `setupEIP7702` function has a `signature` parameter. The default owner will be set to the address of the EOA account that delegates to this Singleton contract with a threshold of 1.
+
+Because this approach does not use a proxy contract, storage slot 0 remains unused. The Safe Transaction Service and other services that depend on the value at storage slot 0 will not work with this approach.
+
+
+
+### SafeLite
+
+[SafeLite](https://github.com/5afe/safe-eip7702/blob/main/safe-eip7702-contracts/contracts/experimental/SafeLite.sol) is a lite version of Safe that is compatible with EIP-7702. The contract does not have a proxy and does not need initialization.
+
+SafeLite supports ERC-4337 and can use features such as sponsored transactions and batch transactions. SafeLite also supports ERC-1271 for contract-based signatures.
+
+SafeLite is not compatible with Safe\{Wallet\} as it does not use the same storage layout as the existing Safe contracts.
+
+It does not have the features of the existing Safe contracts such as Modules, Fallback Handler, and Guards.
+
+
+
+
+ All the above approaches are experimental and the contracts are not yet audited. Use them at your own risk.
+
+
+## Other resources
+
+- [SafeEIP7702Proxy GitHub repository](https://github.com/5afe/safe-eip7702/blob/main/README.md#demo-using-ui)
+- [Safe + EIP-7702 tutorial](https://www.youtube.com/watch?v=dx4mk6tKHCo)
+- [Safe + EIP-7702 Slides](https://docs.google.com/presentation/d/1blYoVXLdPUNXhfSlck5bgbs8-h9StI9om7wsxj1SxVM)
\ No newline at end of file
diff --git a/pages/advanced/eip-7702/_meta.json b/pages/advanced/eip-7702/_meta.json
new file mode 100644
index 00000000..340b11df
--- /dev/null
+++ b/pages/advanced/eip-7702/_meta.json
@@ -0,0 +1,4 @@
+{
+ "overview": "Overview",
+ "7702-safe": "Safe and EIP-7702"
+}
diff --git a/pages/advanced/eip-7702/overview.mdx b/pages/advanced/eip-7702/overview.mdx
new file mode 100644
index 00000000..2a4463c4
--- /dev/null
+++ b/pages/advanced/eip-7702/overview.mdx
@@ -0,0 +1,40 @@
+import { Callout } from 'nextra/components'
+
+# What is EIP-7702?
+
+EIP-7702 is a step towards account abstraction, enabling EOAs (Externally Owned Accounts) to have both code and storage. This enhancement allows EOAs to function as smart contract accounts, unlocking new features such as:
+
+- **Transaction batching**.
+- **Gas sponsorship**.
+- **Delegated actions**: Granting other addresses limited access to act on behalf of the EOA.
+
+## Signing Process
+
+In its current implementation, EIP-7702 requires the EOA to sign a special hash calculated using the following parameters:
+
+- `chain_id`: The identifier of the blockchain network.
+- `address`: The account address to which calls will be delegated.
+- `nonce`: Current nonce of the account.
+
+Once the EOA signs the hash, an authorization list is sent to the EVM node through a new transaction type, the set code transaction, introduced in EIP-7702.
+
+The execution client then performs the following checks:
+
+- Verifies the signature.
+- Checks the account's nonce.
+- Confirms the chain ID (`0` or the current chain ID).
+
+If all checks pass, the execution client sets the EOA's code in the format `(0xef0100 ++ address)`.
+
+EIP-7702 is available on devnets and testnets such as Pectra Devnet, Ithaca and will be enabled on Ethereum Mainnet after the Pectra upgrade.
+
+An important consideration that applies for EOAs that have code set is that the private key can still be used to sign transactions and even change delegations. Hence, it is important to keep the private key secure even after the authorization has been signed.
+
+
+ This signing method is not compatible with the EIP-712 or EIP-191 standards. Wallet providers must add support
+for this specific signing method.
+
+
+## Further reading
+
+- [EIP-7702 on Ethereum EIPs](https://eips.ethereum.org/EIPS/eip-7702)