-autoAdjustPrice flag to enable/disable automatic price adjustments #2025
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this pull request do? Explain your changes. (required)
At the moment, an orchestrator can be configured with a base price (per pixel) which is then automatically adjusted based on the estimated overhead (the % representing tx cost / ticket face value) for redeeming winning tickets on-chain. As a result, the price advertised by the orchestrator is typically higher than the configured base price and it will fluctuate depending on the current estimated overhead for redeeming tickets. For example, given a base price of 1000:
The motivation for the auto price adjustment mechanism is to allow orchestrators to dynamically update their price to compensate for higher overheads for ticket redemptions if gas prices on Ethereum spike. However, this mechanism can also cause a few problems:
This PR introduces a
-autoAdjustPrice
flag that can be used to enable/disable automatic price adjustments. By default, the flag is set to true which matches the current behavior of the node. If the flag is set to false, the orchestrator will always return its base price as its advertised price regardless of the current estimated overhead of redeeming tickets. For example, if the base price is 1000, regardless of the estimated overhead for ticket redemption, the advertised price would be 1000.Specific updates (required)
See commit history.
How did you test each of these updates (required)
Added unit tests.
Does this pull request close any open issues?
Fixes #1966.
Checklist:
make
runs successfully./test.sh
pass