WORKERBEE and BEE update

Words
102
Reading
1 min
Listen
Play
6y

Just now I submitted a custom json to enable a mining pool for BEE from WORKERBEE.

{ "id": "ssc-mainnet-hive", "json": { "contractName": "mining", "contractAction": "createPool", "contractPayload": { "lotteryWinners": 10, "lotteryIntervalHours": 1, "lotteryAmount": "10", "minedToken": "BEE", "tokenMiners": [ { "symbol": "WORKERBEE", "multiplier": 1} ] } } }

This is an important step from moving off of scotbot for the miner and instead to the mining smart contract that eonwarped@eonwarped recently made live.

That said, BEE is special as it's issuance is determined not by the hive-engine@hive-engine account but it's part of the contract and issued by null@null. So, we'll have to do additional work before this is made live, but wanted to clarify what you're seeing and what we're doing.

WORKERBEE distribution of BEE will be trustless and handled by the smart contract.

WORKERBEE and BEE update | Ecency