Open
Conversation
magurh
requested changes
Mar 6, 2026
| | **Precision (step size)** | ≈0.0122% | [`FastUpdatesIncentiveManager.getPrecision`](/ftso/solidity-reference/IFastUpdateIncentiveManager#getprecision) | | ||
| | **Range** | 0.0183% | [`FastUpdatesIncentiveManager.getRange`](/ftso/solidity-reference/IFastUpdateIncentiveManager#getrange) | | ||
| | **Max range (max increment per block)** | 0.091% (5x) | [`FastUpdatesIncentiveManager.rangeIncreaseLimit`](/ftso/solidity-reference/IFastUpdateIncentiveManager#rangeincreaselimit) | | ||
| | **Max increment per second** | 0.054% | - | |
Member
There was a problem hiding this comment.
I'd remove max increment per second since this is a number that depends on block latency
| | **Mean updates per block** | 1.5 | [`FastUpdatesIncentiveManager.getExpectedSampleSize`](/ftso/solidity-reference/IFastUpdateIncentiveManager#getexpectedsamplesize) | | ||
| | **Precision (step size)** | ≈0.0122% | [`FastUpdatesIncentiveManager.getPrecision`](/ftso/solidity-reference/IFastUpdateIncentiveManager#getprecision) | | ||
| | **Range** | 0.0183% | [`FastUpdatesIncentiveManager.getRange`](/ftso/solidity-reference/IFastUpdateIncentiveManager#getrange) | | ||
| | **Max range (max increment per block)** | 0.091% (5x) | [`FastUpdatesIncentiveManager.rangeIncreaseLimit`](/ftso/solidity-reference/IFastUpdateIncentiveManager#rangeincreaselimit) | |
Member
There was a problem hiding this comment.
remove "(max increment per block)"
| | **Update size** | ≈200k (1.33%) | - | | ||
| | **Mean updates per block** | 1.5 | [`FastUpdatesIncentiveManager.getExpectedSampleSize`](/ftso/solidity-reference/IFastUpdateIncentiveManager#getexpectedsamplesize) | | ||
| | **Precision (step size)** | ≈0.0122% | [`FastUpdatesIncentiveManager.getPrecision`](/ftso/solidity-reference/IFastUpdateIncentiveManager#getprecision) | | ||
| | **Range** | 0.0183% | [`FastUpdatesIncentiveManager.getRange`](/ftso/solidity-reference/IFastUpdateIncentiveManager#getrange) | |
Member
There was a problem hiding this comment.
Add a description for Range in brackets: "(precision * mean updates)"
| | **Range** | 0.0183% | [`FastUpdatesIncentiveManager.getRange`](/ftso/solidity-reference/IFastUpdateIncentiveManager#getrange) | | ||
| | **Max range (max increment per block)** | 0.091% (5x) | [`FastUpdatesIncentiveManager.rangeIncreaseLimit`](/ftso/solidity-reference/IFastUpdateIncentiveManager#rangeincreaselimit) | | ||
| | **Max increment per second** | 0.054% | - | | ||
| | **Incentive duration** | 17 blocks (≈29 seconds) | [`FastUpdatesIncentiveManager.getIncentiveDuration`](/ftso/solidity-reference/IFastUpdateIncentiveManager#getincentiveduration) | |
Member
There was a problem hiding this comment.
Remove the "=(29 seconds)" since this depends on block latency
|
|
||
| | Metric | Value | Associated functions | | ||
| | ------------------------ | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | **Update size** | ≈200k (1.33%) | - | |
Member
There was a problem hiding this comment.
Update size for Scaling is not correct. Scaling "updates" technically consist of 3 separate transactions from each data provider: submit1, submit2, and submitSignatures. Each takes around 30k gas (usually from 24k to 31k, depending on the transaction).
Meanwhile, for Block latency updates, i.e. the submitAndPass transactions, the current size is 180k to 260k per transaction.
Regardless, these are not really protocol parameters.
fassko
force-pushed
the
protocol-parameters
branch
from
70d4e0d to
d155f3e
Compare
fassko
force-pushed
the
protocol-parameters
branch
from
d155f3e to
70d4e0d
Compare
fassko
force-pushed
the
protocol-parameters
branch
from
63da612 to
0db4d72
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
No description provided.