Topic: [ANN][CRW] CROWN (SHA256) | Platform | Governance | Systemnodes | Masternodes | - page 207. (Read 316957 times)

Just to reassure people, there is 0 nefarious when it comes to Crowncoin, I wouldn't be here otherwise. What you see is what you get.
We all really appreciate your help with this, so much so we have agreed to subsidize your losses (our mistake)

fc1122eb46bc9a5e17afbeb630c3ee68ac1104903e8b615b4f6dc4ffb0a01f3d

Did someone already inform C-cex of the fork?

Looks like they already updated to 70020

HARDFORK - SUNDAY - 25/09/16 10:00 UTC


ALL USERS PLEASE UPDATE



Please download builds from OP or compile from latest source on github. Getinfo should return version 90350 and protocol version 70020.

This update is to implement Dark Gravity Wave to smooth difficulty adjustments.

I'm not sure I fully understand what is going on.  I'm running "version" : 90350, "protocolversion" : 70020, and this is what I can see:


This is what I am expecting to see. The versions with protocol 700010 should be kicked on Sunday...

Thanks.  I was expecting either of those builds to be seeing thrones with 700010. I don't understand why they aren't part of the list before the hardfork epoch. 

I'm just updating my Thrones that run 700010 to latest git anyway.  Its a shame to stop them...they have somehow been running stable for 22 days!

Latest src from GitHub


