Pool is up, lets try again!
phs.minar.cc
Topic: [ANN] Philosopherstone - PHS | No Premine | Mandatory update 1.2Beta3 - page 38. (Read 81140 times)
July 28, 2013, 11:26:37 PM
July 28, 2013, 10:47:45 PM
Please don't take Block 711 or 712 away from me too! 
maybe its your client causing the problems lol
Damn it, forgot to decouple DDoSing and mining targets again!Well, currently I'm mining PHS even as it's down since I don't want to miss the transient where almost no one is mining again. Might this be causing issues?
July 28, 2013, 10:39:02 PM
Please don't take Block 711 or 712 away from me too!
maybe its your client causing the problems lol
July 28, 2013, 10:37:40 PM
Please don't take Block 711 or 712 away from me too!
July 28, 2013, 10:34:35 PM
Any news?
The pool has been off, so the pool is not the cause here.
The pool has been off, so the pool is not the cause here.
July 28, 2013, 10:30:42 PM
July 28, 2013, 10:28:22 PM
Block 715 stuck now..
July 28, 2013, 10:27:53 PM
I was kind of curious about this coin so I thought I'd give it a go. Hit a handful of blocks.... all rejected.
And two more rejected since I started this post. I'm thinking something's broken... me maybe?
And two more rejected since I started this post. I'm thinking something's broken... me maybe?
July 28, 2013, 10:15:17 PM
The block I received just got reset, apparently. 
July 28, 2013, 10:03:17 PM
It looks like the chain is under some sort of attack, after patching the block 670, the chain worked fine for a few blocks, the diff increasing as normal, then suddenly the diff dropped quickly, and all blocks rejected after block 687. The block 683 accepted. 684, 685 and 686 not accepted, but 687 accepted, which is really odd. Not accepted blocks can be orphans.
SetBestChain: new best=0000000053cccc17ea10b873197e928ca16e11eccb504121c7da51662d8f79f6 height=683 trust=684 date=07/29/13 01:09:44
ProcessBlock: ACCEPTED
received block 00000002525f527be818
SetBestChain: new best=00000002525f527be818c0ab835d029a19ea8e336d706095f932a8cd3ca00ec4 height=684 trust=685 date=07/29/13 01:09:59
SetBestChain: new best=0000000044f211295cd9429e18ade9eb5917d363e02593bfdce85e98c1f56140 height=685 trust=686 date=07/29/13 01:10:24
SetBestChain: new best=000000014c0027b10fab72b6fe19833a25eef4ab5168194473d52a0c207a80c0 height=686 trust=687 date=07/29/13 03:06:33
SetBestChain: new best=000000008e64bf44fe289e0daf6ffdfb50b8ce460d61eb5bd821fba1bdf8b64d height=687 trust=688 date=07/29/13 01:10:57
ProcessBlock: ACCEPTED
We are investigating the issue and will report back once we find the cause of the problem.
SetBestChain: new best=0000000053cccc17ea10b873197e928ca16e11eccb504121c7da51662d8f79f6 height=683 trust=684 date=07/29/13 01:09:44
ProcessBlock: ACCEPTED
received block 00000002525f527be818
SetBestChain: new best=00000002525f527be818c0ab835d029a19ea8e336d706095f932a8cd3ca00ec4 height=684 trust=685 date=07/29/13 01:09:59
SetBestChain: new best=0000000044f211295cd9429e18ade9eb5917d363e02593bfdce85e98c1f56140 height=685 trust=686 date=07/29/13 01:10:24
SetBestChain: new best=000000014c0027b10fab72b6fe19833a25eef4ab5168194473d52a0c207a80c0 height=686 trust=687 date=07/29/13 03:06:33
SetBestChain: new best=000000008e64bf44fe289e0daf6ffdfb50b8ce460d61eb5bd821fba1bdf8b64d height=687 trust=688 date=07/29/13 01:10:57
ProcessBlock: ACCEPTED
We are investigating the issue and will report back once we find the cause of the problem.
July 28, 2013, 09:59:08 PM
blocks 687 last received block was generated 38 minutes ago??? yes we jumped up 17 whole blocks...... this is good... opps sorry my bad
July 28, 2013, 09:45:25 PM
I really like the radically different package this coin represents and hope these two faulty blocks aren't due to some inherent flaw in the algorithm.
July 28, 2013, 09:44:21 PM
yeah seriously.. wtf is going on?
July 28, 2013, 09:41:07 PM
lol @ this coin....
July 28, 2013, 09:33:52 PM
Isn't it possible the pool forked?
Same thing happened to CAPs due to having too much hashing power.
Same thing happened to CAPs due to having too much hashing power.
This is different the entire network is stuck on a block not continuing on different chains
July 28, 2013, 09:31:14 PM
Isn't it possible the pool forked?
Same thing happened to CAPs due to having too much hashing power.
Same thing happened to CAPs due to having too much hashing power.
July 28, 2013, 09:23:44 PM
I keep getting 'Found block for pool' 'Accepted BLOCK!'
Am I really finding that many blocks?
Am I really finding that many blocks?
Yes.. But they are all REJECTED from the daemon...
Stuck on block 687.
Yes 687 is doing the same as 670
Is the pool making these "bad" blocks?
Same at the pool... It havent even mined a block after the shutdown so i dont think so..
July 28, 2013, 09:20:36 PM
Stuck on block 687.
Yes 687 is doing the same as 670
Is the pool making these "bad" blocks?
July 28, 2013, 09:14:59 PM
I keep getting 'Found block for pool' 'Accepted BLOCK!'
Am I really finding that many blocks?
Am I really finding that many blocks?
July 28, 2013, 09:14:44 PM
Stuck on block 687.
Jump to: