Topic: [ANN][EGC] EverGreenCoin | Environmental Green Causes | Full 7% PoS | Foundation - page 133. (Read 284552 times)

Some more interesting clues, thank you for bringing them to attention.  It would make sense that wallets that are not generating can wonder with peers, but it is a good 'process of elimination' fact to be known that you proved.

Initially I could not find the 10054 error code you mentioned. I then found that in log files of windows wallets. But it only appears the error codes must not be "standardized" across OS's as Linux wallets use code 104. The fact you have not seen this on other coins is, as you say, the worrisome fact. Possibly suggesting some underlying poor communication between nodes. Which may explain a lot here.

Again, thank you for the observations. I will continue to investigate.

Are any exchanges working?

@EverGreenCoin:

This coin is too good to pass up solely because of these fork issues however annoying they might be. You guys will solve this eventually.

More info:

My "good" wallet that had staking disabled and I haven't mining with/to it also forked again at block 461516.

So now I know nodes can wander off to wrong forks even without any form of coin generation.

It basically stopped syncing and shows that it's 203 blocks behind but that's just keep increasing as blocks are being generated on the correct fork.


Checking the debug.log I have plenty of this:

received block 000000272a378005f92d
Misbehaving: 149.202.49.99:5757 (0 -> 100) DISCONNECTING
disconnecting node egc-seed5.granitecoin.com
ERROR: ProcessBlock() : block with too little proof-of-work

And a ton of these from even before the fork:

trying connection egc-seed1.granitecoin.com lastseen=0.0hrs
connected egc-seed1.granitecoin.com
send version message: version 70000, blocks=461605, us=0.0.0.0:0, them=51.254.216.25:5757, peer=51.254.216.25:5757
socket closed
disconnecting node egc-seed1.granitecoin.com

and:

trying connection egc-seed5.granitecoin.com lastseen=0.0hrs
connected egc-seed5.granitecoin.com
send version message: version 70000, blocks=461660, us=0.0.0.0:0, them=149.202.49.99:5757, peer=149.202.49.99:5757
socket recv error 10054
disconnecting node egc-seed5.granitecoin.com


These socket closings are suspicios to me. I don't have that for other coins and as I mentioned earlier these are happening even if I'm on the right fork.

Forgot to mention bootstrap+resynch worked fine.

Ok, this is good info and I thank you for taking the time to do the forensics to uncover it, summarizing, and sharing it. The seednodes on granite's network have not been perfectly immune to the incorrect forks but, we are very diligently watching all seednodes and bringing them off the network quickly if they do wonder. I too thank crysx and the fact these occurrences do seem to be less and less. We were on a roll with them specifically, up until a few hours ago.

I noticed perhaps the same fork you mentioned half a day+ ago. I was mining to the faucets wallet witch actually was/is staking the small amount it holds. When I noticed the nethash and difficulty sharply decrease and sure enough, fork. I will follow your example and disable staking when mining. I did not take not of what peers it had before a began its all to familiar resync routine. On that note and because of that, a more recent (block height 460949) bootstrap has been made available should anyone be in need of it.

Yes, I do not think it will reorganize hundreds of blocks. I have seen the same as you described. The most I have seen it reorganize is ~60 blocks, which I just witnessed a reorganization of just over 40. Thank you for fortifying only the correct blockchain.

Thank you to all of you that have been going threw this ordeal with little complaint. Those who have had much complaint, I do understand your frustration and cannot say I blame you for your words, however harsh. A hopefully final resolution is in the works. Please continue to bear with us. Once it is ready to test, it will take much testing and then, compiled for everyone.

The block explorer is now back online also. Again, sorry for that outage.

Some more info to potentially help figure out the problem:

I resynced from scratch two different wallets on different computers and networks and forced both wallets to only use crysx's granitecoin nodes (thanks crysx) because they seem to be always on the right fork.

One wallet for staking, one for mining (staking disabled).

About half a day ago the staking wallet forked. Okay, I resynced it and disabled staking and it's working fine since. We'll see if it wanders off without staking and mining (unlikely).

