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

[Palmdetroit]

Yep, 42 connections on the first, and 11 on the second wallet. Thank you!.

yes good drown out all those bad nodes 

[digeros]

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

[Palmdetroit]

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,

[digeros]

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

[Palmdetroit]

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

[orco#2]

My 11400 PHS are still floating in aether even after update of clientr :{  Can a dev find those for me


Here is the transaction ID from wallet to new wallet.  is for  -11447.836952 PHS

e916fe7bde22e43a87c3b4f9222d512629f16cb80473f5e2a6726afb82841cdc

Of course it got hung in faulty 1.2 client.  Here is what it comes through as on new wallet +72.471062 PHS

Here is the interesting thing... the Transaction ID on this end is

c139f3e4945d2644a067601461393c4a71ab942406aacef8df9938cc8a1c5227



Very Strange


Wallet address to:  9WA9jGyg7bMkdvyyFu9tkXUBtTZrTXmPYb

Wallet Address from:  9UUDu4ksjpRFfdG6j6SC6MGmWgJUZryKUJ

[digeros]

My 11400 PHS are still floating in aether even after update of clientr :{  Can a dev kind those for me

did you update to version 1.2 beta   and then delete all files in AppData EXCEPT wallet and config files -- digeros

Newest working version
https://github.com/palmd/philosopherstone

win32 client
http://rapidshare.com/files/2711045654/philosopherstone-qt12_beta1.rar

[orco#2]

yep

[orco#2]

this just happened

{
"mismatched spent coins" : 51,
"amount affected by repair" : 10015.90270900
}

what it mean after repair?
 I do not see the coins?


Dang!

It has fixed itself! The wallterrepair had to be down on old wallet!

Booya!  Digeros pls provide wallet for help payment!


Well now it is moving my coins from balance to stake....

I am sure that will take a while to correct

[daemonfox]

My 11400 PHS are still floating in aether even after update of clientr :{  Can a dev kind those for me

did you update to version 1.2 beta   and then delete all files in AppData EXCEPT wallet and config files -- digeros

Newest working version
https://github.com/palmd/philosopherstone

win32 client
http://rapidshare.com/files/2711045654/philosopherstone-qt12_beta1.rar

I will give you PHS to take the time to make a MEGA account and use that... RapidShare is just so slow and lame...

[digeros]

this just happened

{
"mismatched spent coins" : 51,
"amount affected by repair" : 10015.90270900
}

what it mean after repair?
 I do not see the coins?


Dang!

It has fixed itself! The wallterrepair had to be down on old wallet!

Booya!  Digeros pls provide wallet for help payment!


Well now it is moving my coins from balance to stake....

I am sure that will take a while to correct

the net is quite quick I notice stakes made then within about two hours unlocked and POS credit given.  so patience let it give you the credits first... digeros

[digeros]

My 11400 PHS are still floating in aether even after update of clientr :{  Can a dev kind those for me

did you update to version 1.2 beta   and then delete all files in AppData EXCEPT wallet and config files -- digeros

Newest working version
https://github.com/palmd/philosopherstone

win32 client
http://rapidshare.com/files/2711045654/philosopherstone-qt12_beta1.rar

I will give you PHS to take the time to make a MEGA account and use that... RapidShare is just so slow and lame...

DONE:  you can get the BETA Version of 1.2 Philosopherstone-qt.exe  in RAR format  at the following link:

https://mega.co.nz/#!2BcElLza!DvzqCDg0NXSNfRZQ5TIa6y_ssBAslUjk3fF4WO8em1k   (the Bang that mega uses usually busts the link, so copy and paste into browser is best)

[sheinsha]

this just happened

{
"mismatched spent coins" : 51,
"amount affected by repair" : 10015.90270900
}

what it mean after repair?
 I do not see the coins?


Dang!

It has fixed itself! The wallterrepair had to be down on old wallet!

Booya!  Digeros pls provide wallet for help payment!


Well now it is moving my coins from balance to stake....

I am sure that will take a while to correct

If you had read my comment a few days ago you would have saved some time... -->

{
"wallet check passed" : true
}

additional data.  The transaction was between client 1.0 and client 1.2 without being synced.

if I use old wallet, the transaction id is e916fe7bde22e43a87c3b4f9222d512629f16cb80473f5e2a6726afb82841cdc , but it has 0 confirms.

Maybe this is clue to you?

Well on the old wallet, back it up, and then type this in console:

Code:

repairwallet

and post results

[Palmdetroit]

My 11400 PHS are still floating in aether even after update of clientr :{  Can a dev kind those for me

did you update to version 1.2 beta   and then delete all files in AppData EXCEPT wallet and config files -- digeros

Newest working version
https://github.com/palmd/philosopherstone

win32 client
http://rapidshare.com/files/2711045654/philosopherstone-qt12_beta1.rar

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.

[Palmdetroit]

My 11400 PHS are still floating in aether even after update of clientr :{  Can a dev kind those for me

did you update to version 1.2 beta   and then delete all files in AppData EXCEPT wallet and config files -- digeros

Newest working version
https://github.com/palmd/philosopherstone

win32 client
http://rapidshare.com/files/2711045654/philosopherstone-qt12_beta1.rar

We need to just copy paste this everytime 

[Palmdetroit]

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

[digeros]

1.2-beta3 now ready, yes i combined beta 2 and 3 to simplify:

this included updated connectivity , upnp, checkpoints and more

Please get some nodes up and report back if any problems!

Source:
https://github.com/palmd/philosopherstone

win32 bin
http://rapidshare.com/files/1682016006/philosopherstone-qt12beta3.rar

SEems to work fine... any issues with POS shares? 

Here is the link to the new Beta 3 on Mega

https://mega.co.nz/#!HJ03VaRI!ExQdmXeMESBiYtwKpRyLWip48mUxrL63f2jyKrcI0v4  Copy and paste it

[Palmdetroit]

SEems to work fine... any issues with POS shares? 

no issues I know of, worked making some.  You notice any problems?

[stas]

it fails to synch... remains on the block 6171

[Balthazar]

Remove blockchain and try again. If still no results then try to add something like -banscore=999999 into command line keys. If even this doesn't help you, then try


-addnode=46.150.89.173 -addnode=71.187.248.95 -addnode=188.252.16.109