This prints the following. I've added commentary on why the name -> id mapping wasn't used.
ids left: {
'ULTIMUSPOOL': 'ultimuspool', # renamed "Ultimus Pool"
'Huobi.pool': 'huobipool', # rename "Huobi Pool"
'Braiins Pool': 'braiinspool', # not yet including Braiins Pool (should be a rename of id=slush)
'MiningKings': 'miningkings', # removed earlier
'tigerpool.net': 'tigerpoolnet', # consolidated with tiger to tigerpool
'PureBTC.COM': 'purebtccom', # not yet added
'KuCoinPool': 'kucoinpool', # renamed to 'KuCoin Pool'
'Entrust Charity Pool': 'entrustcharitypool', # never even mined a block? https://mempool.space/mining/pool/entrustcharitypool
'BTC Pool Party': 'btcpoolparty', # not traced (1PmRrdp1YSkp1LxPyCfcmBHDEipG5X4eJB isn't identificable)
'tiger': 'tiger', # consolidated with tigerpoolnet to tigerpool
'1M1X': '1m1x', # Not an identified mining pool, and not yet tracked https://github.com/0xB10C/known-mining-pools/issues/73
'OKMiner': 'okminer', # renamed to OKMINER
'BTCPool': 'btcpool' # duplicate
}
For https://github.com/mempool/mining-pools/issues/25. These IDs should not be changed as we want to rely on them in links or in databases as identifiers.
I used the mempool-space slugs where available. See the following script:
This prints the following. I've added commentary on why the name -> id mapping wasn't used.