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

[MemberCount+1]

@jjiimm_64

I think the Dev can do nothing. I suppose your adress is CNiYj371ed9MmS2bKMfsNnLVGb4Cx5NQpk but You have too few peers. My nodes have 20-50 connections! If you publish a new block your message have to do more than one hop in the network and this take 5-10min in a worst case szenario. You should running your node with more peers (24/7 and open port 2225)

A larger network with a better distribution solves the Problem. A good start is to open port 2225 in your Firewall or router. Other nodes can add your node faster because they do not have to wait for an outgoing random port/connections.

The guy with the bigger Impact of the network but maybe a slow computer (but with better connection as you) is CYBMEP41xHmUDopMdvMEbQQ5abu8GzbgVb.

[1713878500]

1713878500

[1713878500]

1713878500

[1713878500]

1713878500

[1713878500]

1713878500

[1713878500]

1713878500

[jjiimm_64]

@jjiimm_64

I think the Dev can do nothing. I suppose your adress is CNiYj371ed9MmS2bKMfsNnLVGb4Cx5NQpk but You have too few peers. My nodes have 20-50 connections! If you publish a new block your message have to do more than one hop in the network and this take 5-10min in a worst case szenario. You should running your node with more peers (24/7 and open port 2225)

A larger network with a better distribution solves the Problem. A good start is to open port 2225 in your Firewall or router. Other nodes can add your node faster because they do not have to wait for an outgoing random port/connections.

Thank you sir..

added port.   please if anyone can also post node list to manually addnode I would appreciate it.

Jim

[MemberCount+1]

you can use this,
https://www.coinexchange.io/network/peers/CACH

but you see the most of all nodes have a random outgoing Connection and therefore we can not simple add this IPs. The best Szenario is a static IP with open port for incoming and outgoing Connection (for mining and stake) but not all users have this requirements.

you can add nodes also on a running wallet with "addnode IP" or  "addnode IP:Port" in the daemon with "cachecoind addnode AAA.BBB.CCC.DDD" or in the GUI->Help->Debug Window->Console  .. return if true if added or false, no connection

[jjiimm_64]

you can use this,
https://www.coinexchange.io/network/peers/CACH

but you see the most of all nodes have a random outgoing Connection and therefore we can not simple add this IPs. The best Szenario is a static IP with open port for incoming and outgoing Connection (for mining and stake) but not all users have this requirements.

you can add nodes also on a running wallet with "addnode IP" or  "addnode IP:Port" in the daemon with "cachecoind addnode AAA.BBB.CCC.DDD" or in the GUI->Help->Debug Window->Console  .. return if true if added or false, no connection

Thank you for that link!!   check out the distribution globally.. very nice.

[CachecoinDev]

Tomorrow you will notice the difficulty and reward begin to adjust based on current network speed. This leads into the java port, the new wallet will have a gui for network statistics with live streaming data. This is just one feature that is being worked on, including simplified access to common features everyone uses on websites will become available inside the wallet.

The java port has been under construction for about 2 years, so to those wondering if the timeline is very long....not really, kalgecin has been working on this for a long time and is about 2/3 completed. This week he began restructuring the chain to be in a sqlite db.

Currently, to receive transactions, you have to configure the wallet to do some mumbo jumbo to process an incoming tx. With the way we are structuring it you can just query the db.

[jjiimm_64]

Currently, to receive transactions, you have to configure the wallet to do some mumbo jumbo to process an incoming tx. With the way we are structuring it you can just query the db.

wait.. ?what?  

So the version that we are using today, which works with incoming transactions...  and your plan is to replace it with one that we have to 'mumbo jumbo' or query the db?

1.  defined mumbo jumbo
2.  define query the db...    do you mean use the rpc as in 'listtransactions' ?  or the console...  


is this actually ready to be released?  or is this just on testnet.?  


edit:  jftr, comments like the quoted do NOT inspire confidence in a coins prospects for the future.  not professional.

[CachecoinDev]

So a sense of humor is never used when working on a project.

[aleksoo7]

The logo of Cachecoin replaced by the new style!

[jjiimm_64]

So a sense of humor is never used when working on a project.

Sorry, I did/do not get the reference... what part is real and what part is a joke?

[aleksoo7]

[MemberCount+1]

I check the pool and see that the block from the miner software not accepted but the walletsoftware generated coins. we should mining local or we need special mining Software?

Code:

06/24/17 00:20:49 ERROR: CheckProofOfWork() : hash doesn't match nBits
06/24/17 00:20:49 ERROR: CheckBlock() : proof of work failed
06/24/17 00:20:49 ERROR: ProcessBlock() : CheckBlock FAILED

[CachecoinDev]

24th has arrived, new protocol is in process. 62.88 (and will adjust often) is the current block reward, 309k h/s is the current network speed. Difficulty is slowly increasing, it appears to be working as intended.

If you are receiving errors, update the wallet.

Mining software will need editing, the classical ones won't function.

[MemberCount+1]

ah ok, but wallet software is the new one

Code:

06/23/17 08:52:16 CACHeCoin version V5.3-42-g30a2321-kal (2017-06-18 19:25:29 +0300)
06/23/17 08:52:16 Using OpenSSL version OpenSSL 1.1.0f 25 May 2017
06/23/17 08:52:16 Default data directory /home/.cachecoin
06/23/17 08:52:16 Used data directory /home/.cachecoin
06/23/17 08:52:16 dbenv.open LogDir=/homr/.cachecoin/database ErrorFile=/home/.cachecoin/db.log
06/23/17 08:52:16 Final lk_max_locks is 537000, sufficient for (worst case) 11 blocks in a single transaction (up to a 5-deep reorganization)
06/23/17 08:52:16 Bound to [::]:2225
06/23/17 08:52:16 Bound to 0.0.0.0:2225

we need new mining software to use the pool. I will see what I can do.

[jjiimm_64]

We this tested on testnet??  what blocknumber did the 'switch' start at?  


My wallet is now in an error state

here is the log when it crashed.   with:  EnvShutdown exception: Invalid argument (22)

Code:

ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
received getdata for: block 00000294ded7a635178e
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 398ms
received getdata for: block 00000294ded7a635178e
received block 0000029849e064a14e07
SetBestChain: new best=0000029849e064a14e07  height=177138  trust=285870772753869  date=06/24/17 00:55:11
ProcessBlock: ACCEPTED
received getdata for: block 0000029849e064a14e07
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
received getdata for: block 0000029849e064a14e07
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
received getdata for: block 0000005a09e2f2e422fa
Flushing wallet.dat
Flushed wallet.dat 380ms
received getdata for: block 00000210835c11ed49b9
CPUMiner : proof-of-stake block found b0524e52507cfde8710b16385800a8c0d32a652cf3c4a6921086b1bb46dbfc42
BitcoinMiner:
new block found
  hash: b0524e52507cfde8710b16385800a8c0d32a652cf3c4a6921086b1bb46dbfc42
target: 000000013d380000000000000000000000000000000000000000000000000000
CBlock(hash=b0524e52507cfde8710b, ver=3, hashPrevBlock=0000029849e064a14e07, hashMerkleRoot=431d2561e2, nTime=1498265745, nBits=1d013d38, nNonce=0, vtx=2, vchBlockSig=3046022100f6712e4f8fc3cac61e39ab542dae91d8f4613deb74183eb73b1f3701d51ce5bc022100b73e193fc25436c613da6225b3fdeac027aa73553d9152c6ebe9b5057bf7c56f)
  Coinbase(hash=49346a1ec6, nTime=1498265745, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, 4294967295), coinbase 03f3b302013c062f503253482f)
    CTxOut(empty)
  Coinstake(hash=910fcdde7d, nTime=1498265745, ver=1, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(76eaf38bff, 1), scriptSig=30440220379974a6fd891d84)
    CTxOut(empty)
    CTxOut(nValue=54.333215, scriptPubKey=030a8de03e1e1326122dc13710dbd16a198389873128fe0db43a465c1a7b06b88e OP_CHECKSIG)
  vMerkleTree: 49346a1ec6 910fcdde7d 431d2561e2
generated 0.00
AddToWallet 910fcdde7d  new
WalletUpdateSpent found spent coin 50.371326cach 76eaf38bff5131b62bc7442165a46ef7f10c833c2b94d0e2610276b6b2e9e368
NotifyTransactionChanged 76eaf38bff5131b62bc7442165a46ef7f10c833c2b94d0e2610276b6b2e9e368 status=1
NotifyTransactionChanged 910fcdde7d54e7209336c6b069eb6c435a07ed61ab63d1988cab0de00740b876 status=0
updateWallet 76eaf38bff5131b62bc7442165a46ef7f10c833c2b94d0e2610276b6b2e9e368 1
   inWallet=1 inModel=1 Index=1100-1101 showTransaction=1 derivedStatus=1
updateWallet 910fcdde7d54e7209336c6b069eb6c435a07ed61ab63d1988cab0de00740b876 0
   inWallet=1 inModel=0 Index=1351-1351 showTransaction=1 derivedStatus=0
SetBestChain: new best=b0524e52507cfde8710b  height=177139  trust=285874238852981  date=06/24/17 00:55:45
ProcessBlock: ACCEPTED
received getdata for: block b0524e52507cfde8710b
EnvShutdown exception: Invalid argument (22)

[jjiimm_64]

Looks like the explorer is also in an error state:

[MemberCount+1]

jup Explorer down atm, try a restart/resync

[jjiimm_64]

jup Explorer down atm, try a restart/resync

resync?? I was told NO fork


received block d7aa22df3f2ac86f5e05
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
Misbehaving: 5.3.240.233:57948 (0 -> 50)
trying connection 123.27.34.122:2225 lastseen=252.3hrs
received block b2f396b6ec096e6d2f5e
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED

Code:

send version message: version 90001, blocks=177124, us=71.224.11.214:2225, them=95.129.166.161:51381, peer=95.129.166.161:51381
Added time data, samples 3, offset +1 (+0 minutes)
Moving 95.129.166.161:2225 to tried
receive version message: version 90000, blocks=177651, us=71.224.11.214:2225, them=95.129.166.161:2225, peer=95.129.166.161:51381
connection timeout
trying connection 23.236.53.118 lastseen=0.0hrs
connection timeout
trying connection 46.133.225.171:2225 lastseen=62.1hrs
Added time data, samples 4, offset +6 (+0 minutes)
receive version message: version 90000, blocks=177651, us=71.224.11.214:53609, them=95.37.144.216:2225, peer=95.37.144.216:2225
connection timeout
trying connection 23.236.53.118 lastseen=0.0hrs
connection timeout
trying connection 175.152.145.196:2225 lastseen=109.4hrs
accepted connection [2001:0:9d38:6ab8:28af:12ac:af0b:d580]:49976
send version message: version 90001, blocks=177124, us=71.224.11.214:2225, them=[2001:0:9d38:6ab8:28af:12ac:af0b:d580]:49976, peer=[2001:0:9d38:6ab8:28af:12ac:af0b:d580]:49976
Added time data, samples 5, offset +5 (+0 minutes)
nTimeOffset = +1  (+0 minutes)
receive version message: version 90000, blocks=177651, us=[2001:0:9d38:90d7:63:1ee2:b81f:f429]:2225, them=80.244.42.127:2225, peer=[2001:0:9d38:6ab8:28af:12ac:af0b:d580]:49976
connection timeout
trying connection 23.236.53.118 lastseen=0.0hrs
connection timeout
[b]received block d7aa22df3f2ac86f5e05
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
Misbehaving: 5.3.240.233:57948 (0 -> 50)
trying connection 123.27.34.122:2225 lastseen=252.3hrs
received block b2f396b6ec096e6d2f5e
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED[/b]
Misbehaving: 5.3.240.233:57948 (50 -> 100) DISCONNECTING
disconnecting node 5.3.240.233:57948
connection timeout
trying connection 23.236.53.118 lastseen=0.0hrs
connection timeout
trying connection 194.242.14.206:2225 lastseen=1.1hrs
connected 194.242.14.206:2225
send version message: version 90001, blocks=177124, us=71.224.11.214:2225, them=194.242.14.206:2225, peer=194.242.14.206:2225

[aleksoo7]

an issue with the last patch has been noticed and fix has been pushed
https://github.com/kalgecin/CACHeCoin/releases/tag/V5.4.1

[MemberCount+1]

jup Explorer down atm, try a restart/resync

resync?? I was told NO fork

because blkindex.dat was destroyed or something like that 

[jjiimm_64]

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