Skip to main content
Testnet

BCIP-2: Establish a TSS Group

Proposal #2 on Band V3

Band V3 network: Day Nov 7 · Healthy

Typical fee 0.0008 BAND

Overview

Updated

Passed

Voting ended
Jan 31, 2025
Opened Jan 29, 2025
Submitted
Jan 29, 2025
Jan 29, 04:11 UTC
Deposit
1,000 BAND
Type
Transition group

Proposed by band1256qq9eh…wgw84f

Votes

  • Yes 32M BAND
  • No 0 BAND
  • No with veto 0 BAND
  • Abstain 0 BAND

Description

Context

This proposal aims to establish a Threshold Signature Scheme (TSS) group under the bandtss module on BandChain, consisting of 8 members with a threshold of 4 signatures required to validate and sign messages. This will enhance security, decentralization, and resilience in the network.

Features

  • Decentralized Signing: Authority is distributed among 8 members, preventing single-point control.
  • Threshold Security: 4 signatures are required for validation, ensuring robustness.
  • Enhanced Resilience: Redundancy allows the signing process to continue even if some members are unavailable.

Effects

  • For TSS members: Members earn fees for their participation and signing.
  • For users: Users can request message signing, enabling secure cross-platform data verification.

What it does

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

  1. Transition group band.bandtss.v1beta1 
    {
    "@type": "/band.bandtss.v1beta1.MsgTransitionGroup",
    "members": [
        "band1dj2z0757yzadyu5ccp7gs5kguaddseu5qql83v",
        "band145fpqhwwqmadwpevzsllvh56ned65dnx2szly9",
        "band10w8ly6geqv5dsy7eswtrhsewy7s0fq7xvuy8wd",
        "band13vygjq9wx99z7vynwuyfd5906wnt4hfhwhlxxt",
        "band1uu9ajlendcxzem8hdkfac40pl9umekamz8w67q",
        "band1724v58tp3r438z4n63d3rlvlzqwag83sr9zsta",
        "band14t9uk7gdnk529fmsyynw7fnwqxym6z89e9azhj",
        "band1qavtnc5lgev8t9c0kux2qkcylelsx3453xxy29"
    ],
    "authority": "band10d07y265gmmuvt4z0w9aw880jnsr700jrdn8wm",
    "exec_time": "2025-02-03T07:00:00Z",
    "threshold": "4"
}

How validators voted

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

Validator Vote When
validator1 Yes Jan 29, 04:37 UTC
validator2 Yes Jan 29, 04:39 UTC
validator3 Yes Jan 29, 04:39 UTC
validator4 Yes Jan 29, 04:39 UTC
Active Nodes Yes Jan 29, 08:17 UTC
B-Harvest Yes Jan 29, 08:48 UTC
Cosmostation Did not vote —
Nansen Did not vote —
Stakeflow Did not vote —
w3coins Did not vote —
BitNordic Did not vote —
0base.vc Did not vote —
ContributionDAO Did not vote —
HighStakes.ch Did not vote —
Nodes.Guru Did not vote —
StakingCabin Did not vote —
node101 Did not vote —
Inter Blockchain Services Did not vote —
UbikCapital Did not vote —
Stakecito Did not vote —
CosmosSpaces Did not vote —
Forbole Did not vote —
STAKECRAFT Did not vote —
stakewolle Did not vote —
Wellstake Did not vote —
StakeTown Did not vote —
WeStaking Did not vote —
Atlas-Staking Did not vote —
armhub Did not vote —
Smart Stake Did not vote —
InfStones Did not vote —
TTT VN Did not vote —
Antrix Validators 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.