Skip to content

test(semantic): update the storage tests to reflect new semantics#130

Draft
samlaf wants to merge 1 commit intoseismicfrom
test--new-storage-opcode-semantics
Draft

test(semantic): update the storage tests to reflect new semantics#130
samlaf wants to merge 1 commit intoseismicfrom
test--new-storage-opcode-semantics

Conversation

@samlaf
Copy link
Contributor

@samlaf samlaf commented Jan 22, 2026

DO NOT MERGE!

We would ideally want to merge this, but we are ongoing audits in this repo, and don't want to merge to seismic branch while that is ongoing. We will merge this after audits are done.

We updated the semantics of confidential storage opcodes in SeismicSystems/seismic-revm#180. The changes here are needed to reflect the new semantics.

Note

Whoever merges this should go and fix the CI in seismic-revm to point back to checking out the seismic branch of this repo, instead of this branch (test--new-storage-opcode-semantics).

We updated the semantics of confidential storage opcodes in SeismicSystems/seismic-revm#180. The changes here are needed to reflect the new semantics.
@samlaf samlaf marked this pull request as draft January 22, 2026 21:42
samlaf added a commit to SeismicSystems/seismic-revm that referenced this pull request Jan 22, 2026
See committed README changes for explanation of new semantics. TLDR is
that we are implementing these new semantics, after some audit
discussions.

|           | (0, public)  | (x, public) | (0, private) | (x, private) |
| --------- | ------------ | ----------- | ------------ | ------------ |
| SLOAD     | 0            | x           | HALT         | HALT         |
| CLOAD     | 0            | x           | 0            | x            |
| SSTORE(y) | (y, public)  | (y, public) | HALT         | HALT         |
| CSTORE(y) | (y, private) | HALT        | (y, private) | (y, private) |

## Note

Had to update CI semantic tests to point to
SeismicSystems/seismic-solidity#130 in order to
fix tests. We should change back CI once that PR merges after audit.
Added a note in that PR.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant