Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Proper Priority for Offchain Phragmen Solution #5532

Description

@kianenigma

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    I4-annoyanceThe client behaves within expectations, however this “expected behaviour” itself is at issue.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions