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: 08:29:49

{
"80.233.175.26:9340" : 70010,
"167.114.249.190:9340" : 70010,
"149.202.170.238:9340" : 70010,
"149.202.164.150:9340" : 70010,
"108.61.10.90:9340" : 70010,
"163.172.64.208:9340" : 70010,
"92.222.9.28:9340" : 70010,
"149.202.170.236:9340" : 70010,
"158.69.66.51:9340" : 70010,
"158.69.66.52:9340" : 70010,
"45.32.156.157:9340" : 70020,
"158.69.66.54:9340" : 70010,
"51.254.131.226:9340" : 70010,
"149.202.170.35:9340" : 70010,
"158.69.66.58:9340" : 70010,
"149.202.170.53:9340" : 70010,
"149.202.170.34:9340" : 70010,
"149.202.171.123:9340" : 70010,
"149.202.170.48:9340" : 70010,
"149.202.170.46:9340" : 70010,
"158.69.94.122:9340" : 70010,
"167.114.246.82:9340" : 70010,
"158.69.66.49:9340" : 70010,
"158.69.66.50:9340" : 70010,
"158.69.66.59:9340" : 70010,
"158.69.66.57:9340" : 70010,
"158.69.66.6:9340" : 70010,
"159.203.31.42:9340" : 70020,
"163.172.177.131:9340" : 70020,
"149.202.170.56:9340" : 70010,
"146.0.32.101:9340" : 70020,
"75.130.163.51:9340" : 70010,
"91.134.143.187:9340" : 70010,
"5.189.152.132:9340" : 70020,
"146.0.36.94:9340" : 70020,
"137.74.157.32:9340" : 70020,
"192.99.73.200:9340" : 70020,
"192.99.73.199:9340" : 70020,
"139.59.255.88:9340" : 70020
}
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!
|
|
|
|
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.
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. |
|
|
|
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. |
|
|
|
|
I hope you guys understand this.
It feels really nice for people to be reporting problems like this. We've been doing these things in a small group for a while. Its great to be getting some help from new community members!
|
|
|
|
Go ahead mate, the more Thrones we have more stable the Crowncoin network becomes and our primary goal with the project approaches faster! Have a Good weekend! Seems to be working now, thanks for that.
Great to hear, welcome to the club  Did the Throne setup guide help you much? Thanks, and yep, wouldn't have had a clue how to set it up without the guide! Should have a couple more up over the weekend. I've set up a second VPS, blockchain all downloaded, but I'm not sure what to put in my local crowncoin.conf file now. At the moment, it's got the following lines in it: externalip=x.x.x.x throne=1 throneprivkey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx which refer to the first throne I set up, as per the guide (I think. It's been working off the first one since I set it up anyway). Does anyone know how I reference the second throne in there as well? Thanks again! Are you trying to run more than one throne from local wallet? Yeah, is that possible? This only tells you how to setup LOCAL side... I recommend using a hosting service to help you setup REMOTE side. Thanks for this. I've followed the instructions, and when I go to throne start-many I get the following error message: { "overall" : "Successfully started 0 thrones, failed to start 2, total 2", "detail" : { "status" : { "alias" : "Throne1", "result" : "failed", "errorMessage" : "Throne has already been started and your IP added to the list." }, "status" : { "alias" : "Throne2", "result" : "failed", "errorMessage" : "Throne has already been started and your IP added to the list." } } } the first throne is in the list of those running when I do throne list, but the second isn't there. Both appear to be running fine on the VPS and are up to date. Any ideas what I might have done wrong? I have experienced this in the past too. I'm not sure exactly what is causing it. I'll look into the root cause and report back. When it happened for me before, I tried again a few hours later and it worked fine. Needs to be fixed though. |
|
|
|
jep.. from github.. "version" : 90200,
"protocolversion" : 70020,
"walletversion" : 60000 {
"139.59.255.88:9340" : "ENABLED",
"146.0.32.101:9340" : "ENABLED",
"192.99.73.200:9340" : "ENABLED"
}
both of you, please update your thrones wallet from github and your windows wallet via OP of this thread this should fix all your problems. This hardfork has been a bumpy ride, and i apologies to everyone, we are setting up procedures on how things will be from here on out this latest wallet will support the hardforking happening sunday 25th at 10 AM UTC The hard fork that we haven't announced yet  We're implementing Dark Gravity Wave so we can enjoy more rapid diff adjustments. We've been squeezed by a few >1Ph pools in the last few weeks and it is creating a bit too much of a sell pressure to be healthy. yeah I see 13hrs ago you guys updated the GitHub, everyone needs to be on the same page . I agree. Basic screw up on our part. I'm going to be taking responsibility for release management from now on so hopefully this will be the last time. |
|
|
|
jep.. from github.. "version" : 90200,
"protocolversion" : 70020,
"walletversion" : 60000 {
"139.59.255.88:9340" : "ENABLED",
"146.0.32.101:9340" : "ENABLED",
"192.99.73.200:9340" : "ENABLED"
}
both of you, please update your thrones wallet from github and your windows wallet via OP of this thread this should fix all your problems. This hardfork has been a bumpy ride, and i apologies to everyone, we are setting up procedures on how things will be from here on out this latest wallet will support the hardforking happening sunday 25th at 10 AM UTC The hard fork that we haven't announced yet We're implementing Dark Gravity Wave so we can enjoy more rapid diff adjustments. We've been squeezed by a few >1Ph pools in the last few weeks and it is creating a bit too much of a sell pressure to be healthy. Block explorer reported I was/am on correct chain, I git cloned directly from your GitHub . I hope that ccex and the block explorer have updated to the latest from GitHub because that's the place we are getting the latest src from. Now, the second master node I have thrown up today is getting rewards and I am double checking the first one that was reportedly getting most the rewards that M8BWNNRFMNdak68c mentioned. We are trying to help with this; "159.203.31.42:9340" : "ENABLED", "146.0.32.101:9340" : "ENABLED", "192.99.73.200:9340" : "ENABLED" fresh master node from src today- this is whats it's reporting with "throne list", it was reporting back the one mentioned but I am double checking it currently and it is expired until then. This is what I can see from the console on one of my Thrones. I can only see two of those three IPs. My thought is that it is essential that you are running the same wallet version locally and remote. We screwed up and while Git was updated, the builds in OP were still for 700010. If you have 700020 remote and 700010 locally, could that explain the problem? {
" 80.233.175.26:9340" : " ENABLED 70010 1FmEkTTa18s5PmuzDrR3hFkmd7ceFNYrH9 2470ff73f777249046334b6fccc029a5492dd82e63dcc2efad738ddf14d8c0e0 1474377338 1126706",
" 167.114.249.190:9340" : " ENABLED 70010 17u9YpYmVv1JLg389FnVnSPEXUvXXv6BK6 0304566d46efd2be4056ffce7557eb1827414ae3eda4fbe001f713ef31e780df 1474377844 1909132",
" 149.202.170.238:9340" : " ENABLED 70010 1LV6hX9BqR1i42JFGv1DZ7g3LG2Hy8p2Pe 13b8fac7f8d471a9da5d6ee2aaa7a321acb85ec973e686474acac3e2e860c43a 1474378629 1909935",
" 149.202.164.150:9340" : " ENABLED 70010 1Biby5dYYG1YSDpXBFbbukpg6DCZpbUQQ9 0461a3f6ebf0e213a1a223f22a9dcf8ac024bb7e8e5d770ff15c5f07058e68bb 1474378536 1307188",
" 149.202.170.56:9340" : " ENABLED 70010 1PkvXnRsDbqbJ9SLh7rFyEGM2e5Np8SxWw 6809f235f344eedd4f17ba8386f2afb1c5c540faa7ffe7857d87e002f97126e4 1474375536 1906835",
" 108.61.10.90:9340" : " ENABLED 70010 158JhEUUuQLe1qMHNa2cX6debdSHpvxt5P 2ca33107605864737cb7ef297452d67da31e768b9d15446373818bf371bd3ed2 1474377661 967790",
" 163.172.64.208:9340" : " ENABLED 70010 1P8PWUyYifD9gEmFKNhfgt6ENnfRtXvbwH e25fd6ba424bb3d802979e7af55f6d1cfb114b23206ec2aba92669460389d871 1474378835 1024668",
" 92.222.9.28:9340" : " ENABLED 70010 1GAHKmGtUE25gHMwmnFgdEoYVq6WyU8FAp 409b833dedee3165021083ae84851a5f497fa91c6eda2ef7ff3208191c386809 1474378900 875777",
" 149.202.170.236:9340" : " ENABLED 70010 13snuFwJGChyPFS3ySZsywoJN9eGeUtnb8 1c288c3f4d96376c4b2d985c60d46f04be1180d7d01e7c9bccbd082dbd82a8f1 1474378818 1910123",
" 158.69.66.51:9340" : " ENABLED 70010 1nBo67JM4sMDjRmgUuKBimWG15swDFuwY d2dbc33150185dd3814c56af018c8bb4424a614003deb2fa50d6fea4802b582b 1474378851 1910144",
" 158.69.66.52:9340" : " ENABLED 70010 1AhZE9VhexN5ctscdFd554fB67br9rYaPN db4d40779384a36f3f38b20ab08b8c268aa113ec3e8f4f0e1857037dd41865e1 1474378894 1910186",
" 163.172.177.131:9340" : " ENABLED 70010 1NYxtDcjFxUtsmjcaoHjt5LnjAHgDmGe59 eee3968601be050afc5f732822fd87a6c8a3124ad0235e47f20ef33fe8019ba5 1474377195 1012172",
" 45.32.156.157:9340" : " ENABLED 70010 1Fe9jBtqxJVcaLTmtYmcxy9noSpGunkkFY 67e5e9bc420b9e274eb35bd1329a8228e8cee214e374acb7e1513fc6301f48ef 1474377169 943597",
" 158.69.66.54:9340" : " ENABLED 70010 1ASDZcVWQ9McVHuSqQXdDFefkEHNY11tTc 7cc0f4b0d39e17af4cd82e1962d3ec68766097b23c21eaa38755187ec7ecb9f1 1474377816 1830926",
" 51.254.131.226:9340" : " ENABLED 70010 12F8KzzZAmceAEb2evCcYYgnZdTVutMUcA 409b833dedee3165021083ae84851a5f497fa91c6eda2ef7ff3208191c386809 1474378315 1193199",
" 149.202.170.35:9340" : " ENABLED 70010 1ALMjFg4zw5p23apYu6oAzQB6vaCkBSS4g 1ecde6006ff296e07388b5b497267621f9d31abce97a0f6dc9ba1a9ab910ec46 1474377495 1908799",
" 158.69.66.58:9340" : " ENABLED 70010 1LapNMzHBrPrRyNoJrvyBLL3TQ3J8nx7tT cff2134ec924e61ed6080ad1aca8c07b039804f5551960b1fbb3eefd46473adb 1474378409 1831331",
" 149.202.170.53:9340" : " ENABLED 70010 1PoD3oFQ58dzxbaHwJhM9FHegCasNLatnQ 3b5c92fcdbfe1aed74c82ca025cee3736f78a8f4dc81476c40a7bf0b34a48c2e 1474377289 1908591",
" 149.202.170.34:9340" : " ENABLED 70010 1Lgqxw8nNezeAJf1mG5Q3RwkerhhoWu7W6 29c97be3faa4b0eaadea18bca90a9364e0fbc4f039d36d3dd0456d7d866770df 1474377295 1908598",
" 149.202.171.123:9340" : " ENABLED 70010 1F6CTu95hqj7mcX3n6Tra4JnuXQMZzo82F 5c12cab8cf7f44bb6129759da52c074d1ef96b1870ef3c679342dd0f43a30efa 1474377961 1909262",
" 149.202.170.48:9340" : " ENABLED 70010 12RgvqhMbe4HhfHKCFLaD3CTSYyxKBNQVg 405c27cf8fd21f26fe02ef3fa261cc22e674e7a684ffecbd8ad2a9f7d3b04682 1474378594 1909895",
" 149.202.170.46:9340" : " ENABLED 70010 1Nd8ymnyNcBKLgrYFE55WmqJYgmtVKjmDL 5d9b65b1a4a73a801fb82ba3100db51eaf36ce2f1cd5ddfa408af65f32d775ab 1474377333 1908633",
" 158.69.94.122:9340" : " ENABLED 70010 15fbYwJG8JWAMtzcRUUNiLLrmfdspx3ZV9 68cd01ffd7a01829f9295f82d6f6a2c93e5dbc2ac8411d51ffe94c45a6ad1421 1474377397 1830585",
" 167.114.246.82:9340" : " ENABLED 70010 1NXYxUp6AXoRsAjZbypRmKNXyEHKE4BVSb 692b5f3fb863c2601c3df8d7b975d80d75cdccf7fcb9c85ea65cf0a348c733d5 1474377488 1908777",
" 158.69.66.49:9340" : " ENABLED 70010 1Cg2dfzMu97g4G39SUWTrrwCMMfkKt7PDS f32274c54705cbdafff6bf02821dbdf9ff02483e3bfcb647061156b4fd2719be 1474377883 1909174",
" 158.69.66.50:9340" : " ENABLED 70010 1D3abmwgPhdiEMdKQDNMEGD5gSzMN5QWRv f541f7b36435593ca1c671e42adb71ed665b2948b9cf8b9b87ed2c8b6ea51ffd 1474378108 1909398",
" 158.69.66.59:9340" : " ENABLED 70010 1N1tqyb2GDXX9398a8DpSTF7pvQtvbfHWc 996282f85939f61088be89bd3e9cd05ad6973c89feed1f6b96634122ec88d471 1474378305 1831323",
" 158.69.66.57:9340" : " ENABLED 70010 1GoL6ptSouurGkmg3XByFsgzzBNaLpPMVH d14aedd6cdb2018253771fcd0d09576d75ef152c36a644b5c6efd3dbfbb612ee 1474378421 1831334",
" 75.130.163.51:9340" : " ENABLED 70010 13rcHZcDRExcn6xEUcqt6w8ZE7Hhiw35H2 af59b2f9e4a835a756898c4156f445334a36ac9b76d6fba4cef1b2d7cfb9a573 1474378221 650722",
" 158.69.66.6:9340" : " ENABLED 70010 1FEwwtpbdxU71XJDoMV8JyTNA4Vixgucrr b32ed6918604410d1d4bfd1dcb8c8f8fec25a6aa09704c68983d1f69f842fa16 1474378354 1831283",
" 91.134.143.187:9340" : " ENABLED 70010 1Q555PD2RuHm8YKKhuWGhrtGV8ps8MTWFd ef73c4b9c1844f5fca0921d7c40a082693d3913174cd1521f8819a38cc5b48bf 1474378255 68455",
" 159.203.31.42:9340" : " ENABLED 70020 13o6pVPzTcFzS3qJLsMAJet6gRbXs1ARQa 6b42f4c9221be40565baae58da6a5edb21a3250f265f4fe04bc933ed216dfc3f 1474378456 7232",
" 192.99.73.200:9340" : " ENABLED 70020 1CUeDmYn4RWEpxs8wbKUQSYEPgRitAJ4UQ 371a02c8774121fb97bc92e4d4782810a7cd0c4598c2a2d547c7690adbb33a72 1474377442 3627"
} |
|
|
|
jep.. from github.. "version" : 90200,
"protocolversion" : 70020,
"walletversion" : 60000 {
"139.59.255.88:9340" : "ENABLED",
"146.0.32.101:9340" : "ENABLED",
"192.99.73.200:9340" : "ENABLED"
}
both of you, please update your thrones wallet from github and your windows wallet via OP of this thread this should fix all your problems. This hardfork has been a bumpy ride, and i apologies to everyone, we are setting up procedures on how things will be from here on out this latest wallet will support the hardforking happening sunday 25th at 10 AM UTC The hard fork that we haven't announced yet We're implementing Dark Gravity Wave so we can enjoy more rapid diff adjustments. We've been squeezed by a few >1Ph pools in the last few weeks and it is creating a bit too much of a sell pressure to be healthy. |
|
|
|
masternodes are quite buggy..
i can start one with"throne start-many".. but after some hours it will stop operating without any comment.
i then have to restart it manually..
and everytime i send one command, i have to type in walletpassphrase again ( although it should be unlocked for some days according to "unlocked_until" )
"error: {"code":-1,"message":"Your wallet is locked, passphrase is required\n"}"
furthermore there is a funny error message for "throne start"
"not capable throne: Invalid port: 9999 - only 9999 is supported on mainnet."
the only masternode which i see continously working is:
"139.59.255.88:9340" : "ENABLED",
my own node is sometimes listed as
"EXPIRED"
so what can i do? it seems that 40% of ALL blocks goes to that single masternode..
"version" : 90200,
"protocolversion" : 70020,
"walletversion" : 60000,
I've just had a browse through the block explorer and can see at least 30 Thrones getting paid (gave up looking at that point). 139.59.255.88 has been up for about 1 day. The average longevity of live thrones at the moment is about 18 days since starting. I have no idea why you are seeing different information. Are you happy to share the IP of your Throne that you are having problems with? |
|
|
|
|
Thanks for reporting this.
We're just looking into it now.
I haven't experienced any problems with compiling on ubuntu 16.04. Will try to see if I can replicate.
|
|
|
|
So we have tested and verified the following so far:
DGW - Works perfectly
Locking of coins when running nodes in HOT configuration
we still need to test the fixes i have made with start-many
and locking of coins in HotCold Setup
Also infernoman should be fixing the connection problem some are experiencing
It took two days to mine the 20k tCRW I need to test start-many because DGW works so well! Sadly I have had to leave town for a day to take care of some work, I'm hoping to finish start-many testing tomorrow morning. Hopefully we'll have a few more volunteers for testing for our next release. Didn't you say that the throne management tab is working now too? |
|
|
|
|
Get your buy orders in. Just spotted a miner consolidating wallets...
|
|
|
|
|
DGW working like a charm. Can see diff changing with every block.
|
|
|
|
So here tonight we set up a little testnet to see if DGW was behaving as it should, and i can announce our implementation is working flawlessly... :-)
Great work all round. We've had several 1 petahash pools mine crw this week and having 1 block difficulty changes is going to make things a lot more sensible. Let's perform two or three more tests and then check out other updates and then release. |
|
|
|
Crowncoin Update 11th September 2016
Great update. Looking forward to seeing more. Keep the momentum going guys I can't believe that somebody who has been involved in crypto for so long has only just created a BCT account |
|
|
|
Bittrex could give us a further boost in interest in CRW This coin is moving to where it belongs - The Crown of Crypto Crowncoin Update 11th September 2016
...
Great update! Summarizes current progression and future plans just perfectly, thanks for sharing Stonehedge.  According to recent market activity, it looks like the time to get cheap CRW is over real soon. Hopefully Bittrex will list us soon. Any news on the bittrex front? Didn't we send out an application? I'm not sure what is going on. I applied to them formally a few weeks ago. They replied saying that they would only list us if they see more activity on twitter relating to us. Then they contacted me inviting me to share our dev plans with them (with a non disclosure agreement). I have said no to this for the same reasons we are being a little mysterious here. I'd rather not risk sharing details of our plans until we're ready to deliver them. Exactly, C-cex is delivering a sterling service as it is anyway. In the near future, bittrex will want to add us... regardless I considered paying them 3 BTC to list us but then came to the same conclusion. They'll add us one day. BTW, there is somebody posting on C-Cex trollbox using Stonehedge handle. Its not me! Although, they seem to be doing a good job spreading the word! |
|
|
|
Bittrex could give us a further boost in interest in CRW This coin is moving to where it belongs - The Crown of Crypto Crowncoin Update 11th September 2016
...
Great update! Summarizes current progression and future plans just perfectly, thanks for sharing Stonehedge. According to recent market activity, it looks like the time to get cheap CRW is over real soon. Hopefully Bittrex will list us soon. Any news on the bittrex front? Didn't we send out an application? I'm not sure what is going on. I applied to them formally a few weeks ago. They replied saying that they would only list us if they see more activity on twitter relating to us. Then they contacted me inviting me to share our dev plans with them (with a non disclosure agreement). I have said no to this for the same reasons we are being a little mysterious here. I'd rather not risk sharing details of our plans until we're ready to deliver them. |
|
|
|
And as if to prove my point about needing to implement DGW, our net hash rate has jumped to 1.2PH! I for one welcome our new ASIC mining overloads  |
|
|
|
This coin is moving to where it belongs - The Crown of Crypto Crowncoin Update 11th September 2016
...
Great update! Summarizes current progression and future plans just perfectly, thanks for sharing Stonehedge. According to recent market activity, it looks like the time to get cheap CRW is over real soon. Hopefully Bittrex will list us soon. |
|
|
|
|
Show Posts
