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

What is the command to query the balance in the wallet address?

CredaCash mining update:

Since the start of mining, close to 10 million units of currency have been rewarded to miners.  There are 190 million units remaining to be rewarded.

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

To get back to this question, CredaCash does not currently have a block explorer, but it is possible to access information about the blockchain from its database.  This gets into the internals of the CredaCash software, which might be of interest to some.

ccnode.exe stores all of its data in an sqlite database.  This database file is located at %LOCALAPPDATA%\CredaCash\CCNode-1\CCdata.db under Windows, and at $HOME/.CredaCash/CCNode-1/CCdata.db under Linux.

To examine this data under Windows, you can download the file sqlite-tools-win32-x86-.zip from https://www.sqlite.org/download.html , extract the contents and then run "sqlite3 %LOCALAPPDATA%\CredaCash\CCNode-1\CCdata.db".  You can do this while ccnode.exe is running or stopped.  The database is in Write Ahead Log (WAL) format, so querying this data will have essentially no effect on ccnode even if it is running, HOWEVER, DO NOT WRITE TO THIS DATABASE.  In other words, you can use commands like .schema and select, but do not use insert, update, alter and other commands that add or change data.

The tables in this database are:

Parameters = various values by Key and Subkey.  The Key values can be found in the source file ccnode\src\dbparamkeys.h
Blockchain = blocks in raw binary format (explained below)
Serialnums = a list of all spent serial numbers and hash keys
Commit_Tree = the Merkle tree of all transaction output commitments
Commit_Roots = the root value of the Merkle tree after each block that contains outputs
Tx_Outputs = index of all transaction outputs, including address, commitment, asset id (usually encrypted), and amount (usually encrypted)

This table stores only indelible data, which is data guaranteed by the CredaCash blockchain protocol to be immutable.  Temporary/mutable data is stored in memory, not on disk.

The information we've been posting here about the mint is stored under Key=7 of the Parameters table, with Subkey set to the block level, and Value set to the total number of mint transactions submitted to the network and seen by this node at each block level.  Here are the queries:

The average block interval (seconds per block) over the last hour:
select (1.*max(Timestamp)-min(Timestamp))/(max(Level)-min(Level)) from Commit_Roots where Timestamp > strftime('%s','now') - 3600;

The number of mint transactions per minute seen by this node over the last 210 blocks (approx 1 hour at 17 seconds/block):
select total(Value)*60/(max(Timestamp)-min(Timestamp)) from Parameters, Commit_Roots where Key=7 and Level = Subkey and Subkey>(select max(Subkey-210) from Parameters where Key=7);

The mint transactions per minute a miner needs to submit to earn an average of two mining rewards over the last hour:
select avg(Value)/30. from Parameters where Key=7 and Subkey>(select max(Subkey-210) from Parameters where Key=7);

The blockchain is stored in a raw binary format, which consists of a series of messages in the format:

  size, 4 bytes (total size, including this size field, the tag field and the data)
  tag, 4 bytes (currently used tags are: block 0xCC010001; mint tx 0xCC040001; pay tx 0xCC060001)
  data, variable size binary data

Most fields, including the size and tag, are stored little-endian.

A block consists of a binary header with zero or more binary transactions appended.  The block header is:

  signature, 64 bytes
  prior_block_oid, 16 bytes
  block_level, 4 bytes
  block_timestamp, 4 bytes
  block_witness_id, 1 byte

The transactions are in size/tag/data format.  The easiest way to extract the data in a transaction is to convert it to JSON format using the "tx-from-wire" command in cctx64.dll.  This can be done from python by calling the function DoJsonCmd located in the cclib.py library, specifically: DoJsonCmd('{"tx-from-wire":{}}', buf=).  Looking at the source code (without actually trying it), the blockchain parameters that have to be included in json format to reconstruct the full transaction are "source-chain", "maximum-input-exponent", "minimum-output-exponent", "maximum-output-exponent" and "merkle-root".  These parameters are all properties of the blockchain.

That's a brief dive into the CredaCash internals that can be used to extract information from the blockchain.  Eventually, we will have a block explorer.  If there are any questions, please let us know.  Thank you.

CredaCash mining update:

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

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

If there is an issue, a solution can probably be found (for example, a private link to a gateway server that is running Tor).

Do you anticipate there being any complication with worldwide exchanges listing CredaCash, since their servers must operate on TOR?

CredaCash mining update:

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

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

There is not currently a block explorer or a GUI wallet.  We would like to have both in the future.  A block explorer would probably come first, because this is required by some exchanges.  Note however there would not be much information in the CredaCash block explorer.  For each transaction, you would see a list of input serial numbers and hash keys, and a list of output addresses, commitments, encrypted amounts and encrypted asset id's.  All of these numbers appear completely random and don't relate to values in any other transaction (ie., none of those numbers should ever appear more than once in the blockchain).  The only information that might be useful would be the timestamp, size and number of transactions in each block, and the transaction fee/donation paid by each transaction.

Please let us know if you have any additional questions. Thank you.

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

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.

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.

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

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

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

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

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

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

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

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.