27 days of Q4 ending
Maybe surprise our dividends arrive as x-mas present.
But i guess not happening
Wallet stuck again, lol.
Since 4 hours
I've been minting and staying on the correct chain with a simple .conf file
maxconnections=25
addnode=ambercoin01.mooo.com
addnode=ambercoin02.mooo.com
addnode=ambercoin03.mooo.com
I'm not solo mining just mining and it seems the peers that are connected to me are mostly on the correct chain also. I think those trying 'connect' and only connecting to one peer are having connection problems. This is a peer to peer network. If you are not talking to your peers how to you think you are going to stay on the correct chain. I've been bouncing around from 17 to 2 connections but mostly around 7~9 connections. Hopefully all your forking settles down. Maybe if you have more peers it will help spread the load across the network. Instead of broadcasting your blocks all down one peer if you broadcasted you solution to 15+ peers maybe you will not fork as much since 15 peers will get you block at the same time to pass to other peers they are connected to. Otherwise trying to jam all traffic down one peer and that peer get full or congested that may cause you to fork off the one peer you are connect to. Remember 'peer to peer' and not all centralized into one node.
So here is an example of what I was asking about. This person has the 3 main nodes in his config file but he has 7-9 connections which means he is connecting to other peers besides the 3 main nodes.
This config file should include:
listen=0
and he should use connect= instead of addnode=
maxconnections is superfluous since connecting to the 3 nodes with listen=0 will result in only 3 connections maximum.
What this tells me is that not everyone is following the instructions that have been posted.
What people need to understand is that during this situation more connections is not a good thing. We want connections to be restricted to the main nodes only.
I understand that this may not solve the problem because there may be another problem in the wallet itself which is causing forks even when these nodes are connected exclusively. But if we fix that problem we still may need to restrict peer connections to the main nodes for a while until the bad forks go away.
In the meantime, I started my wallet last night after forking connecting only to ambercoin01 and ambercoin03 and I have managed to stay on the right fork. I am staking and solo mining.
