BSC验证者管理：BSCValidatorSet与StakeHub的协作关系

BSC验证者管理：BSCValidatorSet与StakeHub的协作关系

概述

在BSC（BNB Smart Chain）中，验证者的管理采用了分层设计。BSCValidatorSet负责底层共识的验证者集合管理，而StakeHub则提供了更高层的验证者治理功能。这种设计既保证了共识的稳定性，又提供了灵活的验证者管理机制。

架构设计

1. 分层职责

• BSCValidatorSet：

• 作为共识层的接口合约

• 维护当前活跃的验证者集合（currentValidatorSet）

• 处理验证者的奖励分发

• 负责验证者集合的原子更新

• StakeHub：

• 管理验证者的完整生命周期

• 处理质押和委托逻辑

• 计算验证者的投票权重

• 提供验证者选举信息

2. 数据流转过程

3. 关键功能实现

验证者创建（StakeHub）

 

function createValidator(
    address consensusAddress,
    bytes calldata voteAddress,
    bytes calldata blsProof,
    Commission calldata commission,
    Description calldata description
) external payable whenNotPaused notInBlackList {
    // 基本检查
    address operatorAddress = msg.sender;
    if (_validatorSet.contains(operatorAddress)) revert ValidatorExisted();
    
    uint256 delegation = msg.value - LOCK_AMOUNT; // 创建验证者需要锁定1 BNB
    if (delegation < minSelfDelegationBNB) revert SelfDelegationNotEnough();

    // 部署质押合约
    address creditContract = _deployStakeCredit(operatorAddress, description.moniker);

    // 添加验证者信息
    _validatorSet.add(operatorAddress);
    consensusToOperator[consensusAddress] = operatorAddress;
    voteToOperator[voteAddress] = operatorAddress;

    emit ValidatorCreated(consensusAddress, operatorAddress, creditContract, voteAddress);
}

验证者信息获取（StakeHub）

 

 

function getValidatorElectionInfo(
    uint256 offset,
    uint256 limit
) external view returns (
    address[] memory consensusAddrs,
    uint256[] memory votingPowers,
    bytes[] memory voteAddrs,
    uint256 totalLength
) {
    totalLength = _validatorSet.length();
    if (offset >= totalLength) {
        return (consensusAddrs, votingPowers, voteAddrs, totalLength);
    }

    limit = limit == 0 ? totalLength : limit;
    uint256 count = (totalLength - offset) > limit ? limit : (totalLength - offset);
    consensusAddrs = new address[](count);
    votingPowers = new uint256[](count);
    voteAddrs = new bytes[](count);
    for (uint256 i; i < count; ++i) {
        address operatorAddress = _validatorSet.at(offset + i);
        Validator memory valInfo = _validators[operatorAddress];
        consensusAddrs[i] = valInfo.consensusAddress;
        votingPowers[i] = valInfo.jailed ? 0 : IStakeCredit(valInfo.creditContract).totalPooledBNB();
        voteAddrs[i] = valInfo.voteAddress;
    }
}

验证者集合更新（BSCValidatorSet）

function updateValidatorSetV2(
        address[] memory _consensusAddrs,
        uint64[] memory _votingPowers,
        bytes[] memory _voteAddrs
    ) public onlyCoinbase onlyZeroGasPrice {
        uint256 _length = _consensusAddrs.length;
        Validator[] memory _validatorSet = new Validator[](_length);
        for (uint256 i; i < _length; ++i) {
            _validatorSet[i] = Validator({
                consensusAddress: _consensusAddrs[i],
                feeAddress: payable(address(0)),
                BBCFeeAddress: address(0),
                votingPower: _votingPowers[i],
                jailed: false,
                incoming: 0
            });
        }

        // step 0: force all maintaining validators to exit `Temporary Maintenance`
        // - 1. validators exit maintenance
        // - 2. clear all maintainInfo
        // - 3. get unjailed validators from validatorSet
        (Validator[] memory validatorSetTemp, bytes[] memory voteAddrsTemp) =
            _forceMaintainingValidatorsExit(_validatorSet, _voteAddrs);

        // step 1: distribute incoming
        for (uint256 i; i < currentValidatorSet.length; ++i) {
            uint256 incoming = currentValidatorSet[i].incoming;
            if (incoming != 0) {
                currentValidatorSet[i].incoming = 0;
                IStakeHub(STAKE_HUB_ADDR).distributeReward{ value: incoming }(currentValidatorSet[i].consensusAddress);
            }
        }

        // step 2: do dusk transfer
        if (address(this).balance > 0) {
            emit systemTransfer(address(this).balance);
            address(uint160(SYSTEM_REWARD_ADDR)).transfer(address(this).balance);
        }

        // step 3: do update validator set state
        totalInComing = 0;
        if (validatorSetTemp.length != 0) {
            doUpdateState(validatorSetTemp, voteAddrsTemp);
        }

        // step 3: clean slash contract
        ISlashIndicator(SLASH_CONTRACT_ADDR).clean();
        emit validatorSetUpdated();
    }

系统启动与演进

1. 初始化阶段

• 创世区块中包含初始验证者集合（INIT_VALIDATORSET_BYTES）

• BSCValidatorSet通过init()函数初始化这些验证者

• StakeHub初始化为空状态

2. 运行阶段

• 新的验证者通过StakeHub的createValidator()函数加入

• 验证者的质押量决定其投票权重

• Parlia定期从StakeHub获取最新的验证者信息

• BSCValidatorSet根据这些信息更新共识层的验证者集合

3. 安全保障

• 即使StakeHub返回空列表，BSCValidatorSet也会保持当前的验证者集合

• 验证者的更新是原子性的，确保共识安全

• 通过质押机制防止恶意行为

优势分析

1. 解耦设计

• 共识层与治理层分离

• 便于升级和维护

• 降低系统复杂度

2. 灵活性

• 可以修改StakeHub的选举规则而不影响共识

• 支持质押和委托等高级功能

• 便于实现治理功能

3. 安全性

• 保证验证者集合永不为空

• 原子性更新确保共识安全

• 多层次的验证者管理机制

总结

BSCValidatorSet和StakeHub的设计体现了BSC在验证者管理上的创新。通过分层设计，既保证了底层共识的稳定性，又提供了灵活的验证者管理机制。这种架构为BSC的可扩展性和安全性提供了坚实的基础。