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

[Palmdetroit]

just for 8332? like this?
https://github.com/palmd/philosopherstone/commit/00b856b38be0af3b3142ef599f5eac9551a9a79f

You can place it on any 9000+ block, but 8332 will be enough.

ok 1.2 is fully synced to block 11610, but should i changed the checkpoint to the new one??

11637*

[1713483614]

1713483614

[1713483614]

1713483614

[1713483614]

1713483614

[1713483614]

1713483614

[Palmdetroit]

WTF?

Reorganize happened, there is another fork and this chain has a higher weight.

OK, remove this checkpoint and wait until syncronization will be completed.

ok its fully synced add checkpoint with the new blockhash for 8332?

[Balthazar]

WTF?

Reorganize happened, there is another fork and this chain has a higher weight.

OK, remove this checkpoint and wait until syncronization will be completed.

ok its fully synced add checkpoint with the new blockhash for 8332?

Let's wait for another reports... If there will be another user with the same results, then we will be allowed to set a checkpoint on any block of this chain. Maybe closer to 10000-11000.

[Palmdetroit]

WTF?

Reorganize happened, there is another fork and this chain has a higher weight.

OK, remove this checkpoint and wait until syncronization will be completed.

ok its fully synced add checkpoint with the new blockhash for 8332?

Let's wait for another reports... If there will be another user with the same results, then we will be allowed to set a checkpoint on any block of this chain. Maybe closer to 10000-11000.

{
"blocks" : 11637,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 4.67342365,
"networkhashps" : 186069077,
"pooledtx" : 0,
"testnet" : false
}

[Palmdetroit]

WTF?

Reorganize happened, there is another fork and this chain has a higher weight.

OK, remove this checkpoint and wait until syncronization will be completed.

ok its fully synced add checkpoint with the new blockhash for 8332?

Let's wait for another reports... If there will be another user with the same results, then we will be allowed to set a checkpoint on any block of this chain. Maybe closer to 10000-11000.

*crickets*

[Balthazar]

It's better to publish builds now, to allow other users try this out.

But it's only a part of issue, the final build should contain syncronized checkpointing enabled. Because it's required to prevent chain accidental forks on initial stages.

Official maintainer should generate a key pair and set his public key in checkpoints.cpp file. When this will be completed he should run own instance with private -checkpointkey=privatekey_here option.

[monocolor]

yes please publish it, my 1.2 (existing) client sync's at 8347 only...

[monocolor]

Looks like there base code may not be as mature as Litecoin...

Elacoin and many another examples can prove that you are wrong. Shitty code could be done using any codebase.

maybe you are right, but recent pow/pos coins have a lot problems, not only this one. As a comparison, pow only coins have much less problems and mostly stable. Maybe the dev of these coins all screwed on something...

[Palmdetroit]

It's better to publish builds now, to allow other users try this out.

http://rapidshare.com/files/1990813362/philosopherstone-qt.zip

Modified 1.2 for windows

https://github.com/palmd/philosopherstone/commits/master

should have all dll's

USE at OWN risk DYODD.. worked for me from a empty directory but takes time

report back

[Palmdetroit]

Newest working version with new checkpoint:
https://github.com/palmd/philosopherstone

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

[Palmdetroit]

WTF?

Reorganize happened, there is another fork and this chain has a higher weight.

OK, remove this checkpoint and wait until syncronization will be completed.

ok its fully synced add checkpoint with the new blockhash for 8332?

Let's wait for another reports... If there will be another user with the same results, then we will be allowed to set a checkpoint on any block of this chain. Maybe closer to 10000-11000.

{
"blocks" : 11637,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 4.67342365,
"networkhashps" : 186069077,
"pooledtx" : 0,
"testnet" : false
}

{
"blocks" : 11640,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 4.67342365,
"networkhashps" : 179670610,
"pooledtx" : 1,
"testnet" : false
}

[Balthazar]

maybe you are right, but recent pow/pos coins have a lot problems, not only this one.

This means nothing. I can jump from the rooftop, and then say that it's a problem of building design, but that would be a false.

As a comparison, pow only coins have much less problems and mostly stable.

Just because the most copy&paste developers already made this errors in the past. They know what they allowed or disallowed to do with the PoW design. But it doesn't mean that the PoW design is matured enough or hybrid design isn't matured enough.

[monocolor]

maybe you are right, but recent pow/pos coins have a lot problems, not only this one.

This means nothing. I can jump from the rooftop, and then say that it's a problem of building design, but that would be a false.

As a comparison, pow only coins have much less problems and mostly stable.

Just because the most copy&paste developers already made this errors in the past. They know what they allowed or disallowed to do with the PoW design. But it doesn't mean that the PoW design is matured enough or hybrid design isn't matured enough.

lol, pow/pos are copy-paste too, tho john claimed changed something, I guess it's small things.

[monocolor]

yes please publish it, my 1.2 (existing) client sync's at 8347 only...

Code:

http://rapidshare.com/files/1990813362/philosopherstone-qt.zip

grab it and join the *maybe* the main chain

the client stuck at block 3500, with a lot errors in the log:

ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input

[Palmdetroit]

Hows the chain coming mono, or anyone else out there who has this ver?

[Palmdetroit]

yes please publish it, my 1.2 (existing) client sync's at 8347 only...

Code:

http://rapidshare.com/files/1990813362/philosopherstone-qt.zip

grab it and join the *maybe* the main chain

the client stuck at block 3500, with a lot errors in the log:

ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input

I think I had a wallet,peers and .conf file and nothing else when I ran it

[monocolor]

Hows the chain coming mono, or anyone else out there who has this ver?

I restarted the client, it seems sync'ing. Now seems stuck at block 9540. but my previous 1000 some coins are gone! I am pretty sure it is not the original chain, do you have the check points in the code?

[Palmdetroit]

Hows the chain coming mono, or anyone else out there who has this ver?

I restarted the client, it seems sync'ing. Now seems stuck at block 9540. but my previous 1000 some coins are gone! I am pretty sure it is not the original chain, do you have the check points in the code?

no checkpoints in that no, it should jump backwards again, did for me

(no checkpoints form me, has orig devs 1.2 checkpoints)

[Balthazar]

lol, pow/pos are copy-paste too, tho john claimed changed something, I guess it's small things.

Anyone could "change a small things" in the linux kernel, and then say that UNIX design isn't matured enough. It's ridiculous and there is nothing to argue about.

This incidents with the recently coins has absolutely no connection with the basic design, it's just a qualification related bugs. You can dispute this, but it wouldn't change the reality. So, I propose to end the conversation on this topic.

Hows the chain coming mono, or anyone else out there who has this ver?

Trying this now.

// I hate rapidshare

[Palmdetroit]

Good i put another on vps to see what happens

on other server going strong straight to 9k and going fast, this was with no default directory