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

[A L I E N]

We are at block #8306 @ 16:30 GMT.

Anyone else have the same as this?

[1713280474]

1713280474

[bholzer]

We are at block #8306 @ 16:30 GMT.

Anyone else have the same as this?

Nobody I've talked to, man. I think we're in trouble.

[A L I E N]

Well there is about 22mh/s mining away (not me) on the chain I am synced to:

{
"blocks" : 8317,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.69654359,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 22328388,
"pooledtx" : 0,
"testnet" : false
}

[SoulSlayerPT]

We are at block #8306 @ 16:30 GMT.

Anyone else have the same as this?

Nop.. Block 6083 and i lost like 5000 phs.. Dam.. I must be in another chain i think!

[Molitor]

Philosopherstone version v1.2.0.0 ($Format:%cD)
Using OpenSSL version OpenSSL 1.0.1e 11 Feb 2013
Startup time: 08/09/13 17:07:25
Default data directory C:\xxxxxxxx
Used data directory C:\xxxxxxxx
dbenv.open LogDir=C:\xxxxxxxx
Loading block index...
LoadBlockIndex(): hashBestChain=000000006fc3794409f7  height=6084  trust=6085  date=08/06/13 06:02:36
LoadBlockIndex(): synchronized checkpoint 00000000241ef810f9c2c8294b6b911f747173218f5fc8166385a92f434bc0b4
Verifying last 2500 blocks at level 1
 block index            9422ms
Loading wallet...
nFileVersion = 70200
 wallet                  515ms
Rescanning last 6084 blocks (from block 0)...
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CBlock::ReadFromDisk() : errors in block header
 rescan                 4150ms
Loading addresses...
Loaded 0 addresses from peers.dat  0ms
RandAddSeed() 201396 bytes
mapBlockIndex.size() = 6256
nBestHeight = 6084

That's the rescan log, with errors, FWIW.

I can't get past 6084 now, no matter what I do. Watching the rescanning log file, it grows by about one of these every minute:

ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 55cd698198132e35593d8e4fab08d37a9254d9218ead2c88a61139aa6bac2ccc, hashProof=0000000000000000000000000000000000000000000000000000000000000000
WARNING: ProcessBlock(): check proof-of-stake failed for block 86630e17580cea7694ce1d46ea241e82d8a49d17da054a6178cacd2510252670


At this rate, I fear it'll take many, many hours to process, and even then I don't know what I'll have at the end.

[Palmdetroit]

Philosopherstone version v1.2.0.0 ($Format:%cD)
Using OpenSSL version OpenSSL 1.0.1e 11 Feb 2013
Startup time: 08/09/13 17:07:25
Default data directory C:\xxxxxxxx
Used data directory C:\xxxxxxxx
dbenv.open LogDir=C:\xxxxxxxx
Loading block index...
LoadBlockIndex(): hashBestChain=000000006fc3794409f7  height=6084  trust=6085  date=08/06/13 06:02:36
LoadBlockIndex(): synchronized checkpoint 00000000241ef810f9c2c8294b6b911f747173218f5fc8166385a92f434bc0b4
Verifying last 2500 blocks at level 1
 block index            9422ms
Loading wallet...
nFileVersion = 70200
 wallet                  515ms
Rescanning last 6084 blocks (from block 0)...
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CBlock::ReadFromDisk() : errors in block header
 rescan                 4150ms
Loading addresses...
Loaded 0 addresses from peers.dat  0ms
RandAddSeed() 201396 bytes
mapBlockIndex.size() = 6256
nBestHeight = 6084

That's the rescan log, with errors, FWIW.

I can't get past 6084 now, no matter what I do. Watching the rescanning log file, it grows by about one of these every minute:

ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 55cd698198132e35593d8e4fab08d37a9254d9218ead2c88a61139aa6bac2ccc, hashProof=0000000000000000000000000000000000000000000000000000000000000000
WARNING: ProcessBlock(): check proof-of-stake failed for block 86630e17580cea7694ce1d46ea241e82d8a49d17da054a6178cacd2510252670


At this rate, I fear it'll take many, many hours to process, and even then I don't know what I'll have at the end.

Welp I think my client is current on some fork and I get tons of:

INFO: check kernel failed on coinstake

 and

WARNING: ProcessBlock(): check proof-of-stake failed for block

or

stake reward exceeded

anyone knows what this means lol.. def no stakes showing up

[Molitor]

Well there is about 22mh/s mining away (not me) on the chain I am synced to:

{
"blocks" : 8317,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.69654359,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 22328388,
"pooledtx" : 0,
"testnet" : false
}

{
"blocks" : 6084,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.89145117,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 71130719,
"pooledtx" : 0,
"testnet" : false
}


Seems like a lot of people mining.

[Palmdetroit]

Well there is about 22mh/s mining away (not me) on the chain I am synced to:

{
"blocks" : 8317,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.69654359,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 22328388,
"pooledtx" : 0,
"testnet" : false
}

{
"blocks" : 6084,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.89145117,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 71130719,
"pooledtx" : 0,
"testnet" : false
}


Seems like a lot of people mining.


{
"blocks" : 8326,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.46482350,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 14614946,
"pooledtx" : 0,
"testnet" : false
}


wish we could visualize all the many forks

[trid]

Well there is about 22mh/s mining away (not me) on the chain I am synced to:

{
"blocks" : 8317,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.69654359,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 22328388,
"pooledtx" : 0,
"testnet" : false
}


{
"blocks" : 8353,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.65313587,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 22566445,
"pooledtx" : 0,
"testnet" : false
}

[A L I E N]

{
"blocks" : 8353,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.65313587,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 22566445,
"pooledtx" : 0,
"testnet" : false
}

We are on the same chain, and I think Palmdetroit is too:

{
"blocks" : 8356,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.65313587,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 22918277,
"pooledtx" : 0,
"testnet" : false
}

[Molitor]

Are all the ~6084 people on Windows, and the ~8300 people on Linux?

I'm on Windows and still stuck at ~6048.

[trid]

Are all the ~6084 people on Windows, and the ~8300 people on Linux?

I'm on Windows and still stuck at ~6048.

no, i'm on windows



{
"blocks" : 8382,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.03878709,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 36605140,
"pooledtx" : 0,
"testnet" : false
}

[bholzer]

Are all the ~6084 people on Windows, and the ~8300 people on Linux?

I'm on Windows and still stuck at ~6048.

The network speed is almost 4 times higher on the ~6100ish fork (75 MH/s) vs the ~8300ish fork (22 MH/s)

This has gone on too long now - the dev has essentially been a no-show and I'm not sure we can recover from this. A bummer since it was about to be added to Cryptsy. If things were more established we might have been okay but the response has been unacceptable.

[datguyian]

{
"version" : "v1.2.0.0",
"protocolversion" : 60006,
"walletversion" : 60000,
"balance" : 1459.46561600,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 7193,
"moneysupply" : 736723.35759200,
"connections" : 3,
"proxy" : "",
"difficulty" : 3.51030749,
"testnet" : false,
}

Weird... everyone else is stuck at either 6xxx or 8xxx, I'm at 7193.

[Molitor]

Are all the ~6084 people on Windows, and the ~8300 people on Linux?

I'm on Windows and still stuck at ~6048.

The network speed is almost 4 times higher on the ~6100ish fork (75 MH/s) vs the ~8300ish fork (22 MH/s)

This has gone on too long now - the dev has essentially been a no-show and I'm not sure we can recover from this. A bummer since it was about to be added to Cryptsy. If things were more established we might have been okay but the response has been unacceptable.

Agreed.

Maybe someone's messing with blockchain on purpose?

The only thing it cost me is a few minutes of annoyance -- I'm more curious as to what went wrong than worried about losing anything -- but I feel bad for you losing real money.

[A L I E N]

I am on Windows too and on the same chain as Trid (which I believe is correct).  We are synced and network hash is increasing.

{
"blocks" : 8390,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.16889024,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 41726100,
"pooledtx" : 0,
"testnet" : false
}


I think the nethash you guys are seeing at 6100 is the historical quote, ie the networkhash was ~71mh/s on that block when it was made but no one is mining at that block currently (I don't think you could, but not 100% sure).

Has anyone tried to create a new wallet.dat and connect direct to a node?  If that was able to sync, then you could dump your private keys and import them into the working wallet.

[Molitor]

I am on Windows too and on the same chain as Trid (which I believe is correct).  We are synced and network hash is increasing.

{
"blocks" : 8390,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.16889024,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 41726100,
"pooledtx" : 0,
"testnet" : false
}


I think the nethash you guys are seeing at 6100 is the historical quote, ie the networkhash was ~71mh/s on that block when it was made but no one is mining at that block currently (I don't think you could, but not 100% sure).

Has anyone tried to create a new wallet.dat and connect direct to a node?  If that was able to sync, then you could dump your private keys and import them into the working wallet.

I redownloaded 1.2; got rid of everything except the .conf which contained only the single line "connect=188.252.16.109" and with one connection, it goes fine until it hits 6084; est. total blocks 4193. Then the log chokes slowly with those ERROR: CheckProofOfStake() things. It's consuming 0% CPU, so it's not doing much. Also, the greenbar disappears, but I never get the green checkmark, and it still says (out of sync).

Plus, I've mined on the 6084 fork and got some blocks, about 10x faster than I should, which obviously means this is the correct fork.

Gonna reredownload 1.2 from another source, maybe one is corrupted.

EDIT: Reredownload hits 6084 with est total blocks 4199. Maybe it's ... AMD CPUs on ~6084?

[Lasergun]

So I can note that in v.1.2 stake reward was reduced (b4 was much more than 3.5% monthly).

[digeros]

I am on Windows too and on the same chain as Trid (which I believe is correct).  We are synced and network hash is increasing.

{
"blocks" : 8390,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.16889024,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 41726100,
"pooledtx" : 0,
"testnet" : false
}


I think the nethash you guys are seeing at 6100 is the historical quote, ie the networkhash was ~71mh/s on that block when it was made but no one is mining at that block currently (I don't think you could, but not 100% sure).

Has anyone tried to create a new wallet.dat and connect direct to a node?  If that was able to sync, then you could dump your private keys and import them into the working wallet.

I redownloaded 1.2; got rid of everything except the .conf which contained only the single line "connect=188.252.16.109" and with one connection, it goes fine until it hits 6084; est. total blocks 4193. Then the log chokes slowly with those ERROR: CheckProofOfStake() things. It's consuming 0% CPU, so it's not doing much. Also, the greenbar disappears, but I never get the green checkmark, and it still says (out of sync).

Plus, I've mined on the 6084 fork and got some blocks, about 10x faster than I should, which obviously means this is the correct fork.

Gonna reredownload 1.2 from another source, maybe one is corrupted.

I wouldn't trust just one connection... use a bunch of nodes then the nodes have to aggree on the blockchain... here are my current connection IP  add to config file

addnode=24.16.169.96
addnode=188.252.16.109
addnode=72.23.76.121
addnode=46.150.89.173
addnode=198.50.233.22
addnode=188.81.161.38
addnode=64.120.17.149
addnode=50.149.211.203
addnode=46.229.50.42
addnode=81.27.169.82
addnode=81.105.30.173
addnode=24.6.21.198
addnode=183.187.168.120
addnode=184.88.62.170

[2Kool4Skewl]

I'm running 1.2 and stuck at block 7373.