And now, a few hours ago the other wallet I was mining to forked. The forked wallet is still connected to the same nodes as the one on the correct chain and the forked wallet says it's synced while it's several hundred blocks off and it's staying there for hours. The debug.log says I get disconnected from the nodes periodically with socket recv error 10054 but it reconnects prompty anyway. Note that same error is happening just as frequently on the "good" wallet.

I could still mine and advance the wrong fork while it's connected to the "good nodes". I get that it should eventually make its way back on the right fork but I'm not sure if that's a good idea instead of refusing connections to wrong forks because it doesn't seem to get back there especially after hundreds of blocks on the forked chain.

Either way, I've never seen anything like this before.

I need to bring down the explorer for maintenance.

Sorry for the outage of the explorer and the inconvenience.

with regards to knowing where you are at - in linux its easy ... windows is a little more complicated to keep track of ...

in linux ...

find the debug log file - which is normally ~/.evergreencoin/debug - and tail ( or mutlitail ) it ...


or ...


in windows ...

find the debug log file and do a similar thing - though windows does not have ve a tail or mutlitail application that i know of ... but you can view the debug.log file - and keep checking it every so often ...

the file will be found in your EverGreenCoin folder where your wallet.dat is located also ...

this debug.log contains ALL the details that the wallet / daemon needs ... do NOT look at it as an issue if there are - errors and disconnections and banning ip etc - this is normal functionality of the wallet / daemon - and the debug.log file is for us that require it to see what is happening so that we can 'debug' any issue that may arise ...

i hope this helps further ...

btw - the latest hash check i have in all seeds are ...


this of course is in linux - so do what you do for your own method of finding the block hash - either through the wallet or daemon ...

i have mine as an executable and service in linux - so i dont have the './' - and dont need it to check ... but mine is not a normal installation either ...

#crysx

Be certain to delete your peers.dat file so that you get all new peers from the seednodes. Also, remove any addnodes's you may have previously added to the ervergreencoin.conf file.
 
You can delete the peers.dat file while it is still bootstrapping, as it has yet to read the file.

Yes, like bathrobehero mentioned, watch the file size of blk0001.dat to see the progress. It can take up to 2 hours or longer depending on the system and its availability of resources.

Thank you for taking the time to upgrade and resync.

If you really want to know, you can see where you're at by looking at the size of the blk0001.dat file in your EverGreenCoin directory where your wallet file is.

It will keep increasing in size and until it reaches about the same size as the bootstrap file, at which point it's done.



@EverGreenCoin: you're right and thank you for the explanation.

oops.. ive been lazy and busy.
Didnt update to latest wallet.. so yesterday it seems i went unsynched.

Downloaded the latest version, and the bootstrap.

Started the loading now.
If there is any posibility to incorporate a indicatior of progress on boostrap-loading, that would be helpful.
Im guessing many just assume everything has hung when its acting like it is while loading bootstrap.

hi guys,

dev and communities still continue to work on this coin.

the simple design banners for OP and paper wallet. green.. green.. greeeennn...  .

When the problems with forking have been solved, I think it would be wise to have a look into giving Evergreen a renewable energy face like eg. Solarcoin or Greencoin are doing.
I think a good example is this one https://steemit.com/solar/@ihashfury/my-favourite-crypto-miner.
Just my 2 EGC

wish i could give a thumbs up or even a high five on some of these positive and true comments today. im there till the end to things happen but what makes it better is when we get together figure out the problem and help others get on the same page then we overcome. things might be hard these things are not easy if you stressed or mad there is an anger bar in the bottom right corner at http://evergreencoin.proboards.com/ have at it. other than that hey its life things happen suck it up buttercup get up brush yourself off and keep going giving up is not an option thats for the weak the strong pull together.

Green is the color of Hope. There are hard times, no doubt, but i'll be supporting this coin and this project since its end, like a miner and investor. Come on!

very nice join free

Yes, I had hoped enough would willingly upgrade to not make a mandatory upgrade and lockout needed. These and other options are being explored.

Thank you for your input GizFreak. It is welcome and appreciated.

Thanks joinfree! 

why should i give my knowledge into a shitty-coin like EGC ?
It will die within the next weeks ...
Think due the next fork more people lost money with it (not due trading) and think like me ...

I took a look at your sig stating: crypto helping others, so maybe help instead of complaining?