You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `to` and `memo` fields in `DecryptionData` were redundant: the
on-chain `ZoneInbox` already decrypts the ciphertext via AES-256-GCM
and can derive these values directly from the plaintext. Remove them
from the struct and use the decrypted values on-chain instead of
comparing against sequencer-supplied duplicates.
Saves 52 bytes of calldata per encrypted deposit (20-byte address +
32-byte memo).
Closes#357
Made-with: Cursor
Copy file name to clipboardExpand all lines: docs/pages/protocol/privacy/overview.md
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1230,18 +1230,18 @@ This ensures deposits are processed in the exact order they were made, regardles
1230
1230
1231
1231
**On-chain decryption verification:**
1232
1232
1233
-
The zone can verify encrypted deposit decryption on-chain without the sequencer revealing their private key. The sequencer provides the ECDH shared secret alongside the decrypted data:
1233
+
The zone can verify encrypted deposit decryption on-chain without the sequencer revealing their private key. The sequencer provides the ECDH shared secret and a proof of correct derivation:
0 commit comments