GenesisValidator doesn't have `minimum_delegation_amount` and `maximum_delegation_amount`.

[zie1ony]

In tests we use GenesisConfigBuilder to setup validators. It should be possible to define minimum_delegation_amount and maximum_delegation_amount. Right now it forces us to use add_bid. It would be much easier if we don't have to build and execute add_bid.wasm for every validator on every test context setup.

[devendran-m]

Internal Jira ticket CORE-129 created to address this requirement.

[zie1ony]

We also discovered that the validators set up in the genesis in the testenv don't set minimum_delegation_amount to the value from the chainspec. It is 0 instead.

[devendran-m]

We also discovered that the validators set up in the genesis in the testenv don't set minimum_delegation_amount to the value from the chainspec. It is 0 instead.

Thanks @zie1ony , for identifying and highlighting this.
cc: @mpapierski

[devendran-m]

Reference -

casper-node/storage/src/system/genesis/account_contract_installer.rs

Lines 328 to 329 in 32100b0

	0,
	u64::MAX,

[devendran-m]

We also discovered that the validators set up in the genesis in the testenv don't set minimum_delegation_amount to the value from the chainspec. It is 0 instead.

According to the L1 discussion on July 3, 2025, a bug JIRA ticket CORE-138 has been raised to address the above issue.