[ANN] Cachecoin |CACH| POW+POS | NO PREMINE | NO ICO | CRYPTOPIA |

[aleksoo7]

jup Explorer down atm, try a restart/resync

resync?? I was told NO fork

because blkindex.dat was destroyed or something like that 

Fair enough.. So I had a copy of the chain from yesterday.. and every synced fine until

Code:

ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
received block 000000413930d52b84c7
SetBestChain: new best=000000413930d52b84c7  height=177646  trust=285870772754377  date=06/24/17 06:03:44
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
received block 0000006df406479624c2
SetBestChain: new best=0000006df406479624c2  height=177647  trust=285870772754378  date=06/24/17 06:04:00
SetBestChain: new best=0000001c68b05113cb5e  height=177648  trust=285870772754379  date=06/24/17 06:04:24
SetBestChain: new best=00000038db37739036a4  height=177649  trust=285870772754380  date=06/24/17 06:05:38
SetBestChain: new best=00000039f6da994cfc7c  height=177650  trust=285870772754381  date=06/24/17 06:06:02
ProcessBlock: ACCEPTED

Then checkBlock fails.. I think the chain is forked.

Code:

received block de240e733b720a64d8f9
ERROR: CheckBlock() : bad block signature
ERROR: ProcessBlock() : CheckBlock FAILED
Misbehaving: 5.3.240.233:2225 (0 -> 100) DISCONNECTING

Have you seen the link to the fix updated some minutes ago!
https://github.com/kalgecin/CACHeCoin/releases/tag/V5.4.1

[1714040498]

1714040498

[1714040498]

1714040498

[1714040498]

1714040498

[1714040498]

1714040498

[1714040498]

1714040498

[1714040498]

1714040498

[MemberCount+1]

same issue with the patch

Code:

06/24/17 08:03:02 CACHeCoin version 0.7.5-13-gbadd0fd-kal (2017-06-24 10:20:40 +0300)
06/24/17 08:03:02 Default data directory /root/.cachecoin
06/24/17 08:03:02 Used data directory /root/.cachecoin
06/24/17 08:03:02 dbenv.open LogDir=/root/.cachecoin/database ErrorFile=/root/.cachecoin/db.log
06/24/17 08:03:02 Final lk_max_locks is 537000, sufficient for (worst case) 11 blocks in a single transaction (up to a 5-deep reorganization)
06/24/17 08:03:02 Bound to [::]:2225
06/24/17 08:03:02 Bound to 0.0.0.0:2225
06/24/17 08:03:02 AddLocal(37.120.173.195:2225,6)
06/24/17 08:03:02 Loading block index...
06/24/17 08:03:04 LoadBlockIndex(): hashBestChain=74e6a61750262a7d8a0f  height=177652  trust=285875312599413  date=06/24/17 07:43:01
06/24/17 08:03:04 LoadBlockIndex(): synchronized checkpoint 00000000214828a26dc5a8328f01daf6c0116af8ee9fb7be336485ba4c7a454b
06/24/17 08:03:04 Verifying last 666 blocks at level 1
06/24/17 08:03:04 ERROR: CBlock::ReadFromDisk() : GetHash() doesn't match index
06/24/17 08:03:04 ERROR: LoadBlockIndex() : block.ReadFromDisk failed
06/24/17 08:03:04 CACHeCoin: Error loading blkindex.dat
06/24/17 08:03:04 Flush(false)
06/24/17 08:03:04 blkindex.dat refcount=0
06/24/17 08:03:04 blkindex.dat checkpoint
06/24/17 08:03:04 blkindex.dat closed
06/24/17 08:03:04 DBFlush(false) ended              10ms
06/24/17 08:03:04 StopNode()
06/24/17 08:03:04 Flushed 0 addresses to peers.dat  1ms
06/24/17 08:03:04 Flush(true)
06/24/17 08:03:04 DBFlush(true) ended               0ms
06/24/17 08:03:04 CACHeCoin exited

my 5 nodes are down 

[jjiimm_64]

in my opinion:

time to rollback to a position where the network was running smoothly..  

then properly test the changes on TESTNET.

then, and only then roll out changes to the mainnet.


here is my blockhash's:


getblockhash 177649
00000038db37739036a4d670e840de224ad29355fa582da8330607134d9da83c

getblockhash 177650
00000039f6da994cfc7cce8d852a8ca9990abe0570d1a0c32360c0388b2ca091

getblockhash 177651
19032de520876de87aeaa4acc0ef367f53fbe87ec1a1eb6c3cdd07e7802022cf

[aleksoo7]

Please wait a bit. Kalgecin is fixing it.

[jjiimm_64]

Please wait a bit. Kalgecin is fixing it.

my wallet is reporting synced:


v5.4.0.0-g32a928e-kal



getblockhash 177652
74e6a61750262a7d8a0ffcdba2d0528d3769eb06b64fd6ce71f3a8ecde387c08




received block 74e6a61750262a7d8a0f
SetBestChain: new best=74e6a61750262a7d8a0f  height=177652  trust=285875312599413  date=06/24/17 07:43:01
ProcessBlock: ACCEPTED
received getdata for: block 74e6a61750262a7d8a0f
Flushing wallet.dat

[jjiimm_64]

New block:


getblockhash 177653
64a7f64145fb30a309f4040a0f3b59ecadea8c03c349d7bae8db3f4eed649473

[MemberCount+1]

New block:


getblockhash 177653
64a7f64145fb30a309f4040a0f3b59ecadea8c03c349d7bae8db3f4eed649473

Jop. Do you run the patch-version?

[jjiimm_64]

New block:


getblockhash 177653
64a7f64145fb30a309f4040a0f3b59ecadea8c03c349d7bae8db3f4eed649473

Jop. Do you run the patch-version?

NO.  I am running: v5.4.0.0-g32a928e-kal

The exchange cryptopia is running:  V5.3-42-g30a2321-kal

I suggesting running a KNOWN good version of the code until the devs can prove good code on testnet


edit:

getblockhash 177654
fe0e42f80fb4a24b8fec4e798b229395d1f2fa4d7d94906e471ecea4f6769c72

[MemberCount+1]

I'm run the CACHeCoin version V5.3-42-g30a2321-kal (2017-06-18 19:25:29 +0300) Linux and Windows v5.4.0.0-g32a928e-kal and now sync done

[jjiimm_64]

I'm run the CACHeCoin version V5.3-42-g30a2321-kal (2017-06-18 19:25:29 +0300) Linux and Windows v5.4.0.0-g32a928e-kal and now sync done

getblockhash 177655

e2dcdb35ca18cd6c8eacef65267bffd93ed3c27308c4354e49977f3a50f737ea

[jjiimm_64]

It seams some are still on the wrong chain.

Code:

received block d77283663e89316561c2
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED

I am on the same chain as the exchange..  that is the right chain!!


AFAIK  you cannot change the POW algo without a fork.. but I am not a crypto DEV so I am not sure. (someone else chime in here)


anyone who is a miner right now should be mining solo ... I think the
CACHeCoin version V5.3-42-g30a2321-kal (2017-06-18 19:25:29 +0300) Linux and Windows v5.4.0.0-g32a928e-kal

will still support the scrypt-jane, but I am not sure...  I will start a solo miner and try.


edit:.. i think it is working:  first is solo, second is swith to a pool

Code:

 yacminer version 3.5.0-yac2 - Started: [2017-06-24 05:00:03]
-------------------------------------------------------------------------------
 (5s):66.00 (avg):96.00h/s | A:0  R:0  HW:0  U:0.00/m  WU:0.00/m  FB:0
 ST: 5  SS: 0  NB: 1  LW: 0  GF: 0  RF: 0
 Connected to 127.0.0.1 diff 323 NF 18 without LP as user jimbit
 Block: cd6c8eacef65267b...  Diff:323  Started: [05:00:02]  Best share: 0
-------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0:  69.0C 1039RPM |  32.00/ 32.00h/s | A:0 R:0 HW:0 U:0.00/m T:1 rI: 400
 GPU 1:  75.0C  268RPM |  33.00/ 32.00h/s | A:0 R:0 HW:0 U:0.00/m T:1 rI: 400
 GPU 2:  75.0C 4473RPM |  32.00/ 32.00h/s | A:0 R:0 HW:0 U:0.00/m T:1 rI: 400

-------------------------------------------------------------------------------

 [2017-06-24 05:00:01] Started yacminer 3.5.0-yac2
 [2017-06-24 05:00:01] Loaded configuration file yac.conf
 [2017-06-24 05:00:02] Probing for an alive pool
 [2017-06-24 05:00:02] Network diff set to 323
 [2017-06-24 05:00:02] Block change for http://127.0.0.1:2224 detection via str
tum+tcp://ikarus.ageleis.de:3003 stratum
 [2017-06-24 05:00:03] Pool 2 difficulty changed to 0.100000
 [2017-06-24 05:00:03] GPU 0: selecting lookup gap of 4
 [2017-06-24 05:00:03] GPU 0: selecting buffer_size of 1856
 [2017-06-24 05:00:03] GPU 0: bufsize for thread @ 1856MB based on buffer-size
 [2017-06-24 05:00:03] GPU 1: selecting lookup gap of 4
 [2017-06-24 05:00:03] GPU 1: selecting buffer_size of 1856
 [2017-06-24 05:00:03] GPU 1: bufsize for thread @ 1856MB based on buffer-size
 [2017-06-24 05:00:03] GPU 2: selecting lookup gap of 4
 [2017-06-24 05:00:03] GPU 2: selecting buffer_size of 1856
 [2017-06-24 05:00:03] GPU 2: bufsize for thread @ 1856MB based on buffer-size
 [2017-06-24 05:00:07] Pool 1 slow/down or URL or credentials invalid
 [2017-06-24 05:00:08] API running in IP access mode on port 5028 (44972)




yacminer version 3.5.0-yac2 - Started: [2017-06-24 05:00:03]
-------------------------------------------------------------------------------
(5s):83.00 (avg):98.00h/s | A:0  R:0  HW:0  U:0.00/m  WU:0.00/m  FB:0
ST: 2  SS: 0  NB: 1  LW: 9  GF: 0  RF: 0
Connected to ikarus.ageleis.de diff 0 NF 18 with stratum as user CRQCAzfgX7U1cf
Block: cd6c8eacef65267b...  Diff:323  Started: [05:00:02]  Best share: 0
-------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0:  72.0C 1058RPM |  33.00/ 32.00h/s | A:0 R:0 HW:0 U:0.00/m T:1 rI: 400
GPU 1:  69.0C  725RPM |  34.00/ 34.00h/s | A:0 R:0 HW:0 U:0.00/m T:1 rI: 400
GPU 2:  71.0C 3927RPM |  33.00/ 32.00h/s | A:0 R:0 HW:0 U:0.00/m T:1 rI: 400

-------------------------------------------------------------------------------

[2017-06-24 05:00:01] Started yacminer 3.5.0-yac2
[2017-06-24 05:00:01] Loaded configuration file yac.conf
[2017-06-24 05:00:02] Probing for an alive pool
[2017-06-24 05:00:02] Network diff set to 323
[2017-06-24 05:00:02] Block change for http://127.0.0.1:2224 detection via stra
um+tcp://ikarus.ageleis.de:3003 stratum
[2017-06-24 05:00:03] Pool 2 difficulty changed to 0.100000
[2017-06-24 05:00:03] GPU 0: selecting lookup gap of 4
[2017-06-24 05:00:03] GPU 0: selecting buffer_size of 1856
[2017-06-24 05:00:03] GPU 0: bufsize for thread @ 1856MB based on buffer-size
[2017-06-24 05:00:03] GPU 1: selecting lookup gap of 4
[2017-06-24 05:00:03] GPU 1: selecting buffer_size of 1856
[2017-06-24 05:00:03] GPU 1: bufsize for thread @ 1856MB based on buffer-size
[2017-06-24 05:00:03] GPU 2: selecting lookup gap of 4
[2017-06-24 05:00:03] GPU 2: selecting buffer_size of 1856
[2017-06-24 05:00:03] GPU 2: bufsize for thread @ 1856MB based on buffer-size
[2017-06-24 05:00:07] Pool 1 slow/down or URL or credentials invalid
[2017-06-24 05:00:08] API running in IP access mode on port 5028 (44972)
[2017-06-24 05:03:07] Switching to pool 2 stratum+tcp://ikarus.ageleis.de:3003

[ljp7839008]

good to see it listed on coinXchange.

[jjiimm_64]

Please wait a bit. Kalgecin is fixing it.

@aleksoo7

I am sorry if I have been too pushy about the versions and blockhash's, but the release of new code was not done in a smooth way.


PLEASE  if you going to do a release, and especially introduce a new POW do the following:

• annouce the change (you did this.. sorta  )
• provide details about the changes
• provide details about the new POW
• provide a new miner, or info how to get a miner for the new POW
• organize with the pools the changes upcomming
• thouroghly test the code on testnet
• release when everything is properly ready

[killa-007]

we should get smth like claymore miner, those are very optimized, but he makes them only for big coins, one day though

[humski]

The new logo is applied at the exchange cryptopia https://www.cryptopia.co.nz/Exchange?market=CACH_BTC

[aleksoo7]

The new logo is applied at the exchange cryptopia https://www.cryptopia.co.nz/Exchange?market=CACH_BTC

Very good support on Cryptopia! Only yesterday I have passed them a new logo!

[aleksoo7]

Referring to the bug during implementation of new POW I kindly ask you to revert back your wallets to V5.3
Windows QT Wallet V5.3: Windows V5.3

[rdnkjdi]

Ah when did cache switch to partial PoS?  Is there any good way to follow dev plans / progress?

[aleksoo7]

Please wait a bit. Kalgecin is fixing it.

@aleksoo7

I am sorry if I have been too pushy about the versions and blockhash's, but the release of new code was not done in a smooth way.


PLEASE  if you going to do a release, and especially introduce a new POW do the following:

• annouce the change (you did this.. sorta  )
• provide details about the changes
• provide details about the new POW
• provide a new miner, or info how to get a miner for the new POW
• organize with the pools the changes upcomming
• thouroghly test the code on testnet
• release when everything is properly ready

Everything were tested on the testnet by developer. The problem rised by the old code when it was implemented in the real network. Our developer do the best to rewrite everything to the new Java code to avoid such a troubles anymore.
Please temporary used wallet V5.3.
Windows QT Wallet V5.3:

[MemberCount+1]

that's too much for me now. confused and it's weekend, I'm out today.   I do not work for nothing, sry this is bad. Ikarus paid out all rewards there is not pending blocks and only my reserve amount is in the wallet, but I do not know if everyone has got the rewards in the right wallet/chain.