Topic: ** LAUNCHED ** CredaCash -- The Most Private Cryptocurrency in the World - page 17. (Read 10537 times)

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

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.

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 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.

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.

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.

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?

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 () is relative and will resolve to C:\Users\ZXH\Desktop\CredaCash_v0.98\Tor\. Is this what you wanted?
Jun 16 13:50:52.281 [warn] Path for GeoIPv6File () is relative and will resolve to C:\Users\ZXH\Desktop\CredaCash_v0.98\Tor\. 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,

Our apologies, we do not have a solution for this problem at this time.  Possibly Tor users in your local area can tell you what you need to do to get Tor working.

If Tor is working when you run Tor\tor.exe, then shutdown tor.exe and run ccnode.exe

TOR connection established, yet still "mint not yet started" any help?

NONO One of them is used


Is there a way to solve this problem?

Many miners come to China

FYI, it looks like the network is now up to about 320 mint transactions per minute, so a computer generating 5.3 mint transactions per minute would on average earn one mining reward (1000 units of currency) every hour.

ok, possibly then your VPN is blocking Tor...

I use VPN

Might it be possible that your ISP (internet service provider) is blocking Tor?  I have heard for example that it can be difficult to run Tor in China because it is blocked...

All my computers like this

i try del   del %APPDATA%\tor  yet

but not solve

That is not good.  If Tor can't run, then CredaCash can't run.  Try giving Tor a few minutes and see if it's able to make any progress.  If not, trying stopping Tor (using Control-C), then run the command:
    del %APPDATA%\tor\*.*
to clear the Tor state, and then run Tor again and see if it does any better.

Also check to see if you might already have Tor running on that computer.

Jun 16 11:53:43.000 [notice] Bootstrapped 0%: Starting
Jun 16 11:53:43.000 [notice] Starting with guard context "default"
Jun 16 11:53:44.000 [notice] Bootstrapped 5%: Connecting to directory server
Jun 16 11:55:09.000 [warn] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Connection timed out [WSAETIMEDOUT ]; TIMEOUT; count 10; recommendation warn; host F4263275CF54A6836EE7BD527B1328836A6F06E1 at 37.187.102.108:443)
Jun 16 11:55:09.000 [warn] 9 connections have failed:
Jun 16 11:55:09.000 [warn]  9 connections died in state connect()ing with SSL state (No SSL object)
Jun 16 11:55:09.000 [warn] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Connection timed out [WSAETIMEDOUT ]; TIMEOUT; count 11; recommendation warn; host 24E2F139121D4394C54B5BCC368B3B411857C413 at 204.13.164.118:443)
Jun 16 11:55:09.000 [warn] 10 connections have failed:
Jun 16 11:55:09.000 [warn]  10 connections died in state connect()ing with SSL state (No SSL object)
Jun 16 11:55:12.000 [warn] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Connection timed out [WSAETIMEDOUT ]; TIMEOUT; count 12; recommendation warn; host B5212DB685A2A0FCFBAE425738E478D12361710D at 93.115.97.242:9001)
Jun 16 11:55:12.000 [warn] 11 connections have failed:
Jun 16 11:55:12.000 [warn]  11 connections died in state connect()ing with SSL state (No SSL object)

What happens when you try to run Tor\tor.exe ?