pool problem with block classification fixed, addet guard for prevent "zero_divide_error at block classification"

If anyone experienced issues running the miner with AVX instructions on Linux, please check the fix. github.com/bitweb-project/cp…

where to trade ? known list of platform where possible trade. komodoplatform.com/en/ dex.gleec.com/ rabid-rabbit.org/account/tra… noirtrade.com/trade?pair=BTE…

ophans fixed , pool online. ( pool was restarted to early ), at future need add guard for this to pool code. but easy to fix at db ) also node updated.

In the next 30 minutes, the pool will update the node, which will take 20 to 40 minutes.

Releases 30.4 and 31.2 have been released. Details: github.com/bitweb-project/bi… github.com/bitweb-project/bi…

The Coinbase reward unlock will occur soon and the logic will return to the standard block reward maturation time of 100. this will happen at block 69400

pool work , miners leave it. Soon it make retarted and diff drop and return to 300s, that is normal. To make retarget need first find block , netowrk cannot fugurate drop diff or rise if new block not found.

Release 31.1 update to Bitcoin upstream 31.x done. github.com/bitweb-project/bi…

Backport release 30.3.1 has been released, containing the latest backported fixes from the 30.x Bitcoin branch. Release 31.1 is currently being compiled. github.com/bitweb-project/bi…

I tested this more than five times, running the entire block period on the test network. Consolidation also kicks in to prevent blocks from getting stuck at more than 500 inputs.

It's not a bug; all balances are already stored within the DB. It's just that once confirmations are received, the entire block period is traversed and the final reward is calculated.

All shares and their calculations relative to blocks are stored in the DB, and as soon as after 69,400, a single payment is made to everyone. It will begin displaying the correct balance for confirmed blocks. This is an artifact of the pool's logic.

Some people asked why the pool doesn't have a Pending Balance. This isn't a bug, it's an effect of extended maturation. The Pending Balance logic is that it only counts confirmed blocks.

Pool is ready pool.bitwebcore.net/

fixed , there was wrong setup api. try again. export from old import to new.

also web wallet is not recomend to use, it's ok use for small amounts , but for large amount use only full node. Old web wallet was very unsecure , like all paper wallets. New fully redone. It now use bip39 , erase key buffers etc.

You need import from old to new your key / or data what you used. old page still work , api is down old. Simple export key and import to new.

Restart officially done. You can download release follow migration instructions at official site / or GitHub. bitwebcore.net/en/blog/bitwe… github.com/bitweb-project/bi… if you used web wallet - import key to new or create new. webwallet2.bitwebcore.net/#/

A snapshot is done this way: on a specific date, a snapshot of blockchain balances is taken, and in the new block chain, all wallets receive to the same address an equivalent at the specified rate.