[ANN] Philosopherstone - PHS | No Premine | Mandatory update 1.2Beta3

[SoulSlayerPT]

My wallet still doesn't sync, even with the new nodes only... Any ideas?

[1714825932]

1714825932

[1714825932]

1714825932

[1714825932]

1714825932

[DogtownHero]

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.

[bholzer]

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?

[one4many]

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.

Read subject ... read 1st post ... start thinking ... that's why.

[Palmdetroit]

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

[r3wt]

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

[SoulSlayerPT]

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..

[A L I E N]

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.

[r3wt]

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.

lol then we lose all of our coins? and just so you know, it still get stuck at 6084

[bholzer]

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.

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.

[A L I E N]

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.

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

[r3wt]

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.

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.

[A L I E N]

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

[bholzer]

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

For sure -- I'm calling it quits for now...but appreciate your help.

[r3wt]

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

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.

[Palmdetroit]

you guys try a -rescan with the connect= ?

[r3wt]

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.

[Palmdetroit]

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

[A L I E N]

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.

[r3wt]

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.

because the dev attempted to change block rewards of blocks prior to current height of the update. rookie mistake. now the coin is as good as dead, because the chain is all screwed up. the only way to fix it now would be to go back, fork it a few blocks before where the reward changes, re release then let everyone sync. then make a checkpoint for the current block (8277 or whatever), then put a checkpoint into a new source for that block height, then re release and pray like hell it works. of course it won't work because he's manipulated block values of a block that had already been mined.