Skip to content

Use Memory Type Variable Instead of Storage Type Variable in Event to Save Gas#2650

Open
HighBe wants to merge 1 commit intoLoopring:release_loopring_3.6.3from
HighBe:release_loopring_3.6.3
Open

Use Memory Type Variable Instead of Storage Type Variable in Event to Save Gas#2650
HighBe wants to merge 1 commit intoLoopring:release_loopring_3.6.3from
HighBe:release_loopring_3.6.3

Conversation

@HighBe
Copy link
Copy Markdown

@HighBe HighBe commented Aug 28, 2022

Hi, we are a research group on programming languages and software engineering. We recently have conducted a systematic study about Solidity event usage, evolution, and impact, and we are attempting to build a tool to improve the practice of Solidity event use based on our findings. We have tried our prototype tool on some of the most popular GitHub Solidity repositories, and for your repository, we find a potential optimization of gas consumption arisen from event use.

The point is that when we use emit operation to store the value of a certain variable, local memory type variable would be preferable to storage type (state) variable if they hold the same value. The reason is that an extra SLOAD operation would be needed to access the variable if it is storage type, and the SLOAD operation costs 800 gas.

For your repository, we find that several event uses can be improved.

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