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
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 callestimateGas()
for each update because it's wasteful (they will all return the same value). As a solution, in cases thatfulfillmentGasLimit
is not defined and the transaction to be made is a single Beacon update, we can use theestimateGas()
result we got from https://github.com/api3dao/airseeker/issues/446