CredaCash *** FIRST PRIVACY COIN with INTEGRATED P2P CROSSCHAIN EXCHANGE ***

[qq386437050]

Jun 16 13:50:52.205 [notice] Tor 0.3.5.8 (git-5030edfb534245ed) running on Windows 8 [or later] with Libevent 2.1.8-stable, OpenSSL 1.0.2q, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
Jun 16 13:50:52.211 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jun 16 13:50:52.277 [notice] Configuration file "C:\Users\ZXH\AppData\Roaming\tor\torrc" not present, using reasonable defaults.
Jun 16 13:50:52.281 [warn] Path for GeoIPFile (<default>) is relative and will resolve to C:\Users\ZXH\Desktop\CredaCash_v0.98\Tor\<default>. Is this what you wanted?
Jun 16 13:50:52.281 [warn] Path for GeoIPv6File (<default>) is relative and will resolve to C:\Users\ZXH\Desktop\CredaCash_v0.98\Tor\<default>. Is this what you wanted?
Jun 16 13:50:52.372 [notice] Opening Socks listener on 127.0.0.1:9050
Jun 16 13:50:52.374 [notice] Opened Socks listener on 127.0.0.1:9050
Jun 16 13:50:52.000 [notice] Bootstrapped 0%: Starting
Jun 16 13:50:53.000 [notice] Starting with guard context "default"
Jun 16 13:50:54.000 [notice] Bootstrapped 10%: Finishing handshake with directory server
Jun 16 13:50:54.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Jun 16 13:50:56.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Jun 16 13:50:58.000 [notice] Bootstrapped 100%: Done

It looks like Tor.exe has a normal connection, but ccnode.exe object refuses

[2019-06-16 13:52:35.160530] [0x00003780] [info] torproxy Connect failed error system: 10061 could not be connected due to the active rejection of the target computer.

[2019-06-16 13:52:38.226667] [0x00002c48] [info] Blocksync BlockSyncClient:: Connect Outgoing Call GetHostName ()

[2019-06-16 13:52:39.280958] [0x00002c48] [info] torproxy Connect failed error system: 10061 could not be connected due to the active rejection of the target computer.

[2019-06-16 13:52:39.317702] [0x00002c48] [info] Blocksync BlockSyncClient:: Connect Outgoing No Blockchain servers found

[2019-06-16 13:52:43.133653] [0x000022f0] [info] Relay Relay Service:: Connect Outgoing Call GetHostName ()

[2019-06-16 13:52:43.347168] [0x00002c48] [info] Blocksync BlockSyncClient:: Connect Outgoing Call GetHostName ()

[2019-06-16 13:52:44.167881] [0x000022f0] [info] torproxy Connect failed error system: 10061 could not be connected due to the active rejection of the target computer.

[2019-06-16 13:52:44.244680] [0x000022f0] [info] Relay Relay Service:: Connect Outgoing No relay peers found

[2019-06-16 13:52:44.819137] [0x00003008] [info] Tor started

[2019-06-16 13:52:45.241007] [0x00003008] [error] Tor process exited unexpectedly -- restart will be attempted in 10 seconds...

[2019-06-16 13:52:45.253973] [0x00002c48] [info] torproxy Connect failed error system: 10061 because the target computer actively refused,

[CredaCash]

Jun 16 13:50:52.205 [notice] Tor 0.3.5.8 (git-5030edfb534245ed) running on Windows 8 [or later] with Libevent 2.1.8-stable, OpenSSL 1.0.2q, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.
Jun 16 13:50:52.211 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jun 16 13:50:52.277 [notice] Configuration file "C:\Users\ZXH\AppData\Roaming\tor\torrc" not present, using reasonable defaults.
Jun 16 13:50:52.281 [warn] Path for GeoIPFile (<default>) is relative and will resolve to C:\Users\ZXH\Desktop\CredaCash_v0.98\Tor\<default>. Is this what you wanted?
Jun 16 13:50:52.281 [warn] Path for GeoIPv6File (<default>) is relative and will resolve to C:\Users\ZXH\Desktop\CredaCash_v0.98\Tor\<default>. Is this what you wanted?
Jun 16 13:50:52.372 [notice] Opening Socks listener on 127.0.0.1:9050
Jun 16 13:50:52.374 [notice] Opened Socks listener on 127.0.0.1:9050
Jun 16 13:50:52.000 [notice] Bootstrapped 0%: Starting
Jun 16 13:50:53.000 [notice] Starting with guard context "default"
Jun 16 13:50:54.000 [notice] Bootstrapped 10%: Finishing handshake with directory server
Jun 16 13:50:54.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Jun 16 13:50:56.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Jun 16 13:50:58.000 [notice] Bootstrapped 100%: Done

It looks like Tor.exe has a normal connection, but ccnode.exe object refuses

[2019-06-16 13:52:35.160530] [0x00003780] [info] torproxy Connect failed error system: 10061 could not be connected due to the active rejection of the target computer.

[2019-06-16 13:52:38.226667] [0x00002c48] [info] Blocksync BlockSyncClient:: Connect Outgoing Call GetHostName ()

[2019-06-16 13:52:39.280958] [0x00002c48] [info] torproxy Connect failed error system: 10061 could not be connected due to the active rejection of the target computer.

[2019-06-16 13:52:39.317702] [0x00002c48] [info] Blocksync BlockSyncClient:: Connect Outgoing No Blockchain servers found

[2019-06-16 13:52:43.133653] [0x000022f0] [info] Relay Relay Service:: Connect Outgoing Call GetHostName ()

[2019-06-16 13:52:43.347168] [0x00002c48] [info] Blocksync BlockSyncClient:: Connect Outgoing Call GetHostName ()

[2019-06-16 13:52:44.167881] [0x000022f0] [info] torproxy Connect failed error system: 10061 could not be connected due to the active rejection of the target computer.

[2019-06-16 13:52:44.244680] [0x000022f0] [info] Relay Relay Service:: Connect Outgoing No relay peers found

[2019-06-16 13:52:44.819137] [0x00003008] [info] Tor started

[2019-06-16 13:52:45.241007] [0x00003008] [error] Tor process exited unexpectedly -- restart will be attempted in 10 seconds...

[2019-06-16 13:52:45.253973] [0x00002c48] [info] torproxy Connect failed error system: 10061 because the target computer actively refused,

This would be the expected log output if it was generated prior to the start of mining (the log timestamps use your local time zone, not GMT).

In any event, could you try stopping ccnode (using Control-C), wait for it to fully stop, then wait a few seconds more, then restart it?  Then check the log output again if it is still unable to connect?

[CredaCash]

An update on CredaCash mining.

Since the start of mining, approximately 2 million units of currency have been rewarded to miners.  There are 198 million units remaining to be rewarded.

The block rate has been running close to one block every 20 seconds.  At that rate, the first stage of mining will finish around August 1.

Over the past two hours, an average of just over 1000 mint transactions have been submitted to the network every minute.  That means if your computer is generating 11.2 mint transactions per minute, then you should be earning on average two mining rewards (2000 units of currency) every hour.

[CredaCash]

How do I check my wallet address?
Can multiple absentees use the same wallet file copied from the past?

In CredaCash, you have to generate a new destination for each counterparty.  This is done using the command getnewaddress.  Your counterparty can then send one or more transactions to that destination using the command sendtoaddress -- HOWEVER, the live blockchain will not accept sendtoaddress transactions while the initial mining is in progress.  You will have to wait until August to send mined currency on the live blockchain.  (This was done as a precaution, to keep things as simple as possible so there would be less chance of problems.)

Each wallet does have a single master secret that is used to generate new destinations.  The hash of the master secret is reported by the getwalletinfo command, as the hdmasterkeyid value.  If a destination was generated by your wallet, the command validateaddress will also tell you the hash of the master secret used to generate the destination.

You can copy the wallet data file (the *.ccw file) to another computer, however, you should not continue using it on the old computer.  If you did that, you should not lose any funds, but you might see some anomalous behavior, such as: (a) the wallet attempts to send a transaction, only to discover the funds were already spent; (b) the wallet generates a new destination, only to discover that destination has already been generated and used somewhere else; and (c) the two wallets only see incoming payments sent to destinations that wallet generated, not to destinations generated by the other wallet.  In any event, this has not been thoroughly tested, so use it at your own risk.  The better procedure is to create separate wallets on each computer, and send funds between them when needed.

[CredaCash]

CredaCash mining update:

Since the start of mining, approximately 3 million units of currency have been rewarded to miners.  There are 197 million units remaining to be rewarded.

The block rate has been around one block every 17 to 18 seconds.  At that rate, the first stage of mining will finish around July 25-28.

Over the past hour, an average of just over 1090 mint transactions have been submitted to the network every minute.  That means if your computer is generating 10.4 mint transactions per minute, then you should be earning on average two mining rewards (2000 units of currency) every hour.

[SagIchMaSo]

I am running the minigprogramm since a while and get this errors

[2019-06-16 21:40:52.767159] [0x00002458] [info]    Tx-service Conn 146 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 170 expected 171
[2019-06-16 21:40:58.267314] [0x00001a24] [info]    Tx-service Conn 149 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1148 expected 1149
[2019-06-16 21:40:59.111096] [0x00001a24] [info]    Tx-service Conn 150 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1683 expected 1684
[2019-06-16 21:40:59.173588] [0x00002458] [info]    Tx-service Conn 152 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 2089 expected 2090
[2019-06-16 21:40:59.236088] [0x00001a24] [info]    Tx-service Conn 150 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1688 expected 1689
[2019-06-16 21:40:59.782985] [0x000026b4] [info]    Tx-service Conn 149 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1163 expected 1164
[2019-06-16 21:41:00.126739] [0x00002458] [info]    Tx-service Conn 152 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 2101 expected 2102
[2019-06-16 21:41:00.267376] [0x0000254c] [info]    Tx-service Conn 152 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 2106 expected 2107
[2019-06-16 21:41:01.329918] [0x00002458] [info]    Tx-service Conn 152 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 2120 expected 2121
[2019-06-16 21:41:01.454914] [0x00001a24] [info]    Tx-service Conn 146 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 181 expected 182
[2019-06-16 21:41:01.814310] [0x000026b4] [info]    Tx-service Conn 149 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1178 expected 1179
[2019-06-16 21:41:02.079956] [0x0000254c] [info]    Tx-service Conn 149 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1183 expected 1184

Balance is still at 0...

is there someting i am doing wrong?

Windows 64bit node and wallet

[CredaCash]

I am running the minigprogramm since a while and get this errors

[2019-06-16 21:40:52.767159] [0x00002458] [info]    Tx-service Conn 146 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 170 expected 171
[2019-06-16 21:40:58.267314] [0x00001a24] [info]    Tx-service Conn 149 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1148 expected 1149
[2019-06-16 21:40:59.111096] [0x00001a24] [info]    Tx-service Conn 150 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1683 expected 1684
[2019-06-16 21:40:59.173588] [0x00002458] [info]    Tx-service Conn 152 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 2089 expected 2090
[2019-06-16 21:40:59.236088] [0x00001a24] [info]    Tx-service Conn 150 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1688 expected 1689
[2019-06-16 21:40:59.782985] [0x000026b4] [info]    Tx-service Conn 149 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1163 expected 1164
[2019-06-16 21:41:00.126739] [0x00002458] [info]    Tx-service Conn 152 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 2101 expected 2102
[2019-06-16 21:41:00.267376] [0x0000254c] [info]    Tx-service Conn 152 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 2106 expected 2107
[2019-06-16 21:41:01.329918] [0x00002458] [info]    Tx-service Conn 152 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 2120 expected 2121
[2019-06-16 21:41:01.454914] [0x00001a24] [info]    Tx-service Conn 146 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 181 expected 182
[2019-06-16 21:41:01.814310] [0x000026b4] [info]    Tx-service Conn 149 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1178 expected 1179
[2019-06-16 21:41:02.079956] [0x0000254c] [info]    Tx-service Conn 149 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1183 expected 1184

Balance is still at 0...

is there someting i am doing wrong?

Windows 64bit node and wallet

Something is not going right.  Could you try stopping the wallet (using the command "stop"), wait for it to exit, then restart it and inside the wallet, try the command "cc.mint threads 1".  This will launch only a single thread of mining.  Does the wallet then report that mint transactions are being successfully submitted?  If so, try upping the number of threads ("cc.mint threads 2", "cc.mint threads 4", etc) and see if that is what is making it fail at some point...  This could also be caused by load on your machine from running other programs at the same time, or from prolonged memory paging due to lack of RAM or overuse of RAM.  They key thing though is if the wallet reports that transactions are successfully submitted.

[SagIchMaSo]

Looks a bit different with on thread, but still with errors


[2019-06-16 22:04:55.994130] [0x000026b4] [info]    Tx-service Conn 146 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 2464 expected 2465
[2019-06-16 22:05:02.150592] [0x00002070] [info]    ProcessBlock received valid block level 3208 witness 0 skip 0 size  452 oid 23 27 82 73 f9 16 6a e5 65 dc 93 c2 ae f9 ac b2 prior a6 a6 b9 0b f6 6e bb b6 df 0c 49 56 5d f1 ed c0
[2019-06-16 22:05:02.150592] [0x00002070] [info]    BlockChain::SetNewlyIndelibleBlock announced 4386291 level 3208 witness 0 size 452 oid 23 27 82 73 f9 16 6a e5 65 dc 93 c2 ae f9 ac b2 prior oid a6 a6 b9 0b f6 6e bb b6 df 0c 49 56 5d f1 ed c0
[2019-06-16 22:05:10.120089] [0x000026b4] [info]    Tx-service Conn 151 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 4780 expected 4781
[2019-06-16 22:05:19.152710] [0x00002070] [info]    ProcessBlock received valid block level 3209 witness 0 skip 0 size  452 oid 33 58 ea c6 36 28 2d 18 19 a6 dd ed 1d 42 a6 a4 prior 23 27 82 73 f9 16 6a e5 65 dc 93 c2 ae f9 ac b2
[2019-06-16 22:05:19.152710] [0x00002070] [info]    BlockChain::SetNewlyIndelibleBlock announced 4403126 level 3209 witness 0 size 452 oid 33 58 ea c6 36 28 2d 18 19 a6 dd ed 1d 42 a6 a4 prior oid 23 27 82 73 f9 16 6a e5 65 dc 93 c2 ae f9 ac b2
[2019-06-16 22:05:25.872466] [0x000020c0] [info]    Tx-service Conn 152 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 4759 expected 4760
[2019-06-16 22:05:38.874346] [0x00002070] [info]    ProcessBlock received valid block level 3210 witness 0 skip 0 size  452 oid 6d 2c cb 51 eb 17 12 9e 57 7d 27 c2 ae 74 4d f5 prior 33 58 ea c6 36 28 2d 18 19 a6 dd ed 1d 42 a6 a4
[2019-06-16 22:05:38.874346] [0x00002070] [info]    BlockChain::SetNewlyIndelibleBlock announced 4422995 level 3210 witness 0 size 452 oid 6d 2c cb 51 eb 17 12 9e 57 7d 27 c2 ae 74 4d f5 prior oid 33 58 ea c6 36 28 2d 18 19 a6 dd ed 1d 42 a6 a4

[CredaCash]

Looks a bit different with on thread, but still with errors


[2019-06-16 22:04:55.994130] [0x000026b4] [info]    Tx-service Conn 146 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 2464 expected 2465
[2019-06-16 22:05:02.150592] [0x00002070] [info]    ProcessBlock received valid block level 3208 witness 0 skip 0 size  452 oid 23 27 82 73 f9 16 6a e5 65 dc 93 c2 ae f9 ac b2 prior a6 a6 b9 0b f6 6e bb b6 df 0c 49 56 5d f1 ed c0
[2019-06-16 22:05:02.150592] [0x00002070] [info]    BlockChain::SetNewlyIndelibleBlock announced 4386291 level 3208 witness 0 size 452 oid 23 27 82 73 f9 16 6a e5 65 dc 93 c2 ae f9 ac b2 prior oid a6 a6 b9 0b f6 6e bb b6 df 0c 49 56 5d f1 ed c0
[2019-06-16 22:05:10.120089] [0x000026b4] [info]    Tx-service Conn 151 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 4780 expected 4781
[2019-06-16 22:05:19.152710] [0x00002070] [info]    ProcessBlock received valid block level 3209 witness 0 skip 0 size  452 oid 33 58 ea c6 36 28 2d 18 19 a6 dd ed 1d 42 a6 a4 prior 23 27 82 73 f9 16 6a e5 65 dc 93 c2 ae f9 ac b2
[2019-06-16 22:05:19.152710] [0x00002070] [info]    BlockChain::SetNewlyIndelibleBlock announced 4403126 level 3209 witness 0 size 452 oid 33 58 ea c6 36 28 2d 18 19 a6 dd ed 1d 42 a6 a4 prior oid 23 27 82 73 f9 16 6a e5 65 dc 93 c2 ae f9 ac b2
[2019-06-16 22:05:25.872466] [0x000020c0] [info]    Tx-service Conn 152 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 4759 expected 4760
[2019-06-16 22:05:38.874346] [0x00002070] [info]    ProcessBlock received valid block level 3210 witness 0 skip 0 size  452 oid 6d 2c cb 51 eb 17 12 9e 57 7d 27 c2 ae 74 4d f5 prior 33 58 ea c6 36 28 2d 18 19 a6 dd ed 1d 42 a6 a4
[2019-06-16 22:05:38.874346] [0x00002070] [info]    BlockChain::SetNewlyIndelibleBlock announced 4422995 level 3210 witness 0 size 452 oid 6d 2c cb 51 eb 17 12 9e 57 7d 27 c2 ae 74 4d f5 prior oid 33 58 ea c6 36 28 2d 18 19 a6 dd ed 1d 42 a6 a4

Could you also try restarting ccnode (Control-C, wait for it to stop, wait a few more seconds, then run it again).  You can leave the wallet running while you do that, although it might report server errors until ccnode is running again.

[SagIchMaSo]

No still the same after restart..

[2019-06-16 22:24:21.289715] [0x00001da4] [info]    Tx-service Conn 151 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1122 expected 1123
[2019-06-16 22:24:35.649695] [0x000016cc] [info]    Tx-service Conn 151 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1157 expected 1158
[2019-06-16 22:24:36.071594] [0x00002248] [info]    ProcessBlock received valid block level 3275 witness 0 skip 0 size  452 oid 03 7b 01 ec 6c 08 9c d9 e1 f9 3c bc a8 17 60 18 prior 4f 2d df cf 80 e0 ce 2a 8a 0f 01 08 ed ed c1 80
[2019-06-16 22:24:36.071594] [0x00002248] [info]    BlockChain::SetNewlyIndelibleBlock announced 5560192 level 3275 witness 0 size 452 oid 03 7b 01 ec 6c 08 9c d9 e1 f9 3c bc a8 17 60 18 prior oid 4f 2d df cf 80 e0 ce 2a 8a 0f 01 08 ed ed c1 80
[2019-06-16 22:24:52.384773] [0x00002798] [info]    Tx-service Conn 151 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1190 expected 1191
[2019-06-16 22:24:57.103727] [0x00002248] [info]    ProcessBlock received valid block level 3276 witness 0 skip 0 size  452 oid 82 4f de a1 23 4d cf 07 f3 f1 78 ec 42 36 fd 10 prior 03 7b 01 ec 6c 08 9c d9 e1 f9 3c bc a8 17 60 18
[2019-06-16 22:24:57.103727] [0x00002248] [info]    BlockChain::SetNewlyIndelibleBlock announced 5581203 level 3276 witness 0 size 452 oid 82 4f de a1 23 4d cf 07 f3 f1 78 ec 42 36 fd 10 prior oid 03 7b 01 ec 6c 08 9c d9 e1 f9 3c bc a8 17 60 18
[2019-06-16 22:25:07.041644] [0x000016cc] [info]    Tx-service Conn 149 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 837 expected 838
[2019-06-16 22:25:16.323286] [0x00002248] [info]    ProcessBlock received valid block level 3277 witness 0 skip 0 size  452 oid d9 bf 4a 05 98 45 54 cb 2f 64 a7 57 19 b9 37 6b prior 82 4f de a1 23 4d cf 07 f3 f1 78 ec 42 36 fd 10
[2019-06-16 22:25:16.323286] [0x00002248] [info]    BlockChain::SetNewlyIndelibleBlock announced 5600352 level 3277 witness 0 size 452 oid d9 bf 4a 05 98 45 54 cb 2f 64 a7 57 19 b9 37 6b prior oid 82 4f de a1 23 4d cf 07 f3 f1 78 ec 42 36 fd 10

[CredaCash]

No still the same after restart..

[2019-06-16 22:24:21.289715] [0x00001da4] [info]    Tx-service Conn 151 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1122 expected 1123
[2019-06-16 22:24:35.649695] [0x000016cc] [info]    Tx-service Conn 151 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1157 expected 1158
[2019-06-16 22:24:36.071594] [0x00002248] [info]    ProcessBlock received valid block level 3275 witness 0 skip 0 size  452 oid 03 7b 01 ec 6c 08 9c d9 e1 f9 3c bc a8 17 60 18 prior 4f 2d df cf 80 e0 ce 2a 8a 0f 01 08 ed ed c1 80
[2019-06-16 22:24:36.071594] [0x00002248] [info]    BlockChain::SetNewlyIndelibleBlock announced 5560192 level 3275 witness 0 size 452 oid 03 7b 01 ec 6c 08 9c d9 e1 f9 3c bc a8 17 60 18 prior oid 4f 2d df cf 80 e0 ce 2a 8a 0f 01 08 ed ed c1 80
[2019-06-16 22:24:52.384773] [0x00002798] [info]    Tx-service Conn 151 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1190 expected 1191
[2019-06-16 22:24:57.103727] [0x00002248] [info]    ProcessBlock received valid block level 3276 witness 0 skip 0 size  452 oid 82 4f de a1 23 4d cf 07 f3 f1 78 ec 42 36 fd 10 prior 03 7b 01 ec 6c 08 9c d9 e1 f9 3c bc a8 17 60 18
[2019-06-16 22:24:57.103727] [0x00002248] [info]    BlockChain::SetNewlyIndelibleBlock announced 5581203 level 3276 witness 0 size 452 oid 82 4f de a1 23 4d cf 07 f3 f1 78 ec 42 36 fd 10 prior oid 03 7b 01 ec 6c 08 9c d9 e1 f9 3c bc a8 17 60 18
[2019-06-16 22:25:07.041644] [0x000016cc] [info]    Tx-service Conn 149 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 837 expected 838
[2019-06-16 22:25:16.323286] [0x00002248] [info]    ProcessBlock received valid block level 3277 witness 0 skip 0 size  452 oid d9 bf 4a 05 98 45 54 cb 2f 64 a7 57 19 b9 37 6b prior 82 4f de a1 23 4d cf 07 f3 f1 78 ec 42 36 fd 10
[2019-06-16 22:25:16.323286] [0x00002248] [info]    BlockChain::SetNewlyIndelibleBlock announced 5600352 level 3277 witness 0 size 452 oid d9 bf 4a 05 98 45 54 cb 2f 64 a7 57 19 b9 37 6b prior oid 82 4f de a1 23 4d cf 07 f3 f1 78 ec 42 36 fd 10

Ok, thanks. What is displayed by the wallet?  Does it say tx successfully submitted, or something else?

[SagIchMaSo]

No still the same after restart..

[2019-06-16 22:24:21.289715] [0x00001da4] [info]    Tx-service Conn 151 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1122 expected 1123
[2019-06-16 22:24:35.649695] [0x000016cc] [info]    Tx-service Conn 151 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1157 expected 1158
[2019-06-16 22:24:36.071594] [0x00002248] [info]    ProcessBlock received valid block level 3275 witness 0 skip 0 size  452 oid 03 7b 01 ec 6c 08 9c d9 e1 f9 3c bc a8 17 60 18 prior 4f 2d df cf 80 e0 ce 2a 8a 0f 01 08 ed ed c1 80
[2019-06-16 22:24:36.071594] [0x00002248] [info]    BlockChain::SetNewlyIndelibleBlock announced 5560192 level 3275 witness 0 size 452 oid 03 7b 01 ec 6c 08 9c d9 e1 f9 3c bc a8 17 60 18 prior oid 4f 2d df cf 80 e0 ce 2a 8a 0f 01 08 ed ed c1 80
[2019-06-16 22:24:52.384773] [0x00002798] [info]    Tx-service Conn 151 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1190 expected 1191
[2019-06-16 22:24:57.103727] [0x00002248] [info]    ProcessBlock received valid block level 3276 witness 0 skip 0 size  452 oid 82 4f de a1 23 4d cf 07 f3 f1 78 ec 42 36 fd 10 prior 03 7b 01 ec 6c 08 9c d9 e1 f9 3c bc a8 17 60 18
[2019-06-16 22:24:57.103727] [0x00002248] [info]    BlockChain::SetNewlyIndelibleBlock announced 5581203 level 3276 witness 0 size 452 oid 82 4f de a1 23 4d cf 07 f3 f1 78 ec 42 36 fd 10 prior oid 03 7b 01 ec 6c 08 9c d9 e1 f9 3c bc a8 17 60 18
[2019-06-16 22:25:07.041644] [0x000016cc] [info]    Tx-service Conn 149 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 837 expected 838
[2019-06-16 22:25:16.323286] [0x00002248] [info]    ProcessBlock received valid block level 3277 witness 0 skip 0 size  452 oid d9 bf 4a 05 98 45 54 cb 2f 64 a7 57 19 b9 37 6b prior 82 4f de a1 23 4d cf 07 f3 f1 78 ec 42 36 fd 10
[2019-06-16 22:25:16.323286] [0x00002248] [info]    BlockChain::SetNewlyIndelibleBlock announced 5600352 level 3277 witness 0 size 452 oid d9 bf 4a 05 98 45 54 cb 2f 64 a7 57 19 b9 37 6b prior oid 82 4f de a1 23 4d cf 07 f3 f1 78 ec 42 36 fd 10

Ok, thanks. What is displayed by the wallet?  Does it say tx successfully submitted, or something else?

Yes, that looks good.

cc.mint thread 1, tx submitted, elapsed time 15 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 16 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 16 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 16 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 16 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 16 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 15 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 16 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 14 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 17 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 14 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 15 seconds, wallet balance 0

[CredaCash]

No still the same after restart..

[2019-06-16 22:24:21.289715] [0x00001da4] [info]    Tx-service Conn 151 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1122 expected 1123
[2019-06-16 22:24:35.649695] [0x000016cc] [info]    Tx-service Conn 151 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1157 expected 1158
[2019-06-16 22:24:36.071594] [0x00002248] [info]    ProcessBlock received valid block level 3275 witness 0 skip 0 size  452 oid 03 7b 01 ec 6c 08 9c d9 e1 f9 3c bc a8 17 60 18 prior 4f 2d df cf 80 e0 ce 2a 8a 0f 01 08 ed ed c1 80
[2019-06-16 22:24:36.071594] [0x00002248] [info]    BlockChain::SetNewlyIndelibleBlock announced 5560192 level 3275 witness 0 size 452 oid 03 7b 01 ec 6c 08 9c d9 e1 f9 3c bc a8 17 60 18 prior oid 4f 2d df cf 80 e0 ce 2a 8a 0f 01 08 ed ed c1 80
[2019-06-16 22:24:52.384773] [0x00002798] [info]    Tx-service Conn 151 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1190 expected 1191
[2019-06-16 22:24:57.103727] [0x00002248] [info]    ProcessBlock received valid block level 3276 witness 0 skip 0 size  452 oid 82 4f de a1 23 4d cf 07 f3 f1 78 ec 42 36 fd 10 prior 03 7b 01 ec 6c 08 9c d9 e1 f9 3c bc a8 17 60 18
[2019-06-16 22:24:57.103727] [0x00002248] [info]    BlockChain::SetNewlyIndelibleBlock announced 5581203 level 3276 witness 0 size 452 oid 82 4f de a1 23 4d cf 07 f3 f1 78 ec 42 36 fd 10 prior oid 03 7b 01 ec 6c 08 9c d9 e1 f9 3c bc a8 17 60 18
[2019-06-16 22:25:07.041644] [0x000016cc] [info]    Tx-service Conn 149 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 837 expected 838
[2019-06-16 22:25:16.323286] [0x00002248] [info]    ProcessBlock received valid block level 3277 witness 0 skip 0 size  452 oid d9 bf 4a 05 98 45 54 cb 2f 64 a7 57 19 b9 37 6b prior 82 4f de a1 23 4d cf 07 f3 f1 78 ec 42 36 fd 10
[2019-06-16 22:25:16.323286] [0x00002248] [info]    BlockChain::SetNewlyIndelibleBlock announced 5600352 level 3277 witness 0 size 452 oid d9 bf 4a 05 98 45 54 cb 2f 64 a7 57 19 b9 37 6b prior oid 82 4f de a1 23 4d cf 07 f3 f1 78 ec 42 36 fd 10

Ok, thanks. What is displayed by the wallet?  Does it say tx successfully submitted, or something else?

Yes, that looks good.

cc.mint thread 1, tx submitted, elapsed time 15 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 16 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 16 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 16 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 16 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 16 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 15 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 16 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 14 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 17 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 14 seconds, wallet balance 0
cc.mint thread 1, tx submitted, elapsed time 15 seconds, wallet balance 0

It looks like the mint transactions from your wallet are probably getting through to the network since your log file reports that ccnode is receiving new blocks. You could try kicking the number of threads back up to its full value ("cc.mint start"), let it run for two hours, and see if the wallet balance changes.  When running with full threads, how many threads are running, and what is the average elapsed time per thread?

(PS, we will also take a closer look at that HandleValidationTimeout message, and see what might be causing it or if it might be a misleading warning message.)

[SagIchMaSo]

The block annoucement is shown every 15/20 sec, i let him run with full threads for a wihle and will see what happends  

elapsed time 50 seconds +/- a bit, full with 16 threads

[CredaCash]

The block annoucement is shown every 15/20 sec, i let him run with full threads for a wihle and will see what happends  

elapsed time 50 seconds +/- a bit, full with 16 threads

ok, that's an average of 19 mint transactions per minute from your wallet, while the total network rate is currently about 1150 mint transactions per minute, and the block rate is running about one block per 17 seconds.  Based on those figures, you should get an average of 7 mint rewards (7000 units of currency) every two hours.  That is just an average though--like flipping a coin 100 times, it is possible to get more or less than the expected number of 50 heads or tails...

[CredaCash]

CredaCash mining update:

Since the start of mining, 4 million units of currency have been rewarded to miners.  There are 196 million units remaining to be rewarded.

Over the past hour, an average of just over 1175 mint transactions have been submitted to the network every minute, and one block has been produced every 17 seconds.  That means if your computer can generate 11 mint transactions per minute, you would earn on average two mining rewards (2000 units of currency) every hour.

[CredaCash]

[2019-06-16 22:24:21.289715] [0x00001da4] [info]    Tx-service Conn 151 TransactConnection::HandleValidationTimeout ignoring late or unexpected callback id 1122 expected 1123

Our apologies--it turns out this was just a misleading warning.  If the trace level had been set to debug ("--trace=5") or higher, then the log would show that that validation successfully finishes and the result "OK" is sent to the wallet before the "HandleValidationTimeout ignoring late or unexpected callback" message is logged.  In the next release, we will update the code to not log the HandleValidationTimeout message in that situation.

Thank you for the report and our apologies for the confusion.

[CredaCash]

CredaCash mining update:

Since the start of mining, 6.5 million units of currency have been rewarded to miners.  There are 193.5 million units remaining to be rewarded.

Over the past hour, an average of just over 1800 mint transactions have been submitted to the network every minute, and one block has been produced every 16.9 seconds.  That means if your computer can generate 17 mint transactions per minute, you would earn on average two mining rewards (2000 units of currency) every hour.

[CredaCash]

CredaCash mining update:

Since the start of mining, 7 million units of currency have been rewarded to miners.  There are 193 million units remaining to be rewarded.

Over the past hour, an average of just over 1900 mint transactions have been submitted to the network every minute, and one block has been produced every 17 seconds.  That means if your computer can generate 18 mint transactions per minute, you would earn on average two mining rewards (2000 units of currency) every hour.

[rovait]

do you have a block explorer?
what about GUI wallet?