Question about Forks
piezo last edited by
Hi, i just wonder, who/what defines which Blockchain is the "correct" one and which is the "fork" when let´s say half of the network go on a fork?
For Example here is the Situation right now:
These Pools are at Block 259400
- My local Wallet
This Pool is at Block 259379
This Pool is at Block 259374
So burst.ninja has a lot of mining-power (maybe nearly half of the network?). Is the mining-power for the blockchain defines which one is the correct one? Or the number of wallets mining the same Blockchain? Or maybe something different? Iam a bit confused.
Normally the longer and stronger chain wins.
If ninja runs away and the other pools and solo miners don't agree - we pause ninja for a while.
The situation at the moment is not optimal - we all know that. That's why we try to help the community to run their own pools to spread the power.
- We are tweaking the setup and wallet code that forks won't happen (so often) anymore.
- We are spreading the hashpower so ninja is not so important anymore
FrilledShark last edited by
It is the blockchain with most work put into its blocks. Most of the times it works by just looking at the length. There is some exceptions, but you can mostly ignore them if it is about short term forks
http://188.8.131.52:8121 isn't on a fork, it just slow to update the blockchain, might be because it has some bad peers or is missing some cpu power to validate the block or something.
piezo last edited by piezo
But what about reconfigure the pools to the following Plotsize:
- Then block every miner from using a pool whos plotsize doesnt fit in the size recommondation +-5%
- Smaller Miners could also consider mining on pool.burstcoin.de, burst.mininghere.com and some hopefully coming new pools like this https://forums.burst-team.us/topic/945/new-pool-is-open-http-burstpool-ddns-net-8080/3 .
- Miners with plots > 50TB should use solo-mining for now until the situation is fixed and some more pools are available.
So its just an idea from someone hows new to burst and iam sure there are better ones out there,. But with all this pool-problems something should happen to not damage the image of burst because of "instability".
@piezo We've already done the different size pools. Auto block we can't do, but I'll manually block any miner trying to abuse one of the smaller pools.
maxpayne1256 last edited by
The devV2 pool seems to be broken. The targetheight is changing rapidly up and down since this morning