兄弟连区块链教程open-ethereum-pool矿池源码分析policy模块

open-ethereum-pooleth矿池-policy模块

PolicyServer定义

type PolicyServer struct {
    sync.RWMutex
    statsMu sync.Mutex
    config *Config
    stats map[string]*Stats
    banChannel chan string
    startedAt int64
    grace int64
    timeout int64
    blacklist []string
    whitelist []string
    storage *storage.RedisClient
}

GetBlacklist和GetWhitelist

// Always returns list of addresses. If Redis fails it will return empty list.
func (r *RedisClient) GetBlacklist() ([]string, error) {
    //SMEMBERS eth:blacklist
    //Smembers 命令返回集合中的所有的成员
    cmd := r.client.SMembers(r.formatKey("blacklist"))
    if cmd.Err() != nil {
        return []string{}, cmd.Err()
    }
    return cmd.Val(), nil
}

// Always returns list of IPs. If Redis fails it will return empty list.
func (r *RedisClient) GetWhitelist() ([]string, error) {
    //SMEMBERS eth:whitelist
    //Smembers 命令返回集合中的所有的成员
    cmd := r.client.SMembers(r.formatKey("whitelist"))
    if cmd.Err() != nil {
        return []string{}, cmd.Err()
    }
    return cmd.Val(), nil
}

IsBanned

func (s *PolicyServer) IsBanned(ip string) bool {
    x := s.Get(ip)
    return atomic.LoadInt32(&x.Banned) > 0
}

func (s *PolicyServer) Get(ip string) *Stats {
    s.statsMu.Lock()
    defer s.statsMu.Unlock()

    if x, ok := s.stats[ip]; !ok {
        x = s.NewStats()
        s.stats[ip] = x
        return x
    } else {
        x.heartbeat()
        return x
    }
}

func (s *PolicyServer) NewStats() *Stats {
    x := &Stats{
        ConnLimit: s.config.Limits.Limit,
    }
    x.heartbeat()
    return x
}

处理ApplyMalformedPolicy

//应用格式错误的策略
//malformedLimit为5次
func (s *PolicyServer) ApplyMalformedPolicy(ip string) bool {
    x := s.Get(ip)
    n := x.incrMalformed()
    if n >= s.config.Banning.MalformedLimit {
        s.forceBan(x, ip)
        return false
    }
    return true
}

func (x *Stats) incrMalformed() int32 {
    return atomic.AddInt32(&x.Malformed, 1)
}

func (s *PolicyServer) forceBan(x *Stats, ip string) {
    //没启用Banning或在白名单
    if !s.config.Banning.Enabled || s.InWhiteList(ip) {
        return
    }
    atomic.StoreInt64(&x.BannedAt, util.MakeTimestamp())

    //x.Banned赋值为1
    if atomic.CompareAndSwapInt32(&x.Banned, 0, 1) {
        //"ipset": "blacklist",
        if len(s.config.Banning.IPSet) > 0 {
            s.banChannel <- ip
        } else {
            log.Println("Banned peer", ip)
        }
    }
}

处理ApplyLoginPolicy

func (s *PolicyServer) ApplyLoginPolicy(addy, ip string) bool {
    if s.InBlackList(addy) {
        x := s.Get(ip)
        s.forceBan(x, ip)
        return false
    }
    return true
}

func (s *PolicyServer) InBlackList(addy string) bool {
    s.RLock()
    defer s.RUnlock()
    return util.StringInSlice(addy, s.blacklist)
}

处理ApplyLoginPolicy

func (s *PolicyServer) ApplySharePolicy(ip string, validShare bool) bool {
    x := s.Get(ip)
    x.Lock()

    if validShare {
        x.ValidShares++
        if s.config.Limits.Enabled {
            //Increase allowed number of connections on each valid share
            //每个有效share可以增加的连接数
            //"limitJump": 10
            x.incrLimit(s.config.Limits.LimitJump)
        }
    } else {
        x.InvalidShares++
    }

    totalShares := x.ValidShares + x.InvalidShares
    //Check after after miner submitted this number of shares
    //30个shares后检查
    //"checkThreshold": 30,
    if totalShares < s.config.Banning.CheckThreshold {
        x.Unlock()
        return true
    }
    validShares := float32(x.ValidShares)
    invalidShares := float32(x.InvalidShares)
    x.resetShares()
    x.Unlock()

    //无效share比例
    ratio := invalidShares / validShares

    // Percent of invalid shares from all shares to ban miner
    //"invalidPercent": 30,
    if ratio >= s.config.Banning.InvalidPercent/100.0 {
        s.forceBan(x, ip)
        return false
    }
    return true
}

//加
func (x *Stats) incrLimit(n int32) {
    atomic.AddInt32(&x.ConnLimit, n)
}

//reset
func (x *Stats) resetShares() {
    x.ValidShares = 0
    x.InvalidShares = 0
}

处理ApplyLimitPolicy

func (s *PolicyServer) ApplyLimitPolicy(ip string) bool {
    if !s.config.Limits.Enabled {
        return true
    }
    now := util.MakeTimestamp()
    //"grace": "5m",
    if now-s.startedAt > s.grace {
        //减1
        return s.Get(ip).decrLimit() > 0
    }
    return true
}

func (x *Stats) decrLimit() int32 {
return atomic.AddInt32(&x.ConnLimit, -1)
}

处理BanClient

func (s *PolicyServer) BanClient(ip string) {
    x := s.Get(ip)
    s.forceBan(x, ip)
}

原文地址:http://blog.51cto.com/12918475/2298716

时间: 2024-10-09 10:46:21

兄弟连区块链教程open-ethereum-pool矿池源码分析policy模块的相关文章

兄弟连区块链教程open-ethereum-pool矿池源码分析unlocker模块

兄弟连区块链教程open-ethereum-pool以太坊矿池源码分析unlocker模块open-ethereum-pool以太坊矿池-unlocker模块 unlocker模块配置 json"unlocker": {????"enabled": false,????"poolFee": 1.0,????"poolFeeAddress": "",????"donate": true,?

区块链教程btcpool矿池源码分析StratumServer模块解析

兄弟连区块链教程btcpool矿池源码分析StratumServer模块解析 核心机制总结 接收的job延迟超过60秒将丢弃 如果job中prevHash与本地job中prevHash不同,即为已产生新块,job中isClean状态将置为true????* true即要求矿机立即切换job 三种情况下将向矿机下发新job:???? 收到新高度的job???? 过去一个job为新高度且为空块job,且最新job为非空块job????* 达到预定的时间间隔30秒 最近一次下发job的时间将写入文件(

兄弟连区块链教程btcpool矿池源码分析BlockMaker模块解析

btcpool矿池-BlockMaker模块解析 核心机制总结 blkmaker可以连多个bitcoind节点 blkmaker监听和接收4类消息:RAWGBT.STRATUM_JOB.SOLVED_SHARE和NMC_SOLVED_SHARE 监听RAWGBT目的为获取gbtHash/交易列表,用于构建Block,gbtHash和vtxs写入rawGbtMap_??* rawGbtMap_保存最近100条gbtHash/vtxs对 监听STRATUMJOB目的为获取jobId/gbtHash,

兄弟连区块链教程open-ethereum-pool矿池源码分析payouts模块

open-ethereum-pooleth矿池-payouts模块 PayoutsProcessor定义 type PayoutsProcessor struct { config *PayoutsConfig backend *storage.RedisClient rpc *rpc.RPCClient halt bool lastFail error } GetPendingPayments原理 func (r *RedisClient) GetPendingPayments() []*Pe

兄弟连区块链教程btcpool矿池源码分析JobMaker模块解析

核心机制总结 同时监听kafka KAFKA_TOPIC_RAWGBT和KAFKA_TOPIC_NMC_AUXBLOCK,以支持混合挖矿 接收的Gbt消息,如果与本地时间延迟超过60秒将丢弃,如果延迟超过3秒将打印log 可用的Gbt消息,将以gbtTime+isEmptyBlock+height来构造key写入本地Map,另gbtHash也会写入本地队列 本地gbtHash队列仅保存最近20条,本地gbtMap中Gbt消息有效期:非空Gbt有效期90秒,空Gbt有效期15秒,过期将清除??*

区块链教程open-ethereum-pool矿池源码分析main入口

兄弟连区块链教程open-ethereum-pool矿池源码分析main入口,2018年下半年,区块链行业正逐渐褪去发展之初的浮躁.回归理性,表面上看相关人才需求与身价似乎正在回落.但事实上,正是初期泡沫的渐退,让人们更多的关注点放在了区块链真正的技术之上. open-ethereum-pool以太坊矿池-main入口 命令行启动 ./build/bin/open-ethereum-pool config.json config.json配置文件 { ????"threads": 2,

兄弟连区块链教程open-ethereum-pool矿池源码分析环境安装

安装Geth //安装parity cd /tmp/ wget d1h4xl4cr1h0mo.cloudfront.net/v1.8.11/x86_64-unknown-linux-gnu/parity_1.8.11_ubuntu_amd64.deb dpkg -i parity_1.8.11_ubuntu_amd64.deb //安装screen apt-get update apt-get -y install screen //启动parity screen parity --base-p

兄弟连区块链教程btcpool矿池源码分析核心机制总结及优化思考

btcpool矿池-核心机制总结及优化思考 核心机制总结 ①gbtmaker 监听Bitcoind ZMQ中BITCOIND_ZMQ_HASHBLOCK消息,一有新块产生,将立即向kafka发送新Gbt 另默认每5秒间隔(可从配置文件中指定)主动RPC请求Bitcoind,获取Gbt发送给kafka Gbt消息大小约2M,含交易列表 ②jobmaker 同时监听kafka KAFKA_TOPIC_RAWGBT和KAFKA_TOPIC_NMC_AUXBLOCK,以支持混合挖矿 接收的Gbt消息,如

兄弟连区块链教程open-ethereum-pool矿池源码分析API分析

ApiServer相关定义 type ApiConfig struct { Enabled bool `json:"enabled"` Listen string `json:"listen"` StatsCollectInterval string `json:"statsCollectInterval"` HashrateWindow string `json:"hashrateWindow"` HashrateLarge