Skip to content
This repository has been archived by the owner on Jul 9, 2024. It is now read-only.

Do not use multicall while reading on chain data for individual beacon updates #475

Open
bdrhn9 opened this issue Sep 17, 2023 · 0 comments

Comments

@bdrhn9
Copy link
Contributor

bdrhn9 commented Sep 17, 2023

Related with #449.

Linked PR for #449 removes using multi call while sending transaction to update individual beacons. This saves gas overhead that multi call cause. However in the process of reading on chain data to check whether condition is satisfied, multi call is being utilizied even if one beacon is in the batch. This cost no extra money because it's static call but increases overhead on RPC side.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant