unick (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 14, 2014, 08:31:02 PM |
|
Strange things happening.... I'm on the right blockchain, i used the getblockhash command. Thanks Unick! Current shows: getblockhash 592973 - 0000000cd886aa4eb844f5354e21cdc3a2e9af26cea2f18c7db09e904ca31aa8 Using the betaclient from here: https://www.dropbox.com/s/5xkk8npt6enabuk/GrowthCoin-Qt.zip"version" : "v1.3.0.0-beta", "protocolversion" : 60007, "walletversion" : 60000, But I'm only getting orphans when staking. Some go up to 10 confirmations and then get rejected. this is the wrong version you should have protocol 70001 please download the pre-release version (1.3.1.0) from this link https://github.com/iamunick/growthcoin/releasesthe version you should read in your client is 1.3.0.1 I just grabbed the Qt from the github link, and I get "version" : "v1.3.0.0-beta", "protocolversion" : 60007, "walletversion" : 60001, Hum, let me check then. it's supposed to be protocol 70001
|
|
|
|
Alex_Koekie
Newbie
Offline
Activity: 17
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 14, 2014, 08:34:06 PM |
|
Same here, followed your link and it shows:
"version" : "v1.3.0.0-beta", "protocolversion" : 60007, "walletversion" : 60000,
|
|
|
|
unick (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 14, 2014, 08:35:48 PM |
|
you guys are right,
I'm going to ask Presstab to build the Qt client for windows. I'm on a Mac and can't do it since my virtualbox is not configured properly yet.
sorry about that
|
|
|
|
scryptographer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 14, 2014, 08:38:20 PM |
|
you guys are right,
I'm going to ask Presstab to build the Qt client for windows. I'm on a Mac and can't do it since my virtualbox is not configured properly yet.
sorry about that
No worries. I still got 10 hours till my next block stakes (:
|
|
|
|
unick (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 14, 2014, 08:44:04 PM |
|
Same here, followed your link and it shows:
"version" : "v1.3.0.0-beta", "protocolversion" : 60007, "walletversion" : 60000,
also, the network shouldn't reject blocks from protocol version 60007, so if you can share your debug.log when the rejection occcurs, I would like to take a look at it. thanks
|
|
|
|
|
noise23
Legendary
Offline
Activity: 968
Merit: 1002
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 14, 2014, 09:11:30 PM |
|
It seems like we just got another fork - right now grw.acidpool.com and grw.blockx.info are at 593090 getblockhash 593090 000000011be8c3e99e0baffb7100161e7568a5cf787cbbe7d6045678b40de8b5
my home pc win wallet and grw.multi-pool.info are at 593107 from my pc wallet - getblockhash 593090 3c56abc5208295cbc2c6cfa27d5ff282d1554a94b4e5bd054b8c661f66fcb099
|
|
|
|
unick (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 14, 2014, 09:20:02 PM |
|
thanks for the quick reply ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
Alex_Koekie
Newbie
Offline
Activity: 17
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 14, 2014, 09:21:56 PM |
|
Same here, followed your link and it shows:
"version" : "v1.3.0.0-beta", "protocolversion" : 60007, "walletversion" : 60000,
also, the network shouldn't reject blocks from protocol version 60007, so if you can share your debug.log when the rejection occcurs, I would like to take a look at it. thanks Your 1.3.0.0 github version does seems to stake, now up to 35 confirms, didn't get that with the old 1.3.0.0 dropbox version. Don't know if its relevant, but I remember it showed networkweight of 5000 while my walletweight alone is 17k+ The github 1.3.0.0 version shows more realistic numbers: wallet 17k and networkweight 57065.4 Will try the new wallet from presstab now. BTW the new wallet looks great! :-)
|
|
|
|
unick (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 14, 2014, 09:22:13 PM |
|
It seems like we just got another fork - right now grw.acidpool.com and grw.blockx.info are at 593090 getblockhash 593090 000000011be8c3e99e0baffb7100161e7568a5cf787cbbe7d6045678b40de8b5
my home pc win wallet and grw.multi-pool.info are at 593107 from my pc wallet - getblockhash 593090 3c56abc5208295cbc2c6cfa27d5ff282d1554a94b4e5bd054b8c661f66fcb099
this should not be a problem, the block your home pc and multi-pool are on is a PoS block, if that chains wins to be the longest, it should reorganize and sync for all the network. But I'll still keep an eye on it
|
|
|
|
unick (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 14, 2014, 09:25:43 PM |
|
Same here, followed your link and it shows:
"version" : "v1.3.0.0-beta", "protocolversion" : 60007, "walletversion" : 60000,
also, the network shouldn't reject blocks from protocol version 60007, so if you can share your debug.log when the rejection occcurs, I would like to take a look at it. thanks Your 1.3.0.0 github version does seems to stake, now up to 35 confirms, didn't get that with the old 1.3.0.0 dropbox version. Don't know if its relevant, but I remember it showed networkweight of 5000 while my walletweight alone is 17k+ The github 1.3.0.0 version shows more realistic numbers: wallet 17k and networkweight 57065.4 Will try the new wallet from presstab now. BTW the new wallet looks great! :-) ok, thanks for the heads up, orphans are normal when staking, it is still based on luck so that might just have been the issue. Glad to know it's working then ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) netstakeweight and your wallet weight are surprisingly not related. They are 2 metrics calculated differently. while your wallet weight is based on your blocks age, the netstakeweight is based on the last few blocks of stake generated. hope this makes it a little bit more sense
|
|
|
|
Alex_Koekie
Newbie
Offline
Activity: 17
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 14, 2014, 10:25:58 PM |
|
Same here, followed your link and it shows:
"version" : "v1.3.0.0-beta", "protocolversion" : 60007, "walletversion" : 60000,
also, the network shouldn't reject blocks from protocol version 60007, so if you can share your debug.log when the rejection occcurs, I would like to take a look at it. thanks Your 1.3.0.0 github version does seems to stake, now up to 35 confirms, didn't get that with the old 1.3.0.0 dropbox version. Don't know if its relevant, but I remember it showed networkweight of 5000 while my walletweight alone is 17k+ The github 1.3.0.0 version shows more realistic numbers: wallet 17k and networkweight 57065.4 Will try the new wallet from presstab now. BTW the new wallet looks great! :-) ok, thanks for the heads up, orphans are normal when staking, it is still based on luck so that might just have been the issue. Glad to know it's working then ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) netstakeweight and your wallet weight are surprisingly not related. They are 2 metrics calculated differently. while your wallet weight is based on your blocks age, the netstakeweight is based on the last few blocks of stake generated. hope this makes it a little bit more sense New wallet working correctly. Shows version: "version" : "v1.3.0.1-beta", "protocolversion" : 70001, "walletversion" : 60000, And stakes without orphans, already 6 pos stakes complete, 50+ confirms! I did lose all my old stakes of tonight, but i suppose it was because i was on the wrong fork as well as noise23. My wallet now shows: getblockhash 593090 - 000000011be8c3e99e0baffb7100161e7568a5cf787cbbe7d6045678b40de8b5 But with my old stakes (those who disappeared), it showed getblockhash 593090 - 3c56abc5208295cbc2c6cfa27d5ff282d1554a94b4e5bd054b8c661f66fcb099 I guess getblockhash 593090 - 000000011be8c3e99e0baffb7100161e7568a5cf787cbbe7d6045678b40de8b5 it the current and correct chain, am i correct? BTW your explanation of walletweight i understand, i guess that the comparison of both weights it is also the way the "next stake in xxx days" message is calculated. BTW2....... Are the download links on the grw site and github updated? This to prevent new users from installing the old client. Thanks for all the replies, I hope my information is perceived as helpful and not as complaining, you and all others are doing a great job!
|
|
|
|
SolidStateSurvivor
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 14, 2014, 10:43:50 PM |
|
Yes, I should have said something, I check them both and they were exactly the same size, but I thought not to, I even wrote this without posting it: (That is talking about the new one posted earlier today.) Also when version 1.3.0.1 didn't show up, I was a little curious.
|
Founding member of Hashmeisters Inc...
|
|
|
SolidStateSurvivor
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 14, 2014, 10:47:04 PM Last edit: July 14, 2014, 11:23:34 PM by SolidStateSurvivor |
|
I am getting this error when I am trying to build the windows-qt on ubuntu, with VM.
Starting target Checking if target is up. Preparing build environment qt-win32-4.7.4-gitian.zip 100% 21MB 21.1MB/s 00:01 boost-win32-1.49.0-gitian2.zip 100% 17MB 17.3MB/s 00:01 growthcoin-deps-1.2.0.zip 100% 4050KB 4.0MB/s 00:00 growthcoin.zip 100% 58MB 29.2MB/s 00:02 Updating apt-get repository (log in var/install.log) Installing additional packages (log in var/install.log) Grabbing package manifest Creating build script (var/build-script) Running build script (log in var/build.log) bin/gbuild:21:in `system!': failed to run on-target setarch i386 bash -x < var/build-script > var/build.log 2>&1 (RuntimeError) from bin/gbuild:118:in `build_one_configuration' from bin/gbuild:235 from bin/gbuild:230:in `each' from bin/gbuild:230 from bin/gbuild:228:in `each' from bin/gbuild:228
So I'm currently looking in the "gitian-win32.yml" and comparing it with other wallet that works to build, to see if I can find the error there.
Also going to look in build script (var/build-script) & (log in var/build.log)
I was thinking I could build the windows wallet, when it is needed, but it doesn't seem to work atm.
|
Founding member of Hashmeisters Inc...
|
|
|
unick (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 15, 2014, 12:43:28 AM |
|
Same here, followed your link and it shows:
"version" : "v1.3.0.0-beta", "protocolversion" : 60007, "walletversion" : 60000,
also, the network shouldn't reject blocks from protocol version 60007, so if you can share your debug.log when the rejection occcurs, I would like to take a look at it. thanks Your 1.3.0.0 github version does seems to stake, now up to 35 confirms, didn't get that with the old 1.3.0.0 dropbox version. Don't know if its relevant, but I remember it showed networkweight of 5000 while my walletweight alone is 17k+ The github 1.3.0.0 version shows more realistic numbers: wallet 17k and networkweight 57065.4 Will try the new wallet from presstab now. BTW the new wallet looks great! :-) ok, thanks for the heads up, orphans are normal when staking, it is still based on luck so that might just have been the issue. Glad to know it's working then ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) netstakeweight and your wallet weight are surprisingly not related. They are 2 metrics calculated differently. while your wallet weight is based on your blocks age, the netstakeweight is based on the last few blocks of stake generated. hope this makes it a little bit more sense New wallet working correctly. Shows version: "version" : "v1.3.0.1-beta", "protocolversion" : 70001, "walletversion" : 60000, And stakes without orphans, already 6 pos stakes complete, 50+ confirms! I did lose all my old stakes of tonight, but i suppose it was because i was on the wrong fork as well as noise23. My wallet now shows: getblockhash 593090 - 000000011be8c3e99e0baffb7100161e7568a5cf787cbbe7d6045678b40de8b5 But with my old stakes (those who disappeared), it showed getblockhash 593090 - 3c56abc5208295cbc2c6cfa27d5ff282d1554a94b4e5bd054b8c661f66fcb099 I guess getblockhash 593090 - 000000011be8c3e99e0baffb7100161e7568a5cf787cbbe7d6045678b40de8b5 it the current and correct chain, am i correct? BTW your explanation of walletweight i understand, i guess that the comparison of both weights it is also the way the "next stake in xxx days" message is calculated. BTW2....... Are the download links on the grw site and github updated? This to prevent new users from installing the old client. Thanks for all the replies, I hope my information is perceived as helpful and not as complaining, you and all others are doing a great job! excellent news that everything is staking away ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Losing those Stakes is not that of a big deal since they will stake again on the correct chain. getblockhash 593090 - 000000011be8c3e99e0baffb7100161e7568a5cf787cbbe7d6045678b40de8b5 is indeed on the right chain. You are good there. Wallet weight is based on your coin age. but presently, this information is wrong since no coins will stake before about 8.8 days of age. It will be necessary to create a hard fork and make changes to the stake modifier in order to get the desired 5 days of minimum age. The link on the site (I assume http://growthco.in) I can't change, the link on the github has been updated for the pre-release download. I think it's neilh that provides the website, I'll make sure he gets the info to update the version on the site
|
|
|
|
unick (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 15, 2014, 12:45:58 AM |
|
I am getting this error when I am trying to build the windows-qt on ubuntu, with VM.
Starting target Checking if target is up. Preparing build environment qt-win32-4.7.4-gitian.zip 100% 21MB 21.1MB/s 00:01 boost-win32-1.49.0-gitian2.zip 100% 17MB 17.3MB/s 00:01 growthcoin-deps-1.2.0.zip 100% 4050KB 4.0MB/s 00:00 growthcoin.zip 100% 58MB 29.2MB/s 00:02 Updating apt-get repository (log in var/install.log) Installing additional packages (log in var/install.log) Grabbing package manifest Creating build script (var/build-script) Running build script (log in var/build.log) bin/gbuild:21:in `system!': failed to run on-target setarch i386 bash -x < var/build-script > var/build.log 2>&1 (RuntimeError) from bin/gbuild:118:in `build_one_configuration' from bin/gbuild:235 from bin/gbuild:230:in `each' from bin/gbuild:230 from bin/gbuild:228:in `each' from bin/gbuild:228
So I'm currently looking in the "gitian-win32.yml" and comparing it with other wallet that works to build, to see if I can find the error there.
Also going to look in build script (var/build-script) & (log in var/build.log)
I was thinking I could build the windows wallet, when it is needed, but it doesn't seem to work atm.
Haven't had time to play with the gitian builder. I'm not even sure these files are configured properly, if you make any changes and you make it work, let me know ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
presstab
Legendary
Offline
Activity: 1330
Merit: 1000
Blockchain Developer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 15, 2014, 01:04:37 AM |
|
Ahh the GRW community is very crypto saavy. Seems like every other person knows how to compile, check forks, etc. Good luck here guys! Make my GRW grow!
|
|
|
|
SolidStateSurvivor
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 15, 2014, 01:29:14 PM |
|
Haven't had time to play with the gitian builder. I'm not even sure these files are configured properly, if you make any changes and you make it work, let me know ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) They are not configured? Hmm, then that might be it. I didn't have any luck, with it. Seems like they compile fine in windows, though. But I don't do that, I've been doing these kind of things in Linux since the late 90s, almost. I'll find another coin wallet, build it with gitian and see if I can find out what is missing.
|
Founding member of Hashmeisters Inc...
|
|
|
|
ice00
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 15, 2014, 05:48:23 PM |
|
It is from this morning that I try to sync the pool using the bootstrap of day 11. Now it is blocked at 496288 and seems to not go ahead. The daemon is the latest from source.
|
NXT: 1408301140704352478 EMC: Ec2TpuRxcYr4WHMp12vZYck5ch3ymzskbZ
|
|
|
|