Topic: [ANN] Cachecoin |CACH| POW+POS | NO PREMINE | NO ICO | CRYPTOPIA | - page 45. (Read 81319 times)
June 14, 2017, 11:05:34 AM
the solutions from cach.digger.work are too fast or in other words too light. it is not so good if the hashing power is centralidzed. Large miners could operate as solo miner, it's better for the Network.
June 14, 2017, 11:02:45 AM
Ok. We will check it!
http://cerberus.ageleis.de page 3
Rollback to block 173757
173757 0345e68d277cedf670d27dd3644f25488ff42c5d5d2e0a31cf5adb1a60ce6270 1 0.62657000 Wed, 14 Jun 2017 13:25:12 GMT
173824 67eb01fbd936670e23895fadf8cf21a7764cb0bce6a077543d4890ee8aa6cfb4 1 94.81000000 Wed, 14 Jun 2017 14:09:09 GMT
173823 0ce8814d39258080ac30dcdf15931157a73ade0be4b81e8a6f8368902c783051 1 94.85000000 Wed, 14 Jun 2017 14:03:38 GMT
June 14, 2017, 10:55:55 AM
Ok. We will check it!
June 14, 2017, 10:54:58 AM
What I see that P2Pool is working without any troubles!
173803 Burovik 06/14/2017 15:44:19 0.0003 95.5200 2,862 11,761 410.94
173802 Plastilin 06/14/2017 15:32:35 0.0003 95.5600 2,860 1,142 39.93
173801 thedivine 06/14/2017 15:31:29 0.0003 95.6000 2,853 1,342 47.04
173800 anonymous 06/14/2017 15:30:11 0.0003 95.6400 2,845 3,710 130.40
173799 ms8787 06/14/2017 15:26:32 0.0003 95.6900 2,838 307 10.82
2-3 hours after the explorer displayed 173824, cach.digger.word behind. Then there was a rollback to 173766 in the explorer.
The problem was.
June 14, 2017, 10:50:55 AM
What I see that P2Pool is working without any troubles!
June 14, 2017, 10:48:42 AM
I could expect the problem by the pool, but any case I will check with the developer.
CACH.DIGGER.WORK - Next Network Block 173,771 (Current: 173,770)
CACH.DIGGER.WORK - Next Network Block 173,771 (Current: 173,770)
June 14, 2017, 10:46:29 AM
No fork - the new blocks are coming now - 173766
Most probably I made a mistake by writing a block number from explorer - 173824
Most probably I made a mistake by writing a block number from explorer - 173824
cach.digger.work shows 173803
No, you were not mistaken, I also saw that block in the explorer. Then there was a rollback.
June 14, 2017, 10:44:07 AM
No fork - the new blocks are coming now - 173766
Most probably I made a mistake by writing a block number from explorer - 173824
Most probably I made a mistake by writing a block number from explorer - 173824
June 14, 2017, 10:42:17 AM
We will check it. Maybe it's a fork.
June 14, 2017, 10:35:15 AM
I have passed this info to the owner of pool.
The network doesn't have any problem as soon as block explorer shows last block 173824!
The network doesn't have any problem as soon as block explorer shows last block 173824!
http://Http://cerberus.ageleis.de/ shows 173763.
June 14, 2017, 10:32:03 AM
Alternatively you could mine in P2Pool - IKARUS
Your pool reports on block 173766. Splitting the network?
June 14, 2017, 10:28:47 AM
Alternatively you could mine in P2Pool - IKARUS
June 14, 2017, 10:22:51 AM
I have passed this info to the owner of pool.
The network doesn't have any problem as soon as block explorer shows last block 173824!
The network doesn't have any problem as soon as block explorer shows last block 173824!
June 14, 2017, 10:08:27 AM
The blockchain on the pool "cach.digger.work" was stuck on block 173803.
"Unable to connect to wallet RPC service: RPC call failed: Failed to connect to 192.168.1.100 port 20300: Connection refused"
"Unable to connect to wallet RPC service: RPC call failed: Failed to connect to 192.168.1.100 port 20300: Connection refused"
June 14, 2017, 09:26:00 AM
What do you mean?
Since today the developer is working on modification of POW algo (1st point of Roadmap) and planning to load updates to his github by the end of week!
Since today the developer is working on modification of POW algo (1st point of Roadmap) and planning to load updates to his github by the end of week!
That's good to hear
June 14, 2017, 08:30:15 AM
What do you mean?
Since today the developer is working on modification of POW algo (1st point of Roadmap) and planning to load updates to his github by the end of week!
Since today the developer is working on modification of POW algo (1st point of Roadmap) and planning to load updates to his github by the end of week!
June 14, 2017, 08:17:12 AM
so any updates on what's happening?
June 14, 2017, 05:40:07 AM
5% fees...
hm...
and low pool hashrate
and there is no obligation to use the pool if the fees to high for you. June 14, 2017, 05:31:06 AM
That is condition of the owner! I only could say that it's stable enough and haven't went down.
June 14, 2017, 05:21:09 AM
5% fees...
hm...
and low pool hashrate
Jump to: