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

Optimize undefined gas limit for individual Beacon updates #448

Open
bbenligiray opened this issue Jul 17, 2023 · 1 comment
Open

Optimize undefined gas limit for individual Beacon updates #448

bbenligiray opened this issue Jul 17, 2023 · 1 comment
Labels
enhancement New feature or request Operations
Milestone
Post-Phase 2

Comments

@bbenligiray
Copy link
Member

Blocked by https://github.com/api3dao/airseeker/issues/447 and https://github.com/api3dao/airseeker/issues/446

With self-funded Beacons, we also want to omit fulfillmentGasLimit (same reasons as https://github.com/api3dao/airseeker/issues/447), but we don't want to call estimateGas() for each update because it's wasteful (they will all return the same value). As a solution, in cases that fulfillmentGasLimit is not defined and the transaction to be made is a single Beacon update, we can use the estimateGas() result we got from https://github.com/api3dao/airseeker/issues/446
@metobom metobom added this to the Phase 2 milestone Jul 17, 2023
@bbenligiray bbenligiray changed the title Support undefined gas limit for self-funded Beacons Optimize undefined gas limit for individual Beacon updates Jul 17, 2023
@bbenligiray
Copy link
Member Author

@metobom Let's also drop this from Phase 2 to high priority Post-phase 2

@bbenligiray bbenligiray mentioned this issue Aug 10, 2023
Closed
@metobom metobom modified the milestones: Phase 2, Post-Phase 2 Aug 14, 2023
@metobom metobom added the enhancement New feature or request label Aug 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement New feature or request Operations
Projects
None yet
Milestone
Post-Phase 2
Development

No branches or pull requests
2 participants
@bbenligiray @metobom