Skip to content

Conversation

EperezOk
Copy link

What was wrong?

Related to Issue #1354

How was it fixed?

Removed redundant checks and account destruction operations.

Cute Animal Picture

Jiraffe

@EperezOk EperezOk changed the title fix: redundant account destruction after state modification Fix: Redundant account destruction after state modification Jul 29, 2025
@SamWilsn SamWilsn force-pushed the fix/redundant-account-existence-checks branch from 3adbb4e to a9ce06c Compare July 31, 2025 16:20
@SamWilsn SamWilsn changed the base branch from master to forks/osaka July 31, 2025 16:20
@EperezOk
Copy link
Author

EperezOk commented Aug 1, 2025

@SamWilsn please let me know if anything else is needed from my side or if I should mark the PR as "ready for review"

@SamWilsn
Copy link
Contributor

Hey! Thanks for the fix.

If you're feeling lazy, you can leave this and we'll do the rest of the work ourselves eventually. Otherwise, it'll need to be ported to the other post-merge forks before we can merge.

If you're feeling super enthusiastic, might be worth investigating whether we can remove account_exists_and_is_empty entirely from post-merge forks.

@EperezOk
Copy link
Author

Hi @SamWilsn!

I ported the change to the other post-merge forks. I also confirmed that account_exists_and_is_empty is no longer needed in those forks, so I removed the function and inlined it within modify_state.

@EperezOk EperezOk marked this pull request as ready for review August 31, 2025 06:05
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