You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 15, 2023. It is now read-only.
Modules that manually validate transaction might want to have a configurable Get<u64> as an indicator of how to set the priority. An example would be staking in which the priority of offchain phragmen solutions is better to be configurable.
To demonstrate the problem, consider this: currently, score[0] is the priority, which makes perfect sense if the pool wants to prioritise between 3 transactions of the same type (submit_election_solution_unsigned). Yet, if there are other insignificant transactions in the pool that happen ho have a less priority, then this becomes problematic and the submission of the solution might get deferred.
Modules that manually validate transaction might want to have a configurable
Get<u64>as an indicator of how to set the priority. An example would be staking in which the priority of offchain phragmen solutions is better to be configurable.To demonstrate the problem, consider this: currently,
score[0]is the priority, which makes perfect sense if the pool wants to prioritise between 3 transactions of the same type (submit_election_solution_unsigned). Yet, if there are other insignificant transactions in the pool that happen ho have a less priority, then this becomes problematic and the submission of the solution might get deferred.