Can anyone fill me in on the status of this coin? Dev gone / coin still alive, etc
|
|
|
If you have an older client... Latest build: 1.2-beta3
Source: https://github.com/palmd/philosopherstonewin32 QT (this QT contains the error reporting correction) http://sourceforge.net/projects/philosopherstone/files/-----===----- Recommended Directions for upgrading: -----===----- Windows default directory: C:\Users\Username\AppData\Roaming\Philosopherstone(If from 1.2-beta1 and full chain, simply run the new 1.2-beta3 client, done!) from old 1.2,1.1, ole "el diablo 6084 de muerte", or 'el nino Coinupcabra 9346' (very very important to delete all the bad first) 1.Make sure client is not running. If you just closed it wait at 60 seconds for it to shutdown entirely. 2.Backup wallet.dat file (copy elsewhere) from your Philosopherstone directory, this file is the one that matters. 3.Delete all files/folders inside your Philosopherstone directory except wallet.dat and philosopherstone.conf, you can keep but better to delete peers.dat 4.Then run the new 1.2-beta3 client and keep an eye on the progress as it downloads the new chain. 5.If you see coins appear and reappear and other oddities, this can be normal, don't panic. 6.If the client hangs for a long time (more than 10-15 minutes or a typical computer) start over at #1 6.It's possible to gain or lose coins during this process. This is the healing process 7.Hopefully you have now joined the rest of the good and can again be a productive member of the network
|
|
|
For more info from link above
|
|
|
Right now, I would just like the 1.0 client nodes to upgrade
|
|
|
Anyone else into the open beta later tonight?
Lets make the CyrptoCoin linkshell on Leviathan! PM me details if you are interested
|
|
|
After sync my wallet informed from 1,4K PHS -> 85 PHS. The rest of transactions showed "?" symbol. Please help me recover my PHS... sounds like they may be from one of the many dead chains, but maybe not. How did you get the coins? Solo-mine? Also what client where you on and which client are you on now? If you are using beta3 (see link below) just go through that process to delete the current blockchain and then do a fresh download of the chain to see if anything changes. https://bitcointalk.org/index.php?topic=263744.msg2938461#msg2938461
|
|
|
Buying PHS, pst with quanity and price
some on exchange: https://coinex.pw/and will be on Cryptsy soon
|
|
|
I mean that there is still too many old nodes, which are running unfixed 1.2 and <1.2.
An easy way to verify is it OK or not is open RPC console and run "getcheckpoint" command. If it prints checkpoint for the recent block, then everything is OK.
Ya there is nodes on 1.0 still....
|
|
|
Updating pool with new client!
great I plan on slowing down releases from here on out, unless there is something unforeseen that needs a quick fix. I know downtime sucks
|
|
|
if you ask me, it's desktop QT client are you still having problems with the chain getting stuck?
|
|
|
1.2-beta3 now ready, yes i combined beta 2 and 3 to simplify:
Source: https://github.com/palmd/philosopherstone
win32 QT http://rapidshare.com/files/1682016006/philosopherstone-qt12beta3.rar-----===----- Recommended Directions for upgrading: -----===----- (If from 1.2-beta1 and full chain, simply run the new 1.2-beta3 client, done!) from old 1.2,1.1, ole "el diablo 6084 de muerte", or 'el nino Coinupcabra 9346' (very very important to delete all the bad first) 1.Make sure client is not running. If you just closed it wait at 60 seconds for it to shutdown entirely. 2. Backup wallet.dat file (copy elsewhere) from your Philosopherstone directory, this file is the one that matters. 3.Delete all files/folders inside your Philosopherstone directory except wallet.dat and philosopherstone.conf, you can keep but better to delete peers.dat 4.Then run the new 1.2-beta3 client and keep an eye on the progress as it downloads the new chain. 5.If you see coins appear and reappear and other oddities, this can be normal, don't panic. 6.If the client hangs for a long time (more than 10-15 minutes or a typical computer) start over at #1 6.It's possible to gain or lose coins during this process. This is the healing process 7.Hopefully you have now joined the rest of the good and can again be a productive member of the network
|
|
|
SEems to work fine... any issues with POS shares? no issues I know of, worked making some. You notice any problems?
|
|
|
1.2-beta3 now ready, yes i combined beta 2 and 3 to simplify:
Source: https://github.com/palmd/philosopherstone
win32 bin http://rapidshare.com/files/1682016006/philosopherstone-qt12beta3.rar-----===----- Recommended Directions for upgrading: -----===----- (If from 1.2-beta1 and full chain, simply run the new 1.2-beta3 client, done!) from old 1.2,1.1,1.0 or good ole "el diablo 6084 de coin muerte" (very very important to delete all the bad first) 1.Make sure client is not running. If you just closed it wait at 60 seconds for it to shutdown entirely. 2.Backup wallet.dat file (copy elsewhere) from your Philosopherstone directory, this file is the one that matters. 3.Delete all files in your Philosopherstone directory except wallet.dat peers.dat and philosopherstone.conf 4.Then run the new 1.2-beta-3 client and keep an eye on the progress as it downloads the new chain. 5.If you see coins appear and reappear and other oddities, this can be normal, don't panic. 6.It's possible to gain or lose coins during this process. This is the healing process 7.Hopefully you have now joined the rest of the good can can again be a productive member of the network
|
|
|
We need to just copy paste this everytime
|
|
|
I will give you PHS to take the time to make a MEGA account and use that... RapidShare is just so slow and lame... Ya I don't like either, will find a better distro point soon,, just had to get the files out there.
|
|
|
Yep, 42 connections on the first, and 11 on the second wallet. Thank you!.
yes good drown out all those bad nodes When I look at getpeerinfo IS there any way to determine if one of those nodes is propagating a bad blockchain??? for example should I compare the last block rec'd and get rid of the ones that are far behind??? "addr" : "76.XXX.XXX.XXX:50505", "services" : "00000001", "lastsend" : 1376523374, "lastrecv" : 1376523713,"conntime" : 1376523298, "version" : 60006, "subver" : "/Satoshi:0.7.2/", "inbound" : true, "releasetime" : 0, "startingheight" : 12045,"banscore" : 0 digeros When I type it in a I see about 20-30% giving bad info typically they are kinda grouped on the same blocks 9346 is def people running the bugged 1.2 the well known 6084, etc in field "startingheight" there is so many on wrong chains... that is the big problem... not sure why, SO, it is the STARTING HEIGHT THAT SHOULD MATCH ACROSS THE NETWORK??? I am running V1.2 Beta and MOST of my nodes last rec'd are all within about 10-20 blocks of each other so I guess that all of them are really OK. digeros ya nodes are downloading blocks as time goes on too, some of the dead ends are mining on those broke chain too , I think anyway. They tend to live in clusters Its actually improved much since 1.2beta1
|
|
|
Yep, 42 connections on the first, and 11 on the second wallet. Thank you!.
yes good drown out all those bad nodes When I look at getpeerinfo IS there any way to determine if one of those nodes is propagating a bad blockchain??? for example should I compare the last block rec'd and get rid of the ones that are far behind??? "addr" : "76.XXX.XXX.XXX:50505", "services" : "00000001", "lastsend" : 1376523374, "lastrecv" : 1376523713,"conntime" : 1376523298, "version" : 60006, "subver" : "/Satoshi:0.7.2/", "inbound" : true, "releasetime" : 0, "startingheight" : 12045, "banscore" : 0 digeros When I type it in a I see about 20-30% giving bad info typically they are kinda grouped on the same blocks 9346 is def people running the bugged 1.2 the well known 6084, etc in field "startingheight" there is so many on wrong chains... that is the big problem... not sure why,
|
|
|
Yep, 42 connections on the first, and 11 on the second wallet. Thank you!.
yes good drown out all those bad nodes
|
|
|
|