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

Our apologies for the difficulties.  Does the command "ping" work?  Is the console output of ccnode.exe still reporting new blocks (the latest block as of this post is level 203683).  If you do a listsinceblock command, how many transactions do you see with zero confirmations and what is the total value of their output billets? (Note that unconfirmed transactions should be listed last, but it may take a while for this command to complete because it filters out and does not report unconfirmed mint transactions that did not earn a mining reward.)  How does this compare with the balance reported by getbalance?  If you use the command cc.poll_destination to poll the address of one of the unconfirmed transactions, does the transaction then show as cleared after a short time?  Does the command listunspent show any unspent billets, and what is their total value compared to the amount you are trying to send?

P.S., did you at some point copy the wallet .ccw file to another computer and then start using it at two computers at the same time?  If so, then the balances of the two wallets might overlap, and when you send funds from one wallet, it could have made those same funds unspendable in the other wallet.

Transactions are cleared and coins can be sent. You just have to wait.

Seems like no additional billets are being generated / cleared. I should clarify I was trying to consolidate my balances across numerous wallets, however, no amount of waiting appears to remedy the issue. It's been at least 10 min since I attempted sending coins and now even attempting to send 500 coins results in the below message.

The wallet appears to have sufficient balance, but there are not enough billets available to construct the
transaction. It may be possible to manually solve this problem by sending transactions to yourself to split the wallet
balance into more output billets.

Error:
{
  "code" : -6,
  "message" : "Insufficient funds"

You can get the latest file by re-running the script ./get_genesis.sh and then restarting ccnode.exe and waiting a few minutes for the tor network to bootstrap.  Please let us know if that works for you, and our apologies again for the oversight.  Thank you.

Ok, big apologies, this is our fault.  The new distribution has a different rendezvous.lis file and it has not yet been updated for the Linux build process.  We will update it shortly and reply again when it is available to download.  Our most sincere apologies, and thank you for bearing with us...

everything works fine. Transactions are cleared and coins can be sent. You just have to wait.

No, problem not resolved by itself. But i didnt use ready version, used github and compiled. Maybe that could be problem?
Because old version worked correctly but new one doesnt find peers

Noted, thank you.  You could try stopping the wallet and then restarting with the command line or configuration file option "--tx-new-billet-wait-sec=180".  This will cause the wallet to wait 3 minutes for an expected incoming billet to clear before reporting "Insufficient funds".

The following explanation is based on the intended wallet design, not on actually testing, so the details might be slightly wrong.  Assuming the wallet holds a sufficient number of minted billets that all have a value of 1000 units, then to send 8000 units, the wallet will first construct two transactions that have four inputs of 1000 units each, and two outputs, one roughly 3999.9 units (slightly less than 4000 to account for the transaction fee), and one output of zero value (which is a dummy output that makes the transactions publicly appear as a standard 4-in-2-out).  After these two transactions clear and the wallet detects them as cleared (which might take 30-60 seconds), the wallet will construct a final transactions with 2 inputs of 3999.9 and one input of 1000, with one output of 8000 units to the intended recipient and one output sending the balance (the change) back it itself.  If it takes more than 90 seconds for one of the two intermediate transactions to be detected as cleared, the wallet will abort the send command and return "Insufficient funds".  In that case, nothing was sent to the intended recipient, but one of more of the intermediate transactions that sent consolidated funds back to the wallet may still be pending.  The amount of time the wallet waits is determined by the command line / configuration file option tx-new-billet-wait-sec, which by default is 90 seconds but we will likely increase that to 120 seconds in a future release based on this feedback.  When the wallet returns "Insufficient funds", you can wait a short amount of time and then retry the transaction.  The commands listtransactions and listsinceblock can be used to show which prior transactions have still not cleared (zero confirmations).  Once the transactions have cleared (1 or more confirmations), then the amounts the wallet expects to receive in those transactions can be spent.

Definitely some issues with the sending process.  Tried sending 100,000 out of a balance of 212,000 and it says insufficient funds after cutting it up into 25 transactions. Right now seems like sending multiple small chunks manually is working far better than large lump sums.

Any chance this problem has resolved itself?  What are log messages are you seeing now?

Sending 8000 units to destination CredaCash_b......

The wallet appears to have sufficient balance, but there are not enough billets available to construct the
transaction. It may be possible to manually solve this problem by sending transactions to yourself to split the wallet
balance into more output billets.

Error:
{
  "code" : -6,
  "message" : "Insufficient funds"
}


I got a similar messenge too, don't understand how the billets works in the transaction process 

Apologies--see my edits/additions in my prior reply. The wallet balance includes expected change or other funds the wallet sent to itself, but these might not be immediately spendable.  The "insufficient funds" message just means insufficient funds at the moment.  You could retry the transaction after a short wait.  If you want to do a little diagnosis before that, the commands listtransactions and listsinceblock can be used to show the transactions that have not yet cleared (zero confirmations).  As a last resort, you could stop the wallet and restart it with the --reset-wallet option and then run the listunspent command--that is really a last resort though--it is better to wait for the uncleared transactions to clear.  You might be able to force the wallet to detect a cleared transaction by polling the destination to which the billet was sent using the command cc.poll_destination where destination is the billet "address" reported by listtransactions or listsinceblock.

Normal response. all the coins are there.. but more than 10.000 does not want to send...

The most common cause of this message is that the wallet is expecting to receive change from a prior transaction, and needs that change in order to send the requested funds, but after some period of time the change has not arrived as expected so it gives up and returns that error.  This can also happen if the wallet submits one or more preliminary billet merge transactions (which it likely would do in order to send 15000 units) and the preliminary transactions does not immediately go through.  The amount of time that the wallet waits before reporting "Insufficient funds" is determined by the wallet command line or configuration file option "tx-new-billet-wait-sec" which by default is 90 seconds.

What do you get from getbalance?

Sending 15000 units to destination CredaCash_#########
Waiting for pending billets to become available...

Error:
{
  "code" : -6,
  "message" : "Insufficient funds"
}



WHY???

Put the folder in the root of drive C://

C:\CredaCash

apparently in the path has non-Latin characters

Hmm, looks like tor starts correctly:
Aug 16 19:10:02.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Aug 16 19:10:02.000 [notice] Bootstrapped 100%: Done

I think i get similar problem at beginning too, but forgot how to resolve it.

It could be that tor is still bootstrapping--that can take a while, like 2-5 minutes.  You could check earlier in the log though to see if it reports "Tor started", "Unable to start Tor", "Tor process exited unexpectedly" or any other messages regarding tor.

I get this error:

[2019-08-16 18:56:40.224515] [0x00007fbd34ff9700] [info]    Blocksync BlockSyncClient::ConnectOutgoing no blockchain servers found
[2019-08-16 18:56:44.224664] [0x00007fbd34ff9700] [info]    Blocksync BlockSyncClient::ConnectOutgoing calling GetHostName()
Aug 16 18:56:46.000 [notice] Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
[2019-08-16 18:56:46.621942] [0x00007fbc1effd700] [info]    torproxy command returned 91
[2019-08-16 18:56:46.621989] [0x00007fbc1effd700] [info]    Relay RelayService::ConnectOutgoing no relay peers found