Skip to content

Match pallet configuration constants in tests with mainnet #824

@Jinxit

Description

@Jinxit

Currently the pallet constants are kind of all over the place. Some are set to be for tests only, some for benchmarks only, some for testnet only. If the values change in any one of these instances, it's tough to know what needs to be changed elsewhere.

We should narrow these down to be declared in a single location and imported elsewhere. This could be done either with a single set used everywhere or possibly two, with the other variant being used for testing if it's essential for how the tests function.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions