Topic: [ANN] Philosopherstone - PHS | No Premine | Mandatory update 1.2Beta3 - page 27. (Read 81158 times)
August 09, 2013, 10:20:49 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...
August 09, 2013, 10:15:17 AM
there are multiple forks from what i can tell
computer 1
stuck on block 6084
computer 2
stuck on block 6311
computer 3(one with the 930 phs in wallet)
stuck on block 7564
computer 4
stuck on block 6733
computer 1
stuck on block 6084
computer 2
stuck on block 6311
computer 3(one with the 930 phs in wallet)
stuck on block 7564
computer 4
stuck on block 6733
Ive seen another 2 others ones to these.. some are being mined on too.. not even sure if the highest block one (that I'm aware of) is the main chain lol
August 09, 2013, 10:13:17 AM
So just the 2 blk files.dat for windows?
correctya i tested just moving those two (good files) over onto a directory on one of the fork dirs and it didn't work, I can post em, but not sure what good it will do
Before you attempt to copy files around you need to make sure that the daemon is NOT running.
yup, no go
August 09, 2013, 10:10:48 AM
I mined PHS several days too... One wallet only solo mining, the other- pooled. Both were stuck at the same block. I was so excited about the pos blocks...
One wallet @ 6340,
The other, with the solo mining @6336 - the coins are still confirmed. Strange...
One wallet @ 6340,
The other, with the solo mining @6336 - the coins are still confirmed. Strange...
August 09, 2013, 10:04:00 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
August 09, 2013, 10:01:50 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.
August 09, 2013, 09:52:06 AM
there are multiple forks from what i can tell
computer 1
stuck on block 6084
computer 2
stuck on block 6311
computer 3(one with the 930 phs in wallet)
stuck on block 7564
computer 4
stuck on block 6733
computer 1
stuck on block 6084
computer 2
stuck on block 6311
computer 3(one with the 930 phs in wallet)
stuck on block 7564
computer 4
stuck on block 6733
This whole thing is a great big clusterfork.
forked up from the fork up
August 09, 2013, 09:45:28 AM
there are multiple forks from what i can tell
computer 1
stuck on block 6084
computer 2
stuck on block 6311
computer 3(one with the 930 phs in wallet)
stuck on block 7564
computer 4
stuck on block 6733
computer 1
stuck on block 6084
computer 2
stuck on block 6311
computer 3(one with the 930 phs in wallet)
stuck on block 7564
computer 4
stuck on block 6733
This whole thing is a great big clusterfork.
August 09, 2013, 09:42:53 AM
there are multiple forks from what i can tell
computer 1
stuck on block 6084
computer 2
stuck on block 6311
computer 3(one with the 930 phs in wallet)
stuck on block 7564
computer 4
stuck on block 6733
computer 1
stuck on block 6084
computer 2
stuck on block 6311
computer 3(one with the 930 phs in wallet)
stuck on block 7564
computer 4
stuck on block 6733
August 09, 2013, 09:37:54 AM
what the fuck
August 09, 2013, 09:37:39 AM
My two wallets were stuck at 7841, or something. Redownloading.
When everything is cleared, I WILL give r3wt his priceless 6 LTC/930 PHS back.
When everything is cleared, I WILL give r3wt his priceless 6 LTC/930 PHS back.
August 09, 2013, 09:32:47 AM
So just the 2 blk files.dat for windows?
correctya i tested just moving those two (good files) over onto a directory on one of the fork dirs and it didn't work, I can post em, but not sure what good it will do
Before you attempt to copy files around you need to make sure that the daemon is NOT running.
August 09, 2013, 09:18:00 AM
what a mess. hindsight is a fucking bitch right now. x_x
August 09, 2013, 09:10:45 AM
So just the 2 blk files.dat for windows?
correctya i tested just moving those two (good files) over onto a directory on one of the fork dirs and it didn't work, I can post em, but not sure what good it will do
August 09, 2013, 09:06:05 AM
And... in the time I typed the previous post, it unsynced and I'm back to 6298, with ~1926 remaining.
I don't know.
johntawaki needs to get on this ASAP, at least stay around and say he's working on it, make sure it's resolved, give updates, or say SOMETHING.
He could have a nice, successful coin, even with the problems, but if he doesn't care, why should anyone else?
I don't know.
johntawaki needs to get on this ASAP, at least stay around and say he's working on it, make sure it's resolved, give updates, or say SOMETHING.
He could have a nice, successful coin, even with the problems, but if he doesn't care, why should anyone else?
but anyway ima post the correct windows files here ina min
nvm i found another fork....
Yeah, I think mine synced to the 8000ish fork, then unsynced and now it's synced on the 6299 fork, with 23 connections. Too many people on the old client? The timing would suggest that.
If someone's staying synced to the 8000ish fork, maybe their firewall is (coincidentlally) blocking out the bad nodes? Is there something to forward/not forward that could make a diff? DGC wallet would lose sync unless you forwarded a port, although it didn't cause more problems than a neverending greenbar.
August 09, 2013, 09:01:23 AM
So just the 2 blk files.dat for windows?
correct August 09, 2013, 08:48:45 AM
And... in the time I typed the previous post, it unsynced and I'm back to 6298, with ~1926 remaining.
I don't know.
johntawaki needs to get on this ASAP, at least stay around and say he's working on it, make sure it's resolved, give updates, or say SOMETHING.
He could have a nice, successful coin, even with the problems, but if he doesn't care, why should anyone else?
I don't know.
johntawaki needs to get on this ASAP, at least stay around and say he's working on it, make sure it's resolved, give updates, or say SOMETHING.
He could have a nice, successful coin, even with the problems, but if he doesn't care, why should anyone else?
but anyway ima post the correct windows files here ina min
nvm i found another fork....
August 09, 2013, 08:47:44 AM
And... in the time I typed the previous post, it unsynced and I'm back to 6298, with ~1926 remaining.
I don't know.
johntawaki needs to get on this ASAP, at least stay around and say he's working on it, make sure it's resolved, give updates, or say SOMETHING.
He could have a nice, successful coin, even with the problems, but if he doesn't care, why should anyone else?
I don't know.
johntawaki needs to get on this ASAP, at least stay around and say he's working on it, make sure it's resolved, give updates, or say SOMETHING.
He could have a nice, successful coin, even with the problems, but if he doesn't care, why should anyone else?
August 09, 2013, 08:43:01 AM
I have a windows version, one4many,.. as I posted above, are we on the same chain?
And if so, which files do these guys need
Great ... it looks like we (you and me) are on the same chain ... current block in my client is: 8216 [EDIT: 8217 now]And if so, which files do these guys need
So they need all .dat files from your Philosopherstone data directory ... WITHOUT wallet.dat and peers.dat
All the best!
one4many
So just the 2 blk files.dat for windows?
August 09, 2013, 08:38:15 AM
yeah, thats to much trouble. i want my money back Moray
Hmmm .... It is actually none of my business and I couldn't care less about your LTC's ...BUT ... If he sent you the coins using the correct chain, it is your responsibility to maintain an up-to-date client and not his. He did nothing wrong.
On the other hand, if he is/was on the wrong chain ... then he should send the LTC's back to you.
Just my 0.000005 (worthless) PHS's
there were no problems when he sent them to me two days ago(i was on the new client by the way, i downloaded v1.2.0.0.0 to make the transaction as i had never used PHS prior to the trade. then today when the fork or whatever happened bam, all my 930 phs gone. regardless he has refused to reimburse me my LTC and ignores my private messages which leads me to believe he did this knowingly
What block your client think its at?
-tb-
7564
So there are three chains??
Mine synced and block at 6290. Some reporting syncing with block in the 8000. WTF!
Going to sync one more time with only the config file.
-tb-
I believe I am synced now. Using ONLY the NEW nodes posted:
addnode=24.6.21.198
addnode=46.150.89.173
addnode=64.120.17.149
addnode=70.29.193.48
addnode=125.79.142.201
I waited for it to "sync" (at like 6290), then restarted with the -rescan option, and it fully synced. I don't think it would without the -rescan.
Jump to: