Skip to content

fix: invalidate stale storage map values after slot recreation - #2378

Open
bravesasha wants to merge 1 commit into
0xMiden:nextfrom
bravesasha:fix/storage-map-remove-create-stale-entries
Open

fix: invalidate stale storage map values after slot recreation#2378
bravesasha wants to merge 1 commit into
0xMiden:nextfrom
bravesasha:fix/storage-map-remove-create-stale-entries

Conversation

@bravesasha

Copy link
Copy Markdown

When a storage map was removed and then created again, old entries from the previous map could incorrectly remain visible in the new one. This happened because removing the map did not clear its existing values from the database. The fix now removes all old map values when the storage slot is removed, and adds regression tests covering both separate Remove - Create updates and the merged patch scenario from issue #2328

@bravesasha
bravesasha force-pushed the fix/storage-map-remove-create-stale-entries branch from 04c12f6 to 293e24a Compare July 26, 2026 17:21
@bravesasha
bravesasha force-pushed the fix/storage-map-remove-create-stale-entries branch from 293e24a to ea25ec9 Compare July 26, 2026 17:27
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.

2 participants