Skip to main content
Testnet

Update Inactive Penalty Duration to 1 minute

Proposal #3 on Band V3

Band V3 network: Day Nov 7 · Healthy

Typical fee 0.0008 BAND

Overview

Updated

Passed

Voting ended
Mar 27, 2025
Opened Mar 25, 2025
Submitted
Mar 25, 2025
Mar 25, 10:06 UTC
Deposit
1,000 BAND
Type
Oracle parameters and 1 more

Proposed by band1256qq9eh…wgw84f

Votes

  • Yes 34M BAND
  • No 0 BAND
  • No with veto 6 BAND
  • Abstain 0 BAND

Description

Context

This proposal aims to update the inactive penalty duration parameter to 1 minute for both the oracle and bandtss modules. This change will affect how long validators are penalized for inactivity.

Features

  • Shorter Penalty Duration: Reduces the penalty duration to 1 minute from the current duration
  • Enhanced Flexibility: Allows validators to recover more quickly from temporary inactivity

Effects

  • For Validators: Shorter recovery time after periods of inactivity
  • For Network: Maintains security while providing more forgiving conditions for temporary technical issues

What it does

The messages the chain carries out if it passes, as written in the proposal.

  1. Oracle parameters band.oracle.v1 
    {
    "@type": "/band.oracle.v1.MsgUpdateParams",
    "params": {
        "max_ask_count": "16",
        "base_owasm_gas": "50000",
        "max_calldata_size": "4096",
        "sampling_try_count": "3",
        "ibc_request_enabled": true,
        "max_report_data_size": "4096",
        "max_raw_request_count": "16",
        "expiration_block_count": "100",
        "oracle_reward_percentage": "70",
        "inactive_penalty_duration": "60000000000",
        "per_validator_request_gas": "0"
    },
    "authority": "band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"
}
  2. Bandtss parameters band.bandtss.v1beta1 
    {
    "@type": "/band.bandtss.v1beta1.MsgUpdateParams",
    "params": {
        "fee_per_signer": [
            {
                "denom": "uband",
                "amount": "50"
            }
        ],
        "reward_percentage": "10",
        "max_transition_duration": "604800s",
        "min_transition_duration": "86400s",
        "inactive_penalty_duration": "60s"
    },
    "authority": "band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm"
}

How validators voted

A validator's vote counts for its delegators unless they vote themselves. Largest stake first.

Validator Vote When
validator1 Did not vote —
validator2 Did not vote —
validator3 Did not vote —
validator4 Did not vote —
Active Nodes Yes Mar 25, 12:42 UTC
B-Harvest Yes Mar 26, 05:00 UTC
Cosmostation Yes Mar 25, 13:16 UTC
Nansen Yes Mar 26, 05:43 UTC
Stakeflow Yes Mar 25, 13:09 UTC
w3coins Did not vote —
BitNordic Yes Mar 25, 15:43 UTC
0base.vc Yes Mar 25, 11:28 UTC
ContributionDAO Did not vote —
HighStakes.ch Yes Mar 25, 11:31 UTC
Nodes.Guru Yes Mar 25, 12:04 UTC
StakingCabin Yes Mar 25, 18:30 UTC
Citadel.one Did not vote —
node101 Yes Mar 25, 12:12 UTC
Inter Blockchain Services Yes Mar 25, 12:44 UTC
UbikCapital Did not vote —
Stakecito Did not vote —
CosmosSpaces Did not vote —
Forbole Did not vote —
STAKECRAFT Yes Mar 25, 20:16 UTC
stakewolle Did not vote —
Wellstake Did not vote —
StakeTown Yes Mar 26, 14:01 UTC
AtlasNodes Yes Mar 26, 08:31 UTC
LithiumDigital Yes Mar 25, 14:36 UTC
WeStaking Did not vote —
Atlas-Staking Did not vote —
bronbro Did not vote —
InfStones Did not vote —
TTT VN Yes Mar 26, 04:35 UTC
HashKeyCloudValidator1 Yes Mar 27, 09:56 UTC
bandvaloper13p2s…4klq Did not vote —

Estimated: voting ended before BitBasic recorded who could vote, so "Did not vote" is from the validators BitBasic reckons were in the active set then.