nickgogerty
|
|
November 09, 2016, 05:30:57 PM |
|
According to CryptoID / SLR Explorer there are just 14 wallets active on the 'correct' fork right now. As this is out of 67 on 2.1.6 and 18 still on 2.1.1 (which is no longer valid I understand).
My wallet(s) are all now showing all [?] / orphaned blocks since the fork and it would seem to be better to shut them down rather than keep poisoning the well by being on the wrong one.
I have reloaded the blockchain, scanned the wallets, restarted over and over and frankly this is starting to look worrying.
T
suggest the following: update the file solarcoin.conf with the list of 2.1.6 addnodes from chainz: 1. shut down solarcoin. 2. find and open solarcoin.conf 3. replace with addnode list from chainz of 2.1.6. 4. restart, reload chain (download) 5. rescan wallet. This will minimize noise from 2.1.1 from the start. In the console you can use> getpeerinfo to see the version and blockheight for each of the nodes you are connecting to. could even edit the solarcoin.conf file to start with nodes that are both 2.1.6 and have blockheight similar to figure shown in Chainz explorer. https://chainz.cryptoid.info/slr/#addnode=104.243.243.215 addnode=104.40.180.191 addnode=106.188.97.66 addnode=108.2.63.62 addnode=109.92.226.147 addnode=121.99.234.213 addnode=122.58.152.232 addnode=122.58.156.103 addnode=124.169.44.143 addnode=13.95.228.73 addnode=137.74.194.42 addnode=140.96.96.34 addnode=162.243.214.120 addnode=174.57.197.124 addnode=174.57.202.216 addnode=176.9.61.40 addnode=176.9.65.41 addnode=177.237.140.73 addnode=178.239.212.149 addnode=181.49.47.233 addnode=193.62.194.254 addnode=193.63.220.237 addnode=2.25.219.139 addnode=2.30.78.124 addnode=202.161.30.214 addnode=213.214.73.240 addnode=213.91.205.134 addnode=216.252.93.239 addnode=218.153.165.108 addnode=222.237.184.208 addnode=24.184.112.226 addnode=24.45.125.112 addnode=31.153.53.171 addnode=37.112.117.122 addnode=40.112.185.197 addnode=46.177.125.194 addnode=46.251.115.205 addnode=46.4.66.6 addnode=47.90.61.29 addnode=49.125.2.84 addnode=5.53.251.3 addnode=50.110.249.40 addnode=64.56.26.26 addnode=73.10.58.144 addnode=73.148.159.177 addnode=73.220.153.187 addnode=77.117.40.57 addnode=78.23.178.34 addnode=78.46.23.222 addnode=78.83.197.46 addnode=80.110.126.158 addnode=80.84.176.209 addnode=81.135.94.111 addnode=81.157.7.7 addnode=81.165.11.25 addnode=81.247.156.211 addnode=81.82.241.123 addnode=82.102.115.59 addnode=89.215.51.199 addnode=89.25.80.98 addnode=90.40.180.202 addnode=90.61.194.24 addnode=92.135.209.175 addnode=93.106.236.196 addnode=94.173.60.137 addnode=94.226.224.181 addnode=94.65.89.195 addnode=95.208.92.30
|
Solarcoin (§ SLR) are like airmiles. Each 1 Mhw generated gets you §1 free. Solarcoins can purchase what others will trade: USD,BTC, Soy candles..etc.
|
|
|
|
|
|
"I'm sure that in 20 years there will either be very large transaction volume or no volume." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
onsightit
|
|
November 09, 2016, 05:48:04 PM |
|
According to CryptoID / SLR Explorer there are just 14 wallets active on the 'correct' fork right now. As this is out of 67 on 2.1.6 and 18 still on 2.1.1 (which is no longer valid I understand).
My wallet(s) are all now showing all [?] / orphaned blocks since the fork and it would seem to be better to shut them down rather than keep poisoning the well by being on the wrong one.
I have reloaded the blockchain, scanned the wallets, restarted over and over and frankly this is starting to look worrying.
T
suggest the following: update the file solarcoin.conf with the list of 2.1.6 addnodes from chainz: 1. shut down solarcoin. 2. find and open solarcoin.conf 3. replace with addnode list from chainz of 2.1.6. 4. restart, reload chain (download) 5. rescan wallet. This will minimize noise from 2.1.1 from the start. In the console you can use> getpeerinfo to see the version and blockheight for each of the nodes you are connecting to. could even edit the solarcoin.conf file to start with nodes that are both 2.1.6 and have blockheight similar to figure shown in Chainz explorer. https://chainz.cryptoid.info/slr/#addnode=104.243.243.215 addnode=104.40.180.191 addnode=106.188.97.66 addnode=108.2.63.62 addnode=109.92.226.147 addnode=121.99.234.213 addnode=122.58.152.232 addnode=122.58.156.103 addnode=124.169.44.143 addnode=13.95.228.73 addnode=137.74.194.42 addnode=140.96.96.34 addnode=162.243.214.120 addnode=174.57.197.124 addnode=174.57.202.216 addnode=176.9.61.40 addnode=176.9.65.41 addnode=177.237.140.73 addnode=178.239.212.149 addnode=181.49.47.233 addnode=193.62.194.254 addnode=193.63.220.237 addnode=2.25.219.139 addnode=2.30.78.124 addnode=202.161.30.214 addnode=213.214.73.240 addnode=213.91.205.134 addnode=216.252.93.239 addnode=218.153.165.108 addnode=222.237.184.208 addnode=24.184.112.226 addnode=24.45.125.112 addnode=31.153.53.171 addnode=37.112.117.122 addnode=40.112.185.197 addnode=46.177.125.194 addnode=46.251.115.205 addnode=46.4.66.6 addnode=47.90.61.29 addnode=49.125.2.84 addnode=5.53.251.3 addnode=50.110.249.40 addnode=64.56.26.26 addnode=73.10.58.144 addnode=73.148.159.177 addnode=73.220.153.187 addnode=77.117.40.57 addnode=78.23.178.34 addnode=78.46.23.222 addnode=78.83.197.46 addnode=80.110.126.158 addnode=80.84.176.209 addnode=81.135.94.111 addnode=81.157.7.7 addnode=81.165.11.25 addnode=81.247.156.211 addnode=81.82.241.123 addnode=82.102.115.59 addnode=89.215.51.199 addnode=89.25.80.98 addnode=90.40.180.202 addnode=90.61.194.24 addnode=92.135.209.175 addnode=93.106.236.196 addnode=94.173.60.137 addnode=94.226.224.181 addnode=94.65.89.195 addnode=95.208.92.30 Thanks for the info, Nick. I would also add after step 1, remove peers.dat. It will get rebuilt. If you are running a daemon, you can download the bootstrap.zip file here: http://blockexplorer.solarcoin.org/downloads/bootstrap.zip Unzip it and overwrite the blk0001.dat and txleveldb contents in your data dir. -Steve
|
VRC: VMTMcvFjZHAshmVNLY5KYVHCTqcfEnH6Bd SLR: 8W7D6D7rortYp51BK9MSrfripSoZWyVPVr BTC: 1LbgAsTDtyWEGjiSaguJhJbaHBPgcMnHfP BCC: 1Ta39PK67VXTD2xnmPNo5J9KJyBVHdYmy
|
|
|
Nomadseif
Newbie
Offline
Activity: 38
Merit: 0
|
|
November 09, 2016, 06:01:05 PM Last edit: November 09, 2016, 06:13:54 PM by Nomadseif |
|
According to CryptoID / SLR Explorer there are just 14 wallets active on the 'correct' fork right now. As this is out of 67 on 2.1.6 and 18 still on 2.1.1 (which is no longer valid I understand).
My wallet(s) are all now showing all [?] / orphaned blocks since the fork and it would seem to be better to shut them down rather than keep poisoning the well by being on the wrong one.
I have reloaded the blockchain, scanned the wallets, restarted over and over and frankly this is starting to look worrying.
T
suggest the following: update the file solarcoin.conf with the list of 2.1.6 addnodes from chainz: 1. shut down solarcoin. 2. find and open solarcoin.conf 3. replace with addnode list from chainz of 2.1.6. 4. restart, reload chain (download) 5. rescan wallet. This will minimize noise from 2.1.1 from the start. In the console you can use> getpeerinfo to see the version and blockheight for each of the nodes you are connecting to. could even edit the solarcoin.conf file to start with nodes that are both 2.1.6 and have blockheight similar to figure shown in Chainz explorer. https://chainz.cryptoid.info/slr/#addnode=104.243.243.215 addnode=104.40.180.191 addnode=106.188.97.66 addnode=108.2.63.62 addnode=109.92.226.147 addnode=121.99.234.213 addnode=122.58.152.232 addnode=122.58.156.103 addnode=124.169.44.143 addnode=13.95.228.73 addnode=137.74.194.42 addnode=140.96.96.34 addnode=162.243.214.120 addnode=174.57.197.124 addnode=174.57.202.216 addnode=176.9.61.40 addnode=176.9.65.41 addnode=177.237.140.73 addnode=178.239.212.149 addnode=181.49.47.233 addnode=193.62.194.254 addnode=193.63.220.237 addnode=2.25.219.139 addnode=2.30.78.124 addnode=202.161.30.214 addnode=213.214.73.240 addnode=213.91.205.134 addnode=216.252.93.239 addnode=218.153.165.108 addnode=222.237.184.208 addnode=24.184.112.226 addnode=24.45.125.112 addnode=31.153.53.171 addnode=37.112.117.122 addnode=40.112.185.197 addnode=46.177.125.194 addnode=46.251.115.205 addnode=46.4.66.6 addnode=47.90.61.29 addnode=49.125.2.84 addnode=5.53.251.3 addnode=50.110.249.40 addnode=64.56.26.26 addnode=73.10.58.144 addnode=73.148.159.177 addnode=73.220.153.187 addnode=77.117.40.57 addnode=78.23.178.34 addnode=78.46.23.222 addnode=78.83.197.46 addnode=80.110.126.158 addnode=80.84.176.209 addnode=81.135.94.111 addnode=81.157.7.7 addnode=81.165.11.25 addnode=81.247.156.211 addnode=81.82.241.123 addnode=82.102.115.59 addnode=89.215.51.199 addnode=89.25.80.98 addnode=90.40.180.202 addnode=90.61.194.24 addnode=92.135.209.175 addnode=93.106.236.196 addnode=94.173.60.137 addnode=94.226.224.181 addnode=94.65.89.195 addnode=95.208.92.30 Thanks for the info Nick. It seems to have helped for now I seem to be staying on the correct chain and my bloc height is staying with chainz block height.
|
|
|
|
y_virtual
Sr. Member
Offline
Activity: 377
Merit: 251
Note to self: it's not you doing it, it's us.
|
|
November 09, 2016, 06:15:24 PM |
|
... In the console you can use> getpeerinfo to see the version and blockheight for each of the nodes you are connecting to. could even edit the solarcoin.conf file to start with nodes that are both 2.1.6 and have blockheight similar to figure shown in Chainz explorer. https://chainz.cryptoid.info/slr/#... This was very helpful, thank you Nick!
|
|
|
|
onsightit
|
|
November 09, 2016, 09:24:45 PM |
|
... In the console you can use> getpeerinfo to see the version and blockheight for each of the nodes you are connecting to. could even edit the solarcoin.conf file to start with nodes that are both 2.1.6 and have blockheight similar to figure shown in Chainz explorer. https://chainz.cryptoid.info/slr/#... This was very helpful, thank you Nick! To be clear, getpeerinfo reports the starting height of the node trying to connect to you. If the starting height is less than the height of your node, your node will push its inventory to the requesting node. It is NOT the current height of that node, just the height at the point in time that it connected to you. -Steve
|
VRC: VMTMcvFjZHAshmVNLY5KYVHCTqcfEnH6Bd SLR: 8W7D6D7rortYp51BK9MSrfripSoZWyVPVr BTC: 1LbgAsTDtyWEGjiSaguJhJbaHBPgcMnHfP BCC: 1Ta39PK67VXTD2xnmPNo5J9KJyBVHdYmy
|
|
|
corather
Legendary
Offline
Activity: 1708
Merit: 1000
Solarcoin.org
|
|
November 09, 2016, 11:11:20 PM |
|
... In the console you can use> getpeerinfo to see the version and blockheight for each of the nodes you are connecting to. could even edit the solarcoin.conf file to start with nodes that are both 2.1.6 and have blockheight similar to figure shown in Chainz explorer. https://chainz.cryptoid.info/slr/#... This was very helpful, thank you Nick! To be clear, getpeerinfo reports the starting height of the node trying to connect to you. If the starting height is less than the height of your node, your node will push its inventory to the requesting node. It is NOT the current height of that node, just the height at the point in time that it connected to you. -Steve I can't get the new wallet to run on my XP machine. I did a clean install of the blockchain, and restored a wallet image. Added only peers from 2.1.6, etc. I have a windows 7 machine that does run the wallet, stays on the right chain, but reports a higher balance than what's currently in the wallet.
|
|
|
|
nickgogerty
|
|
November 10, 2016, 03:36:09 AM |
|
for those interested in the LYkke exchange. there is now a channel in the slack solarcoin-group labelled lykke exchange. here is a message there: This was sent to me by Sergey of Lykke. He asked that I relay it. @nickgogerty I've created a subscriber form http://eepurl.com/cn0k9H lykkex.us12.list-manage.com SolarCoin Lykke liquidity pool SolarCoin Lykke liquidity pool Email Forms [1:10] And withdrawal form http://eepurl.com/cn0Ic5 lykkex.us12.list-manage.com SolarCoin Lykke liquidity pool withdrawal SolarCoin Lykke liquidity pool withdrawal Email Forms
|
Solarcoin (§ SLR) are like airmiles. Each 1 Mhw generated gets you §1 free. Solarcoins can purchase what others will trade: USD,BTC, Soy candles..etc.
|
|
|
solarcoiner
|
|
November 10, 2016, 07:41:29 AM |
|
Any chance all of this has no point and there was a problem with the hard fork? My blockchain is still loading but I have a feeling im not going to stay on the correct blockchain for long
|
|
|
|
Nomadseif
Newbie
Offline
Activity: 38
Merit: 0
|
|
November 10, 2016, 08:36:29 AM Last edit: November 10, 2016, 10:23:21 AM by Nomadseif |
|
Ok so an update today, Still only getting orphaned blocks so obviously the wallet has gone to the wrong chain but its back now cause my block height is same as chainz but still can't generate intrest. I did change the conf to have the new node list. What next? at this point I'm worried to send coins anywhere because if the wallet gets to the wrong chain at that moment I'll loose the coins as has already happened to me. Did we hear back from bittrex, have they updated their wallet? e2a: I'm back on the wrong chain again e2a: It seems that the only option for staying on the right chain is to constantly be reloading the blockchian, at least 2-3 times per day. Perhaps we have to think about what we want to do moving forward. Is there an error with the Fork? What about making a message show on all wallets that they need to update to the new version. e2a: I'm turning off my node for now, it's jumping between chains constantly. 1min on one another moment it's on the other chain. I'm gona try a full delete and reinstall of the 2.1.6 build and see if that works but I'll do it later and it'll take about 3 days before I will see if it's worked.
|
|
|
|
solarcoiner
|
|
November 10, 2016, 11:01:07 AM |
|
Ok so an update today, Still only getting orphaned blocks so obviously the wallet has gone to the wrong chain but its back now cause my block height is same as chainz but still can't generate intrest. I did change the conf to have the new node list. What next? at this point I'm worried to send coins anywhere because if the wallet gets to the wrong chain at that moment I'll loose the coins as has already happened to me. Did we hear back from bittrex, have they updated their wallet? e2a: I'm back on the wrong chain again e2a: It seems that the only option for staying on the right chain is to constantly be reloading the blockchian, at least 2-3 times per day. Perhaps we have to think about what we want to do moving forward. Is there an error with the Fork? What about making a message show on all wallets that they need to update to the new version. e2a: I'm turning off my node for now, it's jumping between chains constantly. 1min on one another moment it's on the other chain. I'm gona try a full delete and reinstall of the 2.1.6 build and see if that works but I'll do it later and it'll take about 3 days before I will see if it's worked. It has become pretty evident to me that there was a problem with the hard fork... Why exaclty did we fork again when everything was working? We need a new wallet update asap By the way im in the process of loading the enitre blockchain again from scratch. Should be done tonight (it has been loading since 24h +) I will let you guys know if this works but I have a feeling its not going to work Edit: I def. would not send any coins until the issue is resolved. Like you said you might be at risk of never getting them back. Where is our developper? Why does it take so long to get this issue fixed? Nick: I dont think posting a tutrial on how to resync the blockchain will help. Everyone here knows how to do that. What we need is our lead developper to step up and fix this problem. As simple as that. (Just like last time we had a hard fork) Just restore everything back to the way it used to be and let it be. And by the way this is starting to get really annoying. The POST algortythm is rewarding like 3 addresses with almost all of the interest since 4 days which is unacceptable. Why do we have to deal with this every update? IM starting to wonder if this is really a coincidence? Honestly what gives? Same thing happened last hard fork
|
|
|
|
TooQik
|
|
November 10, 2016, 12:45:04 PM |
|
Ok so an update today, Still only getting orphaned blocks so obviously the wallet has gone to the wrong chain but its back now cause my block height is same as chainz but still can't generate intrest. I did change the conf to have the new node list. What next? at this point I'm worried to send coins anywhere because if the wallet gets to the wrong chain at that moment I'll loose the coins as has already happened to me. Did we hear back from bittrex, have they updated their wallet? e2a: I'm back on the wrong chain again e2a: It seems that the only option for staying on the right chain is to constantly be reloading the blockchian, at least 2-3 times per day. Perhaps we have to think about what we want to do moving forward. Is there an error with the Fork? What about making a message show on all wallets that they need to update to the new version. e2a: I'm turning off my node for now, it's jumping between chains constantly. 1min on one another moment it's on the other chain. I'm gona try a full delete and reinstall of the 2.1.6 build and see if that works but I'll do it later and it'll take about 3 days before I will see if it's worked. It has become pretty evident to me that there was a problem with the hard fork... Why exaclty did we fork again when everything was working? We need a new wallet update asap By the way im in the process of loading the enitre blockchain again from scratch. Should be done tonight (it has been loading since 24h +) I will let you guys know if this works but I have a feeling its not going to work Edit: I def. would not send any coins until the issue is resolved. Like you said you might be at risk of never getting them back. Where is our developper? Why does it take so long to get this issue fixed? Nick: I dont think posting a tutrial on how to resync the blockchain will help. Everyone here knows how to do that. What we need is our lead developper to step up and fix this problem. As simple as that. (Just like last time we had a hard fork) Just restore everything back to the way it used to be and let it be. And by the way this is starting to get really annoying. The POST algortythm is rewarding like 3 addresses with almost all of the interest since 4 days which is unacceptable. Why do we have to deal with this every update? IM starting to wonder if this is really a coincidence? Honestly what gives? Same thing happened last hard fork I'm in the same boat. Whatever I do I can't keep the new wallet on the correct blockchain. I've turned my wallet off until a solution is available.
|
|
|
|
nickgogerty
|
|
November 10, 2016, 01:03:26 PM |
|
FYI: if you know one of these nodes personally please reach out.
this is the list of 2.1.1 IP addresses
addnode=105.186.89.65 south africa addnode=106.71.143.232 australia addnode=109.89.44.41 Belgium Brabant Wallon Chaumont-Gistoux
addnode=134.54.0.27 134.54.0.27 Belgium Antwerpen Antwerpen
addnode=144.76.71.141 144.76.71.141 Germany Bayern Nuremberg
addnode=178.117.15.134 178.117.15.134 Belgium West-Vlaanderen Waregem
addnode=203.97.255.219 New Zealand Wellington Lower Hutt
addnode=37.49.171.116 37.49.171.116 Russian Federation Irkutskaya oblast' Irkutsk
addnode=46.146.200.181 Russian Federation Permskiy kray Kondratovo
addnode=46.251.116.114 Cyprus Lemesos Limassol
addnode=58.160.91.100 Australia Victoria Melbourne
addnode=66.68.133.221 United States Texas Taylor
addnode=78.23.225.162 Belgium Oost-Vlaanderen Temse
addnode=79.68.18.52 United Kingdom England Shepton Mallet
addnode=84.197.238.43 Belgium Antwerpen Willebroek
addnode=89.138.255.162 Israel HaMerkaz Ramla
addnode=95.182.157.254 Belgium Brabant Wallon La Hulpe
addnode=96.38.132.105 United States Nevada Sparks
addnode=98.115.147.74 United States Pennsylvania Philadelphia
|
Solarcoin (§ SLR) are like airmiles. Each 1 Mhw generated gets you §1 free. Solarcoins can purchase what others will trade: USD,BTC, Soy candles..etc.
|
|
|
Nomadseif
Newbie
Offline
Activity: 38
Merit: 0
|
|
November 10, 2016, 01:48:37 PM |
|
Ok so an update today, Still only getting orphaned blocks so obviously the wallet has gone to the wrong chain but its back now cause my block height is same as chainz but still can't generate intrest. I did change the conf to have the new node list. What next? at this point I'm worried to send coins anywhere because if the wallet gets to the wrong chain at that moment I'll loose the coins as has already happened to me. Did we hear back from bittrex, have they updated their wallet? e2a: I'm back on the wrong chain again e2a: It seems that the only option for staying on the right chain is to constantly be reloading the blockchian, at least 2-3 times per day. Perhaps we have to think about what we want to do moving forward. Is there an error with the Fork? What about making a message show on all wallets that they need to update to the new version. e2a: I'm turning off my node for now, it's jumping between chains constantly. 1min on one another moment it's on the other chain. I'm gona try a full delete and reinstall of the 2.1.6 build and see if that works but I'll do it later and it'll take about 3 days before I will see if it's worked. It has become pretty evident to me that there was a problem with the hard fork... Why exaclty did we fork again when everything was working? We need a new wallet update asap By the way im in the process of loading the enitre blockchain again from scratch. Should be done tonight (it has been loading since 24h +) I will let you guys know if this works but I have a feeling its not going to work Edit: I def. would not send any coins until the issue is resolved. Like you said you might be at risk of never getting them back. Where is our developper? Why does it take so long to get this issue fixed? Nick: I dont think posting a tutrial on how to resync the blockchain will help. Everyone here knows how to do that. What we need is our lead developper to step up and fix this problem. As simple as that. (Just like last time we had a hard fork) Just restore everything back to the way it used to be and let it be. And by the way this is starting to get really annoying. The POST algortythm is rewarding like 3 addresses with almost all of the interest since 4 days which is unacceptable. Why do we have to deal with this every update? IM starting to wonder if this is really a coincidence? Honestly what gives? Same thing happened last hard fork I started fresh with a clean install and deleted all the files in the dir except the wallet file. But I noticed when downloading the chain that the total block height was changing and never matched Chainz so at that point I stopped. I'll wait for your update before I continue and perhaps there will be fix out. Would love the Dev to chime in and perhaps look into the situation.
|
|
|
|
corather
Legendary
Offline
Activity: 1708
Merit: 1000
Solarcoin.org
|
|
November 10, 2016, 02:54:46 PM |
|
Devs are aware of the situation.
|
|
|
|
onsightit
|
|
November 10, 2016, 06:21:02 PM |
|
All, We have just issued version 2.1.7, protocol version 70005, to fix the problem described below: "The reduced txn fee change caused 2.1.1 nodes to fork because 2.1.6 nodes were not paying enough fees. This in turn caused 2.1.6 nodes to fork sporadically." Please update your Qt wallet ASAP and begin staking so we can get the network moving again. Note: This update requires a Blockchain Reload. This is due to the fact that some 2.1.6 nodes are ahead of the master node, and we want to get everyone one the correct chain. After the reload, please rescan your wallet. If you are running a daemon, you can download the bootstrap.zip here: http://blockexplorer.solarcoin.org/downloads/bootstrap.zipPS: We will be notifying the exchanges and explorer ASAP. The website will be updated later today. PPS: After the rescan, you may see conflicted transactions from earned interest. You will make up the "lost" interest in future stakes.
|
VRC: VMTMcvFjZHAshmVNLY5KYVHCTqcfEnH6Bd SLR: 8W7D6D7rortYp51BK9MSrfripSoZWyVPVr BTC: 1LbgAsTDtyWEGjiSaguJhJbaHBPgcMnHfP BCC: 1Ta39PK67VXTD2xnmPNo5J9KJyBVHdYmy
|
|
|
nickgogerty
|
|
November 10, 2016, 07:11:21 PM |
|
|
Solarcoin (§ SLR) are like airmiles. Each 1 Mhw generated gets you §1 free. Solarcoins can purchase what others will trade: USD,BTC, Soy candles..etc.
|
|
|
Scalextrix
|
|
November 10, 2016, 10:41:22 PM |
|
All, We have just issued version 2.1.7, protocol version 70005, to fix the problem described below: "The reduced txn fee change caused 2.1.1 nodes to fork because 2.1.6 nodes were not paying enough fees. This in turn caused 2.1.6 nodes to fork sporadically." Please update your Qt wallet ASAP and begin staking so we can get the network moving again. Note: This update requires a Blockchain Reload. This is due to the fact that some 2.1.6 nodes are ahead of the master node, and we want to get everyone one the correct chain. After the reload, please rescan your wallet. If you are running a daemon, you can download the bootstrap.zip here: http://blockexplorer.solarcoin.org/downloads/bootstrap.zipPS: We will be notifying the exchanges and explorer ASAP. The website will be updated later today. PPS: After the rescan, you may see conflicted transactions from earned interest. You will make up the "lost" interest in future stakes. I cant get synced on the new version, I have connections but the blocks are just getting further behind
|
SolarCoin Address: 8cESoZyjFvx2Deq6VjQLqPfAwu8UXjcBkK Gridcoin Address: SAuPu8zarzQykWLGwxc6JRvW3imM8YU9wc Pinkcoin Address: 2GTnp7oRn2i6KnuwfGaFh1Ps7RZFyDe6nH MannaCurrency Address: GXDwi6W888jbQZ7a79GTaStxiQsYehisfi
|
|
|
nickgogerty
|
|
November 11, 2016, 12:39:08 AM |
|
All, We have just issued version 2.1.7, protocol version 70005, to fix the problem described below: "The reduced txn fee change caused 2.1.1 nodes to fork because 2.1.6 nodes were not paying enough fees. This in turn caused 2.1.6 nodes to fork sporadically." Please update your Qt wallet ASAP and begin staking so we can get the network moving again. Note: This update requires a Blockchain Reload. This is due to the fact that some 2.1.6 nodes are ahead of the master node, and we want to get everyone one the correct chain. After the reload, please rescan your wallet. If you are running a daemon, you can download the bootstrap.zip here: http://blockexplorer.solarcoin.org/downloads/bootstrap.zipPS: We will be notifying the exchanges and explorer ASAP. The website will be updated later today. PPS: After the rescan, you may see conflicted transactions from earned interest. You will make up the "lost" interest in future stakes. I cant get synced on the new version, I have connections but the blocks are just getting further behind did you reload the blockchain?
|
Solarcoin (§ SLR) are like airmiles. Each 1 Mhw generated gets you §1 free. Solarcoins can purchase what others will trade: USD,BTC, Soy candles..etc.
|
|
|
terciops
Member
Offline
Activity: 74
Merit: 10
|
|
November 11, 2016, 03:04:31 AM |
|
All, let me break down the 2.1.7 upgrade process for you a bit further. As there are added frustrations since this is a 'new' file for most browsers/AntiVirus/Windows stuff... From the 2.1.6 HELP -> Check for Update Say YES to everything. As that starts downloading -> Turn off your AntiVirus for the next 30 minutes (it is slowwww) Windows will moan about the download. Click - > more details Say Yes 2.1.7 is now loaded ... Let it start and load whatever it does that takes longer than booting Windows 8 on a 286 PC Reload the Block Chain - > have dinner, in fact have dinner and drinks - this is slow.... Rescan your wallet - > take a post dinner nap Wait for it all to start again Pray Rinse and repeat as required until you have a functional wallet that holds some promise that the POW rewards don't go [?].... Seriously though - well done Devs, let's hope you have the solution with 2.1.7 as 2.1.6 was driving me even more insane than I am normally T
|
SLR - 8dNrncD6mBWzPPQLMRqmk9oCxoC9N7Xfev
|
|
|
Scalextrix
|
|
November 11, 2016, 07:04:15 AM |
|
All, We have just issued version 2.1.7, protocol version 70005, to fix the problem described below: "The reduced txn fee change caused 2.1.1 nodes to fork because 2.1.6 nodes were not paying enough fees. This in turn caused 2.1.6 nodes to fork sporadically." Please update your Qt wallet ASAP and begin staking so we can get the network moving again. Note: This update requires a Blockchain Reload. This is due to the fact that some 2.1.6 nodes are ahead of the master node, and we want to get everyone one the correct chain. After the reload, please rescan your wallet. If you are running a daemon, you can download the bootstrap.zip here: http://blockexplorer.solarcoin.org/downloads/bootstrap.zipPS: We will be notifying the exchanges and explorer ASAP. The website will be updated later today. PPS: After the rescan, you may see conflicted transactions from earned interest. You will make up the "lost" interest in future stakes. I cant get synced on the new version, I have connections but the blocks are just getting further behind did you reload the blockchain? Yes Sir I did, will try again this morning
|
SolarCoin Address: 8cESoZyjFvx2Deq6VjQLqPfAwu8UXjcBkK Gridcoin Address: SAuPu8zarzQykWLGwxc6JRvW3imM8YU9wc Pinkcoin Address: 2GTnp7oRn2i6KnuwfGaFh1Ps7RZFyDe6nH MannaCurrency Address: GXDwi6W888jbQZ7a79GTaStxiQsYehisfi
|
|
|
|