You da man Mr. Fista
Don't forget roadtrain he the man to
Topic: [GLC] Globalcoin | 4 Year Anniversary 1.5.4! | NO IPO, NO PREMINE | [SCRYPT] - page 61. (Read 225832 times)
January 15, 2014, 11:47:20 AM
Don't forget roadtrain he the man to
January 15, 2014, 11:45:37 AM
The wallet stays on Out of synch for days, even though it has 6 active connections. I updated to the latest client, used the latest nodes, tried to rescan the blockchain, deleted peers.dat. To sum it up, I did everything.
How can I get my wallet to synch?
By the way, I used those nodes:
addnode=162.243.239.107
addnode=162.243.106.159
addnode=162.243.104.134
addnode=162.243.231.130
How can I get my wallet to synch?
By the way, I used those nodes:
addnode=162.243.239.107
addnode=162.243.106.159
addnode=162.243.104.134
addnode=162.243.231.130
Wallets are out of sync as a block has not been found for several hours due to the high difficulty and low network hashrate. The client expects blocks to be found closer to the 40 second target and therefore thinks it's out of sync when situations like this occur
Current block: 179,828
Time since last block: 15h 10m 25s
Once a block is found your wallet should show as synced (until a block is hours behind target again anyway).
Perhaps the hard fork could come in a little earlier?
Once I know most/all services etc have the new client we will be hiring a few high Hasher's to drive us up to the fork.
Good things come to those who wait and haz plans
January 15, 2014, 10:49:41 AM
I made a Globalcoin Faucet
January 15, 2014, 09:55:31 AM
The wallet stays on Out of synch for days, even though it has 6 active connections. I updated to the latest client, used the latest nodes, tried to rescan the blockchain, deleted peers.dat. To sum it up, I did everything.
How can I get my wallet to synch?
By the way, I used those nodes:
addnode=162.243.239.107
addnode=162.243.106.159
addnode=162.243.104.134
addnode=162.243.231.130
How can I get my wallet to synch?
By the way, I used those nodes:
addnode=162.243.239.107
addnode=162.243.106.159
addnode=162.243.104.134
addnode=162.243.231.130
Wallets are out of sync as a block has not been found for several hours due to the high difficulty and low network hashrate. The client expects blocks to be found closer to the 40 second target and therefore thinks it's out of sync when situations like this occur
Current block: 179,828
Time since last block: 15h 10m 25s
Once a block is found your wallet should show as synced (until a block is hours behind target again anyway).
Perhaps the hard fork could come in a little earlier?
Thanks. I will wait.
January 15, 2014, 09:48:25 AM
Perhaps the hard fork could come in a little earlier?
It could but I think we should stick to the set block.Users will have plenty of time to upgrade.
The best solution now is point additional hashpower at the network.
January 15, 2014, 08:50:37 AM
The wallet stays on Out of synch for days, even though it has 6 active connections. I updated to the latest client, used the latest nodes, tried to rescan the blockchain, deleted peers.dat. To sum it up, I did everything.
How can I get my wallet to synch?
By the way, I used those nodes:
addnode=162.243.239.107
addnode=162.243.106.159
addnode=162.243.104.134
addnode=162.243.231.130
How can I get my wallet to synch?
By the way, I used those nodes:
addnode=162.243.239.107
addnode=162.243.106.159
addnode=162.243.104.134
addnode=162.243.231.130
Wallets are out of sync as a block has not been found for several hours due to the high difficulty and low network hashrate. The client expects blocks to be found closer to the 40 second target and therefore thinks it's out of sync when situations like this occur
Current block: 179,828
Time since last block: 15h 10m 25s
Once a block is found your wallet should show as synced (until a block is hours behind target again anyway).
Perhaps the hard fork could come in a little earlier?
January 15, 2014, 08:34:05 AM
The wallet stays on Out of synch for days, even though it has 6 active connections. I updated to the latest client, used the latest nodes, tried to rescan the blockchain, deleted peers.dat. To sum it up, I did everything.
How can I get my wallet to synch?
By the way, I used those nodes:
addnode=162.243.239.107
addnode=162.243.106.159
addnode=162.243.104.134
addnode=162.243.231.130
How can I get my wallet to synch?
By the way, I used those nodes:
addnode=162.243.239.107
addnode=162.243.106.159
addnode=162.243.104.134
addnode=162.243.231.130
January 14, 2014, 09:33:53 PM
You da man Mr. Fista
January 14, 2014, 08:23:32 PM
Ok! so I have sent messages to both Coins-E and Cryptsy regarding the update, hopefully they will get sorted in time for block 180,005. Thanks again everyone for the support and patience during these fixes and of course RoadTrain for working his magic again. The fork will commence 5 blocks after the "natural" adjust resulting in a smooth transition in theory.
Enjoy!
Now I can sleep
Enjoy!
Now I can sleep
January 14, 2014, 06:19:55 PM
Excellent; people can mine on my pool then either now or when the fork happens: http://globalcoin.chriskoeber.com.
No fees, Prop payouts, stratum mining.
I'll keep checking back here for updates.
No fees, Prop payouts, stratum mining.
I'll keep checking back here for updates.
January 14, 2014, 06:11:41 PM
If your pool is on linux, you can already compile daemon from source and run. Don't forget to backup your wallet.dat anyways!
If you're on the right chain after a hard fork, it's ok. Otherwise you will run into problems.
Thus it's important to update before a hard fork happens (177 blocks from now).
If you're on the right chain after a hard fork, it's ok. Otherwise you will run into problems.
Thus it's important to update before a hard fork happens (177 blocks from now).
OK, just updated after the wallet backup; the wallet amount seems right.
Here is my getinfo (minus the balance):
Code:
getinfo:
{
"version" : 1050200,
"protocolversion" : 70001,
"walletversion" : 60000,
"blocks" : 179828,
"connections" : 4,
"proxy" : "",
"difficulty" : 12.31608598,
"testnet" : false,
"keypoololdest" : 1386916965,
"keypoolsize" : 103,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
"errors" : ""
}
Looks good?
January 14, 2014, 06:04:46 PM
I've just compiled windows binaries.
January 14, 2014, 06:00:03 PM
If your pool is on linux, you can already compile daemon from source and run. Don't forget to backup your wallet.dat anyways!
If you're on the right chain after a hard fork, it's ok. Otherwise you will run into problems.
Thus it's important to update before a hard fork happens (177 blocks from now).
If you're on the right chain after a hard fork, it's ok. Otherwise you will run into problems.
Thus it's important to update before a hard fork happens (177 blocks from now).
OK, just updated after the wallet backup; the wallet amount seems right.
Here is my getinfo (minus the balance):
Code:
getinfo:
{
"version" : 1050200,
"protocolversion" : 70001,
"walletversion" : 60000,
"blocks" : 179828,
"connections" : 4,
"proxy" : "",
"difficulty" : 12.31608598,
"testnet" : false,
"keypoololdest" : 1386916965,
"keypoolsize" : 103,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
"errors" : ""
}
Looks good?
January 14, 2014, 05:48:35 PM
I think we should start notifying pools and exchanges about the hard fork.
Windows binaries are on the way.
Windows binaries are on the way.
I will update my pool as soon as it comes out.
I am unfamiliar with hard forks so hope this isn't a stupid question:
What happens to existing coins after a hard fork?
Nothing will happen to existing coins. They will remain as normal and usable
If you continue using an older client after the hard fork goes into effect at block 180,005 and are solo mining through that client then any new coins will not be valid on the new network. This goes for pools using older clients/daemons as well. That is how I understand it anyway.
January 14, 2014, 05:38:22 PM
I think we should start notifying pools and exchanges about the hard fork.
Windows binaries are on the way.
Windows binaries are on the way.
I will update my pool as soon as it comes out.
I am unfamiliar with hard forks so hope this isn't a stupid question:
What happens to existing coins after a hard fork?
If you're on the right chain after a hard fork, it's ok. Otherwise you will run into problems.
Thus it's important to update before a hard fork happens (177 blocks from now).
Thanks much. I am on Linux so I will do this now.
January 14, 2014, 05:32:21 PM
I think we should start notifying pools and exchanges about the hard fork.
Windows binaries are on the way.
Windows binaries are on the way.
I will update my pool as soon as it comes out.
I am unfamiliar with hard forks so hope this isn't a stupid question:
What happens to existing coins after a hard fork?
If you're on the right chain after a hard fork, it's ok. Otherwise you will run into problems.
Thus it's important to update before a hard fork happens (177 blocks from now).
January 14, 2014, 05:25:08 PM
I think we should start notifying pools and exchanges about the hard fork.
Windows binaries are on the way.
Windows binaries are on the way.
I will update my pool as soon as it comes out.
I am unfamiliar with hard forks so hope this isn't a stupid question:
What happens to existing coins after a hard fork?
January 14, 2014, 05:24:19 PM
Right on guys, glad to see one of my all time favorite coins will be back in action!
January 14, 2014, 04:33:56 PM
I think we should start notifying pools and exchanges about the hard fork.
Windows binaries are on the way.
Windows binaries are on the way.
January 14, 2014, 03:49:02 PM
This news sounds good
Jump to: