Re: ERC NOBLEPAY COIN2PAY moBUinet STAISYB. VPOS ROKOS MULTIPOOL FEDERATEDCHAINS-DEV
i see there a big problem
the chain u send out is not only different from the block explorer chain its also different from the bittrex chain
u should request bittrex set ERC into maintainance without deposits and withdraw until this issue is solved
we talking here about a major issue
no one should deposit or withdraw from exchanges until that situation is solved
the chain u send out is not only different from the block explorer chain its also different from the bittrex chain
u should request bittrex set ERC into maintainance without deposits and withdraw until this issue is solved
we talking here about a major issue
no one should deposit or withdraw from exchanges until that situation is solved
hmm Thanks for the heads up! appreciated.
So all new wallets run on a new chain? havent had time to check yet but if that is so it is a very big deal that wasnt mention and handled before rolling it out, to have bittrex, bleutrade and any other exchange and all other contributors and supporters of different projects going on the old one, with wrong chain then.. just makes up a lot more anger and frustration when it wont work to withdraw or deposit coins to or from them... a big unnecessicary headache for all involved... that should been stated before roll out of new wallet so people knew that in before hand that.
"-until exchanges and support projects upgrade wallet version hold from deposit or withdraw "
that little meaning would done sooo much. (im not saying it´s so , but IF it is )
Thank you for reporting,
no the chain is still the 2.0 chain this was not a hardfork.
SERVICES
of course we keep services up to date. Some already upgraded, but nonetheless,
i made a second notification round today to all services, nodes, exchanges and blockexplorers.
I highlighted also the urgency for those, who didn't upgrade yet.
Because this time are more behind then normal i assume, the endless upgrades and failures of recent
weeks, made them first watch a day, if this one works . This may be the case especially for those, who don't feel,
they are having issues with a version that is running at that time.
This was my first bug with the potential thread of destroying the network and the coin.
I am confident to hopefully handle this with a much more cooler head, next time.
It was a quite shuttering experience, from time to time, to see over a year of fulltime work
possibly going bust, i have to confess.
Anyway it was the most effective crash course, i ever had, now i know in depth,
how my coin is functioning, there is always a bright site
STATUS
everybody who thinks he may have ended up on a wrong chain, please type "repairwallet",
close it, delete your peers.dat and change/add our nodes using "connect" instead of "addnode".
Then restart and wait. If you are not running ahead of us, it will mostly find back itself.
If it does not find the right chain, checkout our new installer, it has a turnkey ready chain included.
After the wallet returned, switch back to "addnodes" doing everything vise versa.
I checked statistics this morning and we are approaching the tipping-point where 2.0.24 are being run by the majority.
This can caurse the old wallets to misbehave and to bring irregular behaviour into the network, when they are still nearly 50%.
As soon as the majority of new wallets will grow further, this will stop. At the moment you can see the result in the chain randomly speeding up
and then slowing down to nearly zero and then speeding up again.
You can help to stop this quite easily, if you have a working 2.0.24 Wallet, by staking like hell and therefore strengthening the network.
thats it so far
have fun
Matthias
.