EUROPECOIN [ERC] 🌟 FINANCECLOUD 🌟 CRYPTOCURRENY & FINANCE API + SMARTHUB 🌟

[szenekonzept]

we still have people who dont want to use a installer and who sync from zero as a quality gate before they use a coin


so yes nice that we have the easy path

but make sure u can sync from zero hassle-free too

Of course, Europecoin installer is an OPTION,
made for fresh users, or those who like the convenience.

SERVICE is everything ...... right after CHOICE 

have fun
Matthias




.

OP updated

- added our new installer,
- new icon to identify the noinstall version.

have fun
Matthias

[1714079580]

1714079580

[1714079580]

1714079580

[conf]

i just want to say.... the wallet work for me!
Congratz Europecoin team!

[S3cco]

One more wallet back into staking!

Great job, guys!

[pujumba]

Portuguese ANN here people  

  | PORTUGUESE |  

Take a look and have fun, any questions you can send pm or message, on the portuguese ANN

[cryptonit]

blockexplorer stuck? im lot blocks ahead of him and i have lot valid connections

i would love to see ERC on chainz which in my opinion is one of best explorers out there

[szenekonzept]

blockexplorer stuck? im lot blocks ahead of him and i have lot valid connections

i would love to see ERC on chainz which in my opinion is one of best explorers out there

yes, its even not on our chain anymore, i guess.
i will notify Vegas, to upgrade to our newest version
(there are many i have to notify tomorrow, anyway)

thanks for reporting
Matthias

[OKtoshi]

ERC added to ROKOS website: https://twitter.com/AltcoinOfficial/status/723302623072391168

[szenekonzept]

So many friendly  congratulations




Over two month of hardcore survival, time to say

THANK YOU! YOU ARE UNBELIEVABLE!

nothing can stop this community
so fun Matthias 




.

[huige007]

 Stuck again at 921618  WIN7

[cryptonit]

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

[Antebellum]

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

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 )

[Limx 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 Bittrex Exchange running correct. I've it tested yesterday. Also all my wallets are correct. The Explorer is forked by block 921100 ~. My Chain is

Code:

12:29:50

getblockhash 922040


12:29:50

3f0491da78654cded23cab0346b0528504d96f4b3d9d9ebb2f1509c2a1d1e2fb

Stuck again at 921618  WIN7

You must only wait. The wallet is in "preload tx modus". You see a stuck but the wallet works. You can start the wallet with -debug. Here can you see the "preload".

"preload tx modus"  isn't only a dummy word for the works. It is a little different.

[szenekonzept]

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

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



.

[wildduck]

Guys i still have problem wallet with instaler stuck at block 254837

ERROR: AddToBlockIndex() : Rejected by stake modifier checkpoint height=254838, modifier=0xbbb66c4098c49e9b
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
trying connection 109.86.163.180:2828 lastseen=6.8hrs
connection timeout
trying connection 212.25.58.47:2828 lastseen=21.8hrs
connection timeout
trying connection 47.208.180.164:2828 lastseen=17.8hrs
connection timeout
trying connection 188.78.221.62:2828 lastseen=10.8hrs
connection timeout
trying connection 137.135.57.119:2828 lastseen=14.8hrs
connection timeout
trying connection 85.180.234.225:2828 lastseen=13.8hrs
connection timeout
trying connection 85.240.75.83:2828 lastseen=10.9hrs
connection timeout
trying connection 87.143.226.177:2828 lastseen=14.8hrs
connection timeout
trying connection 89.160.194.106:2828 lastseen=2.5hrs
connection timeout
trying connection 95.76.145.63:2828 lastseen=14.0hrs
connection timeout
trying connection 89.160.194.106:2828 lastseen=2.5hrs
connection timeout
trying connection 178.150.87.107:2828 lastseen=9.1hrs
connection timeout
trying connection 213.242.28.12:2828 lastseen=35.9hrs
connection timeout
trying connection 89.160.194.106:2828 lastseen=2.5hrs
connection timeout
trying connection 223.74.46.172:2828 lastseen=6.5hrs
connection timeout
trying connection 119.81.84.252:2828 lastseen=29.3hrs
Flushed 58 addresses to peers.dat  7ms
connection timeout
trying connection 178.150.87.107:2828 lastseen=9.1hrs
ProcessBlock: ORPHAN BLOCK, prev=686ed8ae907d4722b750
connection timeout

[Antebellum]

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



.[/size]

Ok thanks for the reply and clarification! And sorry if i sounded harsh, wasnt my intention at all, i think you all doing a great job. keep it up and this will be a succes.

[Antebellum]

Guys i still have problem wallet with instaler stuck at block 254837

ERROR: AddToBlockIndex() : Rejected by stake modifier checkpoint height=254838, modifier=0xbbb66c4098c49e9b
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
trying connection 109.86.163.180:2828 lastseen=6.8hrs
connection timeout
trying connection 212.25.58.47:2828 lastseen=21.8hrs
connection timeout
trying connection 47.208.180.164:2828 lastseen=17.8hrs
connection timeout
trying connection 188.78.221.62:2828 lastseen=10.8hrs
connection timeout
trying connection 137.135.57.119:2828 lastseen=14.8hrs
connection timeout
trying connection 85.180.234.225:2828 lastseen=13.8hrs
connection timeout
trying connection 85.240.75.83:2828 lastseen=10.9hrs
connection timeout
trying connection 87.143.226.177:2828 lastseen=14.8hrs
connection timeout
trying connection 89.160.194.106:2828 lastseen=2.5hrs
connection timeout
trying connection 95.76.145.63:2828 lastseen=14.0hrs
connection timeout
trying connection 89.160.194.106:2828 lastseen=2.5hrs
connection timeout
trying connection 178.150.87.107:2828 lastseen=9.1hrs
connection timeout
trying connection 213.242.28.12:2828 lastseen=35.9hrs
connection timeout
trying connection 89.160.194.106:2828 lastseen=2.5hrs
connection timeout
trying connection 223.74.46.172:2828 lastseen=6.5hrs
connection timeout
trying connection 119.81.84.252:2828 lastseen=29.3hrs
Flushed 58 addresses to peers.dat  7ms
connection timeout
trying connection 178.150.87.107:2828 lastseen=9.1hrs
ProcessBlock: ORPHAN BLOCK, prev=686ed8ae907d4722b750
connection timeout

that sounds odd, you have to give it time, it just looks like it stuck but since it have a lot of orphans and other blocks to pass thru it will take time before it starts again. as long as you have new wallet, right .conf file and see you have connections, just let it stay open and it will eventually catch up. ( i have synced it on 4 windows 7 x64 systems now , and even thou it takes time all of them are synced, staking and works. )

[szenekonzept]

we still have people who dont want to use a installer and who sync from zero as a quality gate before they use a coin

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.
.............................


..........
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



.[/size]

Ok thanks for the reply and clarification! And sorry if i sounded harsh, wasnt my intention at all, i think you all doing a great job. keep it up and this will be a succes.

so yes nice that we have the easy path

but make sure u can sync from zero hassle-free too

Harsh?? NA, everything ok  
did i sound like that? Your question was definitiv ok.

Services have been late indeed. Now the most important ones upgraded,
Bitnodes are fine too. Network is growing fast, moves smoother every hour.

@wildduck if i one day need someone for software testing, you are on top of my list  
(help is on its way)


ah forgot helmut:
The wallet is ok (for now), Chris is sitting there and monitoring and very many computers are tested now (even Rasperry PI)
The installer is an optional convenience feature, not a workaround.
Its an innovation from Chris, Bitsend features it already quite a while.
If you go back in this thread, you can also see, this was not a quick decission i already annouced it over a week ago.

Of course we always deliver a working noinstall,
no question, i would not like people to overwrite blockchains on upgrade 4 example.
And my server traffic says thank you too 

have fun
Matthias

.

[cryptonit]

get explorer up on right chain make sure he is also one of the seednodes

then everyone should be easy able to see the true chain
i got my withdraw from bittrex now so maybe they are on right chain

maybe because that transaction is visible on both chains the bad one where explorer stuck too

this is a clear sign that the chains interchange data and transactions creating a unhealthy combination

but more and more nodes update and get the right chain synced should help us overcome this

im sorry if i post some red light be carefull message about this

but i still have the opinion to be very carefull with tx from and too exchange until situations like this are stabilized


how they say

[cryptonit]

i see bittrex is in maintenance on ERC now thats great so situation is monitored by them too and no issues will arrise


this is perfect

a few days and we will have a stabilzed network andall services up2date

in a few weeks we will see chain runs like a clockwork now

[meyer]

I used the installer... worked everything perfect
I made a withdraw from Bittrex ... took some time but everything arrives without problems