Governed parameters

Every network policy and economic value of Tenzro Network is a governed parameter: fees and the fee market, minimum bonds for each role, slashing rates, unbonding periods, SLA penalties, duty rewards, sponsorship limits and the voting rules themselves. Each one:

• starts at its genesis value, written into chain state at block 0;
• is read from chain state by every node, so all nodes apply the same value;
• changes only through an enacted parameter_change proposal. No admin method, CLI flag or node configuration sets one.

Reading them

tenzro governance params --rpc https://rpc.tenzro.com
tenzro governance params --key settlement.reconciliation_reward --rpc https://rpc.tenzro.com

tenzro_getNetworkParams returns every parameter, or one with {"key": "..."}, with its current value, its bounds, its genesis value, the direction that tightens it and any enacted change still waiting for its epoch. Values are decimal strings, since several exceed what a JSON number holds exactly. The MCP tool is get_network_params.

Changing one

tenzro governance propose-param --key settlement.reconciliation_reward --value <VALUE> --memo "Why the change"

1. Submission. A key that is not a governed parameter, or a value outside its bounds, is refused when the proposal is submitted.
2. Vote. The proposal is decided on the standard track by the voting rules in force when it opened. A change to the rules enacted while a proposal is open never moves that proposal's window, timelock or threshold.
3. Enactment. After the timelock the change applies at the next epoch. A change that tightens a requirement, such as a higher minimum bond, waits out a grace window first, so an operator who met the old value keeps serving while they top up.

See Governance for tracks, quorums and guardians.

Methods