{
    "159.203.31.42:9340" : "ENABLED",
    "192.99.73.199:9340" : "ENABLED",
    "80.233.175.26:9340" : "ENABLED",
    "158.69.66.49:9340" : "ENABLED",
    "158.69.66.51:9340" : "ENABLED",
    "149.202.170.34:9340" : "ENABLED",
    "45.32.156.157:9340" : "ENABLED",
    "92.222.9.28:9340" : "ENABLED",
    "108.61.10.90:9340" : "ENABLED",
    "149.202.170.53:9340" : "ENABLED",
    "167.114.249.190:9340" : "ENABLED",
    "158.69.66.54:9340" : "ENABLED",
    "149.202.171.123:9340" : "ENABLED",
    "163.172.177.131:9340" : "ENABLED",
    "146.0.32.101:9340" : "ENABLED",
    "158.69.94.122:9340" : "ENABLED",
    "158.69.66.50:9340" : "ENABLED",
    "158.69.66.52:9340" : "ENABLED",
    "149.202.170.35:9340" : "ENABLED",
    "149.202.170.48:9340" : "ENABLED",
    "158.69.66.59:9340" : "ENABLED",
    "167.114.246.82:9340" : "ENABLED",
    "51.254.131.226:9340" : "ENABLED",
    "158.69.66.6:9340" : "ENABLED",
    "158.69.66.58:9340" : "ENABLED",
    "158.69.66.57:9340" : "ENABLED",
    "149.202.170.46:9340" : "ENABLED",
    "149.202.164.150:9340" : "ENABLED",
    "75.130.163.51:9340" : "ENABLED",
    "5.189.152.132:9340" : "ENABLED",
    "192.99.73.200:9340" : "ENABLED",
    "163.172.64.208:9340" : "ENABLED",
    "149.202.170.238:9340" : "ENABLED",
    "149.202.170.236:9340" : "ENABLED",
    "146.0.36.94:9340" : "ENABLED",
    "91.134.143.187:9340" : "ENABLED",
    "149.202.170.56:9340" : "ENABLED",
    "137.74.157.32:9340" : "ENABLED",
    "139.59.255.88:9340" : "ENABLED"

  "version" : 90350,
    "protocolversion" : 70020,
    "walletversion" : 60000,

No rewards yet but it should get some soon
----------------------------------------------------------------------------------

{
    "159.203.31.42:9340" : "ENABLED",
    "146.0.32.101:9340" : "ENABLED",
    "163.172.64.208:9340" : "ENABLED",
    "45.32.156.157:9340" : "ENABLED",
    "163.172.177.131:9340" : "ENABLED",
    "5.189.152.132:9340" : "ENABLED",
    "146.0.36.94:9340" : "ENABLED",
    "137.74.157.32:9340" : "ENABLED",
    "192.99.73.200:9340" : "ENABLED",
    "192.99.73.199:9340" : "ENABLED",
    "139.59.255.88:9340" : "ENABLED"
}
{
    "version" : 90200,
    "protocolversion" : 70020,
    "walletversion" : 60000,

Latest src before recent change
receiving rewards has been running longer (Updated to latest src but before recent change)

Both versions are sending/receiving with each other.
----------------------------------------------------------------------------------------

We're going to get on with that today.  I'm just waiting for a triple check/confirmation that we're 100% happy to go with version and builds that we have posted.  We've made a few mistakes recently and I don't want to repeat them.  Might as well be extra cautious.

I also need to update my own thrones.

Could you do me a favor and post the output from a thronelist protocol from a node that has been running for a few hours?  Thanks.

Best idea is to make sure exchanges and block explorer + pools have been contacted to update src before the soon to be Hardfork. Get everyone on the same page and double check that.

Thanks everybody for the updates.  Our dev is a little short on time at the moment due to day job responsibilities.  We are actively looking for somebody to help us with dev basics like maintaining version numbers and releases to get things moving a bit more smoothly. If you have the skills, please send me a PM and we can discuss terms.

In the meantime, I have set up a Bugzilla instance to help us keep track and prioritise things we need to fix.

For the next week or two I will be paying a 500CRW bounty to anybody who logs a functionality or security related bug on there and posts the Bug report ID number here in this thread. You can find our bug tracker at this address http://bugzilla.crownlab.eu/

We are currently working with a designer on a new wallet so I won't be paying out for cosmetics bugs at the moment.

Good to see people slowly updating to latest version and Throne numbers growing!

vrs 90350 via GitHub latest.



 "159.203.31.42:9340" : "ENABLED",
    "192.99.73.199:9340" : "ENABLED",
    "80.233.175.26:9340" : "ENABLED",
    "158.69.66.49:9340" : "ENABLED",
    "158.69.66.51:9340" : "ENABLED",
    "149.202.170.34:9340" : "ENABLED",
    "45.32.156.157:9340" : "ENABLED",
    "92.222.9.28:9340" : "ENABLED",
    "108.61.10.90:9340" : "ENABLED",
    "149.202.170.53:9340" : "ENABLED",
    "167.114.249.190:9340" : "ENABLED",
    "158.69.66.54:9340" : "ENABLED",
    "149.202.171.123:9340" : "ENABLED",
    "163.172.177.131:9340" : "ENABLED",
    "146.0.32.101:9340" : "ENABLED",
    "158.69.94.122:9340" : "ENABLED",
    "158.69.66.50:9340" : "ENABLED",
    "158.69.66.52:9340" : "ENABLED",
    "149.202.170.35:9340" : "ENABLED",
    "149.202.170.48:9340" : "ENABLED",
    "158.69.66.59:9340" : "ENABLED",
    "167.114.246.82:9340" : "ENABLED",
    "51.254.131.226:9340" : "ENABLED",
    "158.69.66.6:9340" : "ENABLED",
    "158.69.66.58:9340" : "ENABLED",
    "158.69.66.57:9340" : "ENABLED",
    "158.69.195.55:9340" : "ENABLED",
    "149.202.170.46:9340" : "ENABLED",
    "149.202.164.150:9340" : "ENABLED",
    "75.130.163.51:9340" : "ENABLED",
    "5.189.152.132:9340" : "ENABLED",
    "192.99.73.200:9340" : "ENABLED",
    "163.172.64.208:9340" : "ENABLED",
    "149.202.170.238:9340" : "ENABLED",
    "149.202.170.236:9340" : "ENABLED",
    "146.0.36.94:9340" : "ENABLED",
    "91.134.143.187:9340" : "ENABLED",
    "149.202.170.56:9340" : "ENABLED",
    "137.74.157.32:9340" : "ENABLED",
    "139.59.255.88:9340" : "ENABLED"

i have fixed it in the repo releases, ill have a look at the git release code in the source as soon as i have time

what is your crowncoin address, i will send you 2000 crw

So you want us to compile again?
Can you guys all work on the update, test it and then release it. Everyone is not on the same page and bad things can happen. I lost 2k crw in earning so far because of this mess, and I know what I am doing.
It's not showing the old versions and it shouldn't after a hard fork. It should be rejecting those , if you want consensus...Test the release before making the git changes then simply get us all to update at the same time. You guys are doing updates sporadically which for one cause one of my nodes to earn over 5k crw in one day(went from 5k to 2k after your "update" hmm).. You then issued an update 10hrs later which left it stuck and hung on a block..
The oldnodes versioning is obsolete why bother fixing it to show them. I have recovered my CRW from this random updates at anytime. People will start to think you are doing something shadey in the backend if you don't be clear about these updates and take this seriously .
Don't get me wrong though, we are supporting you guys and trying to help...


edit:
Current thrones list on our end;

 {
    "159.203.31.42:9340" : "ENABLED",
    "146.0.32.101:9340" : "ENABLED",
    "163.172.64.208:9340" : "ENABLED",
    "45.32.156.157:9340" : "ENABLED",
    "163.172.177.131:9340" : "ENABLED",
    "5.189.152.132:9340" : "ENABLED",
    "146.0.36.94:9340" : "ENABLED",
    "137.74.157.32:9340" : "ENABLED",
    "192.99.73.200:9340" : "ENABLED",
    "192.99.73.199:9340" : "ENABLED"
}

Starting to look much better, nice work.

What about all the different versions? It can't be helping matters.

Will do

vin error huh..

Can you keep a close eye on that throne please.

If it drops off let us know

Nice one, that worked a treat

FYI, I tried doing a normal throne start-many after sorting out the 2nd VPS - it worked, but I got a VIN error on the first one! 2nd one appeared on list, first did not. Followed the advice above and now both are on the active list.

Happy to help Stonehedge, cheers for the quick responses guys.

soo, updated.. are we on the correct chain now..? i still see only 6 masternodes..

How i fixed this.

Shut down the QT

Goto throne.conf

Copy paste the working throne info to a temp txt file.

Start the wallet again

Do throne start, or if more than one needs fixing throne start-many

This should activate the throne.

Turn the wallet off

Goto throne.conf

Add the throne you copy pasted from before

Restart wallet

----====----

Like stone said, this needs fixing and is on the list, cheers