From 2a6bf98111cef4a71ae9e51ff31e4551cfca0118 Mon Sep 17 00:00:00 2001 From: gajinder Date: Fri, 26 Jul 2024 22:12:19 +0530 Subject: [PATCH] fix --- EIPS/eip-7702.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7702.md b/EIPS/eip-7702.md index 30fe6caa32dcc..07276f05ee9e6 100644 --- a/EIPS/eip-7702.md +++ b/EIPS/eip-7702.md @@ -121,7 +121,7 @@ An alternative to adding chain ID could be to sign over the code the address poi Considering that the delegation from one contract to another contract may cause conflicts and corrupt the storage with a broken contract at the least and a compromised contract at the worst, it is prudent to separate the storage of each delegation in deterministic way. -To this effect, the delegated EOA's storage keys should be proxied (accessed or written) at `keccak256(key||address)[0:30] || key[31:32]`. So essentially we use this key modification for `SLOAD` and `SSTORE` operations for the delegated EOA's orignal key but still writing into EOA storage. +To this effect, the delegated EOA's storage keys should be proxied (accessed or written) at `keccak256(key[0:30]||address)[0:30] || key[31:32]`. So essentially we use this key modification for `SLOAD` and `SSTORE` operations for the delegated EOA's orignal key but still writing into EOA storage. With this method: