 Show Posts
|
|
Pages: [1]
|
I have been having syncing issues with the new wallet and now a checkpoint error. Is there a problem we need to know about? What changes were made? Can't play the game if I don't know the rules.
Also the manipulated trading on YObit is ridiculous right now.
same here. checkpoint error. using new wallet. sample from log file: ........... REORGANIZE: Disconnect 2277 blocks; 0acbf699b3d4e33fc0c7..3c5f4afc4c4133f20103 REORGANIZE: Connect 4210 blocks; 0acbf699b3d4e33fc0c7..ffaf8fda252acd26f16a ERROR: DisconnectBlock() : WriteBlockIndex failed ERROR: Reorganize() : DisconnectBlock 31560d2244aba8362b1a failed InvalidChainFound: invalid block=ffaf8fda252acd26f16a height=1522166 trust=10279014715052 date=03/22/16 16:41:42 InvalidChainFound: current best=3c5f4afc4c4133f20103 height=1520233 trust=10289947094877 date=03/22/16 14:08:57 ERROR: SetBestChain() : Reorganize failed ERROR: ProcessSyncCheckpoint: SetBestChain failed for sync checkpoint ffaf8fda252acd26f16af590a35c1ef34a9130544702ec56627f368054f771e0 REORGANIZE REORGANIZE: Disconnect 2277 blocks; 0acbf699b3d4e33fc0c7..3c5f4afc4c4133f20103 REORGANIZE: Connect 4210 blocks; 0acbf699b3d4e33fc0c7..ffaf8fda252acd26f16a ERROR: DisconnectBlock() : WriteBlockIndex failed ERROR: Reorganize() : DisconnectBlock 31560d2244aba8362b1a failed InvalidChainFound: invalid block=ffaf8fda252acd26f16a height=1522166 trust=10279014715052 date=03/22/16 16:41:42 InvalidChainFound: current best=3c5f4afc4c4133f20103 height=1520233 trust=10289947094877 date=03/22/16 14:08:57 ERROR: SetBestChain() : Reorganize failed ERROR: ProcessSyncCheckpoint: SetBestChain failed for sync checkpoint ffaf8fda252acd26f16af590a35c1ef34a9130544702ec56627f368054f771e0 Flushed 13992 addresses to peers.dat 30ms ResendWalletTransactions() RandAddSeed() 185668 bytes -------------------------- etc. etc. etc. |
|
|
|
|
Hello All,
When I check the difficulty I get:
"proof-of-stake" : 0.05457057,
"search-interval" : 1
Isn't this high for a POS-difficulty? My other coins: TEK, HBN, CAP.... are at least x10 lower.
I have not staked in along time.
Greetings, Alex_Koekie
|
|
|
|
Some stuff on my mind: 1. We should change our .conf from connect to addnote, do we change listen=0 to listen=1 as well? 2. What does it do actually (the listen command), accept incoming connections? 3. I'm currently at block 511961 - blockhash 92c5ee5b968e0810373fc346f7dde4a2735db0d72c8a47dffa3d7a928bdecfda , is this the right chain? 4. If 3 is yes, the blockexplorer http://tek.blockx.info/get/chain/TekCoin is still on wrong chain right? Greetz, Alex_Koekie |
|
|
|
I'm at IP 82.171.127.104 , don't know if it does support incoming. How do i check?
If needed I know how to set up a portforward, but don't know if that is what you mean.
Your node is not reachable so it is not accepting incoming connections - that or it already banned my IP  Can you post the config file? Or do you only need those 3 lines?
If it's supposed to look like this then I'm fine:
listen=0
server=1
daemon=1
rpcuser=you
rpcpassword=pass
rpcallowip=127.0.0.1
rpcallowip=192.168.*.*
Port=8514
RPCPort=18514
connect=70.181.40.178
connect=89.201.186.50
If not... I'll edit to delete this.
That will work. OK, it did add portforwarding for 8514 and 18514 now, but if it does the trick? My config is like the one above. |
|
|
|
@subSTRATA Great Work!!! I followed the instructions and are now synced with 70.181.40.178. No other nodes connected yet. I'm at block 507098, blockhash is 32ca21806c77de224765b62b0a6a8639b53677c20d41b7c563fa083878190ca0 "proof-of-work" : 250768.75421742, "proof-of-stake" : 0.00006144, I did put a copy of the blockchain until the day before the fork online here (glad i remembered to backup for once), it's the blk0001.dat file, this is the one used for bootstrap, right?: https://mega.co.nz/#!bx1zQQhD!HOlas1z4_Rg7KT9sfrxiUCuONDweLRqFjursU33DVXEAwaiting further instructions!  Can your node accept incoming connections? If yes please post your IP so I can add it to list. I'm at IP 82.171.127.104 , don't know if it does support incoming. How do i check? If needed I know how to set up a portforward, but don't know if that is what you mean. |
|
|
|
@subSTRATA Great Work!!! I followed the instructions and are now synced with 70.181.40.178. No other nodes connected yet. I'm at block 507098, blockhash is 32ca21806c77de224765b62b0a6a8639b53677c20d41b7c563fa083878190ca0 "proof-of-work" : 250768.75421742, "proof-of-stake" : 0.00006144, I did put a copy of the blockchain until the day before the fork online here (glad i remembered to backup for once), it's the blk0001.dat file, this is the one used for bootstrap, right?: https://mega.co.nz/#!bx1zQQhD!HOlas1z4_Rg7KT9sfrxiUCuONDweLRqFjursU33DVXEAwaiting further instructions! |
|
|
|
I'm not able to help the programming as well, but I do have a backup of the blockchain the day before the fork(s) Is it of any use to upload it so people can bootstrap and don't have to resync using the network? |
|
|
|
Can someone please post a config file my system seems to missing the file. Thanks...
A tekcoin.conf file? Mine is like this: listen=1 daemon=1 server=1 rpcuser=your username rpcpassword=your password rpcport=18514 port=8514 rpcallowip=127.0.0.1 rpcallowip=your internal network ip rpcconnect=your internal network ip addnode=80.56.202.177 addnode=86.181.242.68 addnode=?unsure what other nodes to use at the moment? edit: changed the nodes to the latest posted by subSTRATA |
|
|
|
|
Hello to all,
Reading along in this topic for quite some time, I'm sorry to join the conversation at such a hard moment, the whole repair operation went so smooth until.......
I'm not a programmer and still learning more about how the coins work, but how do we tell which is the right fork? And if we already know, can you post a blocknumber and checksum so i can check my wallet is on the right fork?
As a solution, a new wallet rejecting old ones seems legit to me. We only have one exchange for TEK and a few important pools, so if they start to use it, the community will be forced to follow, right? If I'm wrong, continue your work, I'll continue learning.
Good luck solving the issue and greetings,
Alex_Koekie
|
|
|
|
I've never heard of allcoin. Seems sketchy to me. I'd rather trade on mintpal or bittrex but cryptsy is good enough and I've never had major problems with them.
Hello to All,  First post here on HBN topic, but reading it for a long time. BTW, thanks for all the hard work Tranz and others! Just want to let you know that I've been trading GRW on Allcoin for some time and found it very reliable so far. So this new HBN market, even small, seems like a great step ahead to me! Greetings, Alex_Koekie |
|
|
|
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 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! |
|
|
|
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! :-) |
|
|
|
|
Same here, followed your link and it shows:
"version" : "v1.3.0.0-beta",
"protocolversion" : 60007,
"walletversion" : 60000,
|
|
|
|
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. |
|
|
|
67.211.45.66:17177
155.210.52.121:17177
I added these two peers, same thing unfortunately. [
{
"addr" : "67.211.45.66",
"services" : "00000000",
"lastsend" : 1405285267,
"lastrecv" : 1405285462,
"conntime" : 1405285267,
"bytessent" : 135,
"bytesrecv" : 366,
"blocksrequested" : 0,
"version" : 0,
"subver" : "",
"inbound" : false,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 6
},
{
"addr" : "155.210.52.121",
"services" : "00000000",
"lastsend" : 1405285268,
"lastrecv" : 1405285462,
"conntime" : 1405285268,
"bytessent" : 135,
"bytesrecv" : 366,
"blocksrequested" : 0,
"version" : 0,
"subver" : "",
"inbound" : false,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 6
},
{
"addr" : "162.243.13.186",
"services" : "00000001",
"lastsend" : 1405285479,
"lastrecv" : 1405285479,
"conntime" : 1405285268,
"bytessent" : 811740,
"bytesrecv" : 3663879,
"blocksrequested" : 0,
"version" : 70001,
"subver" : "/GrowthCoin:1.3.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 119069,
"banscore" : 0
}
]
I thought it may have been because I had been banned for an older version, but I'm pretty sure I didn't start growthcoin before updating. 162.243.13.186 - the only peer who can give me blocks - is still at height 119069, even after several restarts of the client, so for some reason they are not syncing either. edit: just noticed that the two -1 peers are showing a banscore of 6 (?!) Strange.... This is my getpeerinfo:
00:08:05

[
{
"addr" : "23.92.53.139:17177",
"services" : "00000001",
"lastsend" : 1405289246,
"lastrecv" : 1405289246,
"conntime" : 1405264493,
"version" : 60007,
"subver" : "/GrowthCoin:1.3.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 590674,
"banscore" : 0
},
{
"addr" : "67.211.45.66:17177",
"services" : "00000001",
"lastsend" : 1405289245,
"lastrecv" : 1405289245,
"conntime" : 1405264493,
"version" : 60007,
"subver" : "/GrowthCoin:1.3.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 590674,
"banscore" : 0
},
{
"addr" : "188.226.155.94:17177",
"services" : "00000001",
"lastsend" : 1405289246,
"lastrecv" : 1405289246,
"conntime" : 1405264500,
"version" : 60007,
"subver" : "/GrowthCoin:1.3.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 590674,
"banscore" : 0
},
{
"addr" : "155.210.52.121:17177",
"services" : "00000001",
"lastsend" : 1405289246,
"lastrecv" : 1405289246,
"conntime" : 1405264501,
"version" : 60007,
"subver" : "/GrowthCoin:1.3.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 590674,
"banscore" : 0
},
{
"addr" : "82.9.77.178:17177",
"services" : "00000001",
"lastsend" : 1405289246,
"lastrecv" : 1405289245,
"conntime" : 1405283818,
"version" : 60007,
"subver" : "/GrowthCoin:1.3.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 591095,
"banscore" : 0
},
{
"addr" : "162.243.13.186:17177",
"services" : "00000000",
"lastsend" : 1405286555,
"lastrecv" : 1405287507,
"conntime" : 1405286555,
"version" : 0,
"subver" : "",
"inbound" : false,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 3
}
]
Note that the values of startingheight are not the same when you compare the ip's. |
|
|
|
Have managed to negotiate with 162.243.13.186, but that is only at height 119069, and does not appear to be advancing. This is the only peer that has replied to the version message... no such luck with 188.226.240.91, 128.199.191.230, 23.92.53.139, 77.131.6.113, 64.188.164.77, 82.9.77.178, 108.61.18.94
I should add that I started from scratch as per the OP. Empty db, only remnant file being the wallet.
I'm currently connected to: 23.92.53.139:17177 67.211.45.66:17177 188.226.155.94:17177 155.210.52.121:17177 82.9.77.178:17177 All are version: GrowthCoin:1.3.0 None of them shows height -1. I hope it's helpful to you. |
|
|
|
Hello to all! I'm new to this forum and following the GRW topic for some while. My client is of number v1.3.0.0-beta and just synced with the 1.3.0.0 node found here http://grw.blockx.info/connected-nodes. I checked getpeers, but it didn't connect to Satoshi:1.2.1 node found on the same site. I'm at block 590713, but wonder if I'm on the right fork. Can you explain me how to check this? Greetings, Alex_Koekie |
|
|
|
|
