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

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/

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.

Old coins don't go anywhere, there's no need to send them anywhere, or do anything with them.

Max Future Block time 600s Mining Algo argon2id tcost = 3 , mcost = 1024 , lanes = 1 , threads = 1. To migrate, it will be enough to place a copy of the old wallet.dat in the new node and do sync - rescan.

Snapshot date 03.06.2026 00:00 UTC Swap will be old 100:1 to New blockchain. ~ Public Node Release 4 - 6. Final Blockchain Settings Based at BTC 0.30.2 source code. Block Time: 300s Halving Period: 420000 Max amount: 42 000 000 Diff algo: LWMA with window 576

Upcoming Snapshot & New Codebase Migration Distribution: All holders will automatically receive coins on the new chain at a 100:1 ratio (e.g., 100 old = 1 new). Technical Specs: 5m block time | 420,000 halving | 46M max supply.