Topic: [ANN] Philosopherstone - PHS | No Premine | Mandatory update 1.2Beta3 - page 26. (Read 81158 times)
August 09, 2013, 11:23:12 AM
I would let it sit for a while, not sure why its still getting stuck. I had thought it was getting stuck before because of the competing chains, but that should not be the case with one node.
August 09, 2013, 11:21:27 AM
you guys try a -rescan with the connect= ?
-rescan just rescans the blockchain for missing transactions to the addresses in your wallet. knowing that, i still tried it out of desperation but i'm still stranded.
ya isn't there another command like -resync tho? or somesuch, might work
August 09, 2013, 11:19:07 AM
you guys try a -rescan with the connect= ?
-rescan just rescans the blockchain for missing transactions to the addresses in your wallet. knowing that, i still tried it out of desperation but i'm still stranded.
August 09, 2013, 11:16:24 AM
you guys try a -rescan with the connect= ?
August 09, 2013, 11:11:05 AM
The Dev should be the one doing this to get us all on the same chain, not me.
Here are other if you want to try again:
198.50.233.22
98.208.99.180
46.150.89.173
70.29.193.48
14.27.99.40
72.23.76.121
Here are other if you want to try again:
198.50.233.22
98.208.99.180
46.150.89.173
70.29.193.48
14.27.99.40
72.23.76.121
I don't think he wants to even deal with it apparently. thanks for trying for us ALIEN
ok i tried
Code:
connect=68.117.97.76
connect=188.252.16.109
connect=64.120.17.149
and its now showing the synchronizing with network ~2205 blocks but its stuck. thanks again for trying though man, we appreciate it.
August 09, 2013, 11:10:42 AM
The Dev should be the one doing this to get us all on the same chain, not me.
Here are other if you want to try again:
198.50.233.22
98.208.99.180
46.150.89.173
70.29.193.48
14.27.99.40
72.23.76.121
Here are other if you want to try again:
198.50.233.22
98.208.99.180
46.150.89.173
70.29.193.48
14.27.99.40
72.23.76.121
For sure -- I'm calling it quits for now...but appreciate your help.
August 09, 2013, 11:09:43 AM
The Dev should be the one doing this to get us all on the same chain, not me.
Here are other if you want to try again:
198.50.233.22
98.208.99.180
46.150.89.173
70.29.193.48
14.27.99.40
72.23.76.121
Here are other if you want to try again:
198.50.233.22
98.208.99.180
46.150.89.173
70.29.193.48
14.27.99.40
72.23.76.121
August 09, 2013, 11:07:36 AM
I am synced and here are my network stats which I believe are the correct/official block chain of v1.2:
10:40:00
{
"blocks" : 8277,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.60667636,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 20070518,
"pooledtx" : 0,
"testnet" : false
}
To get on the chain, delete all but your wallet.dat and .conf and put "connect=188.252.16.109" or "connect=64.120.17.149" in your .conf and restart. This will download only from that node so it should not get stuck downloading the chain. Once you sync you can change the connect back to addnode.
10:40:00
{
"blocks" : 8277,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.60667636,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 20070518,
"pooledtx" : 0,
"testnet" : false
}
To get on the chain, delete all but your wallet.dat and .conf and put "connect=188.252.16.109" or "connect=64.120.17.149" in your .conf and restart. This will download only from that node so it should not get stuck downloading the chain. Once you sync you can change the connect back to addnode.
Did all this (with connect=188.252.16.109; if I use 64.120.17.149 it gets me nowhere)...now I'm back to being stuck at good old block 6084...same place I was stuck yesterday.
Try this one: 68.117.97.76
tried it. that node isnt even online.
August 09, 2013, 11:05:46 AM
I am synced and here are my network stats which I believe are the correct/official block chain of v1.2:
10:40:00
{
"blocks" : 8277,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.60667636,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 20070518,
"pooledtx" : 0,
"testnet" : false
}
To get on the chain, delete all but your wallet.dat and .conf and put "connect=188.252.16.109" or "connect=64.120.17.149" in your .conf and restart. This will download only from that node so it should not get stuck downloading the chain. Once you sync you can change the connect back to addnode.
10:40:00
{
"blocks" : 8277,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.60667636,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 20070518,
"pooledtx" : 0,
"testnet" : false
}
To get on the chain, delete all but your wallet.dat and .conf and put "connect=188.252.16.109" or "connect=64.120.17.149" in your .conf and restart. This will download only from that node so it should not get stuck downloading the chain. Once you sync you can change the connect back to addnode.
Did all this (with connect=188.252.16.109; if I use 64.120.17.149 it gets me nowhere)...now I'm back to being stuck at good old block 6084...same place I was stuck yesterday.
Try this one: 68.117.97.76
August 09, 2013, 11:02:42 AM
I am synced and here are my network stats which I believe are the correct/official block chain of v1.2:
10:40:00
{
"blocks" : 8277,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.60667636,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 20070518,
"pooledtx" : 0,
"testnet" : false
}
To get on the chain, delete all but your wallet.dat and .conf and put "connect=188.252.16.109" or "connect=64.120.17.149" in your .conf and restart. This will download only from that node so it should not get stuck downloading the chain. Once you sync you can change the connect back to addnode.
10:40:00
{
"blocks" : 8277,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.60667636,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 20070518,
"pooledtx" : 0,
"testnet" : false
}
To get on the chain, delete all but your wallet.dat and .conf and put "connect=188.252.16.109" or "connect=64.120.17.149" in your .conf and restart. This will download only from that node so it should not get stuck downloading the chain. Once you sync you can change the connect back to addnode.
Did all this (with connect=188.252.16.109; if I use 64.120.17.149 it gets me nowhere)...now I'm back to being stuck at good old block 6084...same place I was stuck yesterday.
August 09, 2013, 11:01:29 AM
I am synced and here are my network stats which I believe are the correct/official block chain of v1.2:
10:40:00
{
"blocks" : 8277,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.60667636,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 20070518,
"pooledtx" : 0,
"testnet" : false
}
To get on the chain, delete all but your wallet.dat and .conf and put "connect=188.252.16.109" or "connect=64.120.17.149" in your .conf and restart. This will download only from that node so it should not get stuck downloading the chain. Once you sync you can change the connect back to addnode.
10:40:00
{
"blocks" : 8277,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.60667636,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 20070518,
"pooledtx" : 0,
"testnet" : false
}
To get on the chain, delete all but your wallet.dat and .conf and put "connect=188.252.16.109" or "connect=64.120.17.149" in your .conf and restart. This will download only from that node so it should not get stuck downloading the chain. Once you sync you can change the connect back to addnode.
lol then we lose all of our coins? and just so you know, it still get stuck at 6084
August 09, 2013, 10:54:46 AM
I am synced and here are my network stats which I believe are the correct/official block chain of v1.2:
10:40:00
{
"blocks" : 8277,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.60667636,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 20070518,
"pooledtx" : 0,
"testnet" : false
}
To get on the chain, delete all but your wallet.dat and .conf and put "connect=188.252.16.109" or "connect=64.120.17.149" in your .conf and restart. This will download only from that node so it should not get stuck downloading the chain. Once you sync you can change the connect back to addnode.
10:40:00
{
"blocks" : 8277,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.60667636,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 20070518,
"pooledtx" : 0,
"testnet" : false
}
To get on the chain, delete all but your wallet.dat and .conf and put "connect=188.252.16.109" or "connect=64.120.17.149" in your .conf and restart. This will download only from that node so it should not get stuck downloading the chain. Once you sync you can change the connect back to addnode.
August 09, 2013, 10:44:42 AM
Dev please take a look at this.. I just can't sync my wallet tried everything that some people said on this topic.. 1920 blocks remaining..
August 09, 2013, 10:31:26 AM
man this sucks. i really wanted PHS to succeed but its pretty much dead now. rather than admit defeat, the dev needs to contact an experienced dev like muddafudda to unfuck his coin. he unfucked nanotokens. its worth a shot
August 09, 2013, 10:30:51 AM
on the 8276 chain the dif is like .4 now , putting some cpu miners on it but looks like getting stake errors now in logfile so idk might be a fork
August 09, 2013, 10:30:31 AM
It seems that there were several chains out there, and it took a long time for the network to converge to the "good" chain. Please make sure you use version 1.2 and be patient. The problem, is probably many people did not upgrade to 1.2 in time, causing several chains created, now the network will take some time to select the right chain and sync up...
not to be a dick, but why the hell did you even need a client update? just what the hell was wrong with the client before? if it aint broke don't fix it.
August 09, 2013, 10:26:12 AM
It seems that there were several chains out there, and it took a long time for the network to converge to the "good" chain. Please make sure you use version 1.2 and be patient. The problem, is probably many people did not upgrade to 1.2 in time, causing several chains created, now the network will take some time to select the right chain and sync up...
Everybody is on 1.2 at this point. I was on 1.2 within a couple hours of it being posted. There isn't a single person looking at this thread that isn't using 1.2.
Every time I open up the wallet I'm on a different chain. I've been "waiting" for 24 hours now -- some people are pretty heavily invested in PHS here. There's really no other solution?
August 09, 2013, 10:24:05 AM
It seems that there were several chains out there, and it took a long time for the network to converge to the "good" chain. Please make sure you use version 1.2 and be patient. The problem, is probably many people did not upgrade to 1.2 in time, causing several chains created, now the network will take some time to select the right chain and sync up...
not to be a dick, but why the hell did you even need a client update? just what the hell was wrong with the client before? if it aint broke don't fix it.
August 09, 2013, 10:23:07 AM
My wallet still doesn't sync, even with the new nodes only... Any ideas?
August 09, 2013, 10:22:46 AM
This is definitely a nightmare for people like me who went all-in on PHS. Not only does it look like I'll be losing a lot of coins, this is going to set back the progress and value as well. The crazy part is I stuck to the basics the entire time and still ended up on a fork. Originally posted nodes, upgraded to 1.2 immediately after it was posted, solo-mined, etc. Nothing I could have done here to prevent this, apparently.
Just a bummer - hopefully when the dust settles it won't be as bad as it feels like it will right now.
Just a bummer - hopefully when the dust settles it won't be as bad as it feels like it will right now.
yeah i feel sorry for everyone who mined it and is stuck on the fork. i know it sucks for me that i spent 6 ltc on a bunk coin.
oh and for an update computer 2 synced on block 6325(was stuck on 6311) am going to try to import my wallet to that computer and see what happens
At least it was just 6 LTC. Not to downplay it -- I understand your frustration -- but I put between 8 MH and 24 MH into this thing consistently for nearly 10 days. The power costs I've invested in PHS alone are probably around $400...not to mention all of the hash power wasted that could have been mining something else. Depending on how things play out...this could easily cost me over $1000. Worst case scenario you learned a $15 lesson...I learned the same lesson for $1000. I guess I paid out-of-state tuition on this one.
I'm done going all-in on new coins -- it's primarily due to bad luck...but I've been screwed every single time.
Jump to: