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

I'm not doing any development anymore as it was getting too much work for me as the only remaining dev.
Now I just do some graphic and webdesign stuff for the sake of my own pleasure and at my own pace.

the loss isn"t by selling... this is by lost EGC Coins not refunded, Rig-Rental, Rootserver-Rental.

This coin is a shitty buggy coin !

agreed ...

it seems to be the best way to work - so if steven is willing do so - he will ...

are you now retired from coding? ... or still at it? ...

we have been looking at the coins we now have in arsenal of projects - and rebasing granite ( and eventually ozziecoin - ozc ) is not going to be an easy task ... these issues with forks are not helping our time frames either ...

but hopefully - it will be put to bed soon ... especially if there is expert help around - experienced in such issues ...

#crysx

A mandatory update with the lockout of previous versions, is the best you can do in a situation like this indeed.
When I was active as a dev for ANTI we had the same problem and we managed to get everyone on the right chain by doing it that way.
Not nice for people that have an old version of the wallet, but it's inevitable imo.

all the hardcoded seeds mate - at least i can speak on behalf of the granite ones ... they are all on the right chain ...

just compile the latest git and bootstrap it ...

as for the community - the amount of previous version wallets being used amazes me ...

we have compiled the latest windows wallets for all to download ( no osx ones yet ) - and linux / daemon users compile their own from the uptodate git - and yet the versions that show on most of the seeds are early versions ...

the next version of the update to the code should ( and probably will ) include a mandatory update that will change a few things - including a lockout of previous versions for the sake of the blockchain and all this forking - yes i meant that as a pun also ...

if everyone complies and updates the wallet - there is less risk of it forking ... not a complete guarantee - but NO wallet is guaranteed that ...

we are doing a LOT behind the scenes - and as im not as eloquent as steven when addressing these issues - i will say that those who want to dump and leave have every right to - as much as those who want to stay and stick it out in this rough time ...

this is NOT an exact science - so be patient ... thats all ...

if not - there are so many other coins that will take your money and rip you senseless for that money ... many many many out there ... some are legitimate projects - as is this one - with people who give a damn about not only the code and coin and project - but about the community and what needs to be done to minimize the issues that arise - to make it a less bumpy ride FOR the community ...

steven might not say it - and probably wont like me saying it - but stop stressing and bear with us ... but moreso - work with us ... update those damned wallets ... or - dont bother - it really is up to you ...

we will still be here - working on it ...

#crysx

AikaPool already forked!

What nodes have the correct blockchain?

Just remember everyone... the definition of failure is giving up.

Portdavenport

Bathrobehero, sorry for the slow response. I had to step away from my desk for a few hours for a family obligation I could not bring myself to miss.

I do believe the block explorer can be trusted and is on the correct chain as it does concur with the 2 seednodes (seed & seed2.evergreencoin.org) I have full access to. I am very eagerly awaiting crysx to come online so investigation can continue to his seednodes. He is 13 hours ahead of me and did have to sleep last night.

The coin will correct from forks, in some cases. As you can see this wallet (v1.2.1) 4 days ago doing so. Note how it had an incorrect block hash for 447617, but then is corrected:


More recently, here is an example of the same, but taking 5 minutes to correct, on block 457996:


Both the qt wallet and daemon both appear to hang while doing this reorganization and may appear to not be syncing for several minutes. This may have been what you observed.

I have been in communication with Mammix, the creator of the code from which EGC was cloned, several times recently. He did agree the code improvements would help mitigate forks and also was the one that recommended I add BIP66, which I have. Yes I agree they are coming from PoS blocks as you said. Mammix has agreed to set aside some time for me tomorrow morning. I will wait for him to wake. He is 5 hours ahead of me.

I do understand yours and everyone's frustration. I will do everything necessary to get the blockchian secure from forks.

EDIT: Crysx has risen from his slumber and yes, the block explorer does concur across all EGC seednodes including those on the granite network.

Aaaaand I have forked again...

These things doesn't just happen to all coins, far from it.

And it wasn't caused by a new wallet, it's just happened all of a sudden.
Either the coin can't handle forks for some reason (checkpoints are useless in this case) or the coin is being attacked in some way. If that is the case I'm 90% sure it's because of proof of stake.

I love this coin and own a bunch of it but this is getting kind of ridiculous. I think if the dev can't fix it we might need to fund getting outside help.

Edit: I have two wallets running on two different PCs with different IPs, one for staking and one for solomining. Now both of them forked off - or at least it seems this way because none of them want to sync.
Edit2: None of them forked (I hope, getblockhash 459170 - 00000000b7962f650d5a4d58921c4cf71bdcdd2484bc7b966210864910f821df) but both of them stopped syncing with plenty of connections at different block heights.
Only multiple restarts started syncing them again.
Edit3: If the block explorer can be trusted I am on a fork with both of my clients (they are not connected to each other).

Still seeing some v1.0.0 wallets in my peers list as well which may be causing some issues...

50.33.142.137
66.176.24.142
209.188.18.52
144.76.236.8

Haven't forked again here since the initial fork and compiling the new wallet and re-syncing...

Sorry to say, but those things happen from time to time, no matter what coin.
Btw how can you judge on such a theme with a fresh account like that?
You better leave technical stuff to people with more experience and the money you lost, for me, is because of your weak hands. Nothing less, nothing more.
See it as a good lesson to not sell too early.

don't believe that it is an attack at your coin ...
think it is buggy, no more no less ...

give it up, you will only burn your money with this shitcoin !

Never ever mine or trade this shit again !

I am also experiencing the same thing with you , it's just that I still hold and hope shit this coin could refund my money immediately

Thanks for the wish of luck and the follow!

Good luck to your team. Following twitter now

Some oddities were observed 14 hours ago, difficulty abruptly jumping from 2 to 12 and then back down, before any forks were reported to be found. This does make me suspect the forks may have been from malicious attempts to attack the EverGreenCoin network. However they may have been caused, I apologize.

This block hash you mentioned does concur with all the seednodes and the block explorer.

EDIT: Perhaps the many Windows wallets running the v1.1.2 code because the upgrade to v1.2.1 had yet to be made available formed a consensus and pulled other nodes into an incorrect fork.

I forked twice since my last comment and it's clearly not just me.


getblockhash 458553
000000006b5d12bbbd16654648bfa6eb05bbab925b512aac597191920699cb21

The EverGreenCoin v1.2.1 Windows wallet has been thoroughly tested and is now available for download:
https://mega.nz/#!kkFWHLZC!EvFpstFoMK5G-ZNGlCjV4mwrxvusPNH22jBmatyjp2A

Upgrading your Windows EverGreenCoin wallet to this version 1.2.1 is very strongly advised as it has many improvements that will mitigate the forking problems that the network has suffered. When doing any wallet upgrade it is advised to protect your coins by making a backup of them. To do this you simply need to backup the EverGreenCoin wallet.dat file.

Your wallet.dat file can be found on Windows within %APPDATA%\EverGreenCoin\ or otherwise stated, C:\Users\YOUR USERNAME HERE\AppData\Roaming\EverGreenCoin\
On Mac OS X it can be found within /Users/YOUR USERNAME HERE/Library/Application Support/EverGreenCoin/
On Linux it can be found within ~/.evergreencoin/ or otherwise stated, /home/YOUR USERNAME HERE/.evergreencoin

Simply copy the wallet.dat file to another location you feel is a safe place. For example; your desktop, a removable storage device, or elsewhere on your network. Chances that you will need this backup after the upgrade are small but, the wallet.dat file contains all your EverGreenCoins. It is the best practice to make the backup copy of your wallet.dat before starting the upgrade and is strongly advised.

To perform the actual upgrade is easy. You simply need to run the new version 1.2.1 EverGreenCoin wallet instead of your prior version.

If you need assistance, please feel free to post in this thread, personal message myself or another team member, or seek help in real-time in the IRC. If you do choose the latter, please ask or describe your concern or issue when you enter the room. Please be patient for a response as other people may have stepped away from their keyboards. Someone will help you as soon as possible.

Thank you in advance for taking the time to upgrade to version 1.2.1 as doing so will help ensure you do not get into an incorrect fork and thus will help prevent incorrect forks from forming a consensus on the network.

I sincerely apologize to you for your loss of resources Epsylon3 and to any person that shares that sentiment.