Under what circumstances is it beneficial to run consolidate? I believe I understand what it does, but I see no good reason to use it. Surprised to see that some people consider it a regularly used command
In a general order of frequency of use: --wallet getbalance --wallet getbalance default 0 all --wallet getstakeinfo --wallet getticketmaxprice --wallet setticketmaxprice --wallet getticketfee --wallet setticketfee --wallet purchaseticket ticketfeeinfo 0 1 --wallet walletpassphrase --wallet gettickets true --wallet listtransactions * 100 help --wallet consolidate --wallet getaccount --wallet getnewaddress rebroadcastmissed --wallet getwalletfee --wallet settxfee
dcrd dcrctl --wallet getstakeinfo dcrctl --wallet getbalance "default" 0 all dcrctl --wallet getbalance dcrwallet --walletpass --enablestakemining --balancetomaintain= --ticketmaxprice= dcrctl --wallet walletpassphrase 0 dcrctl --wallet rebroadcastmissed
Which commands do I use? Exhaustive behavioral tests of the software!? Well here is the issue I filed about the inconsistencies of the commands and how they can be better organized. https://github.com/decred/dcrwallet/issues/212
In Windows, a batch file named "status.bat" with the following commands: dcrctl -u xxx -P xxx --wallet getbalance default 0 spendable dcrctl -u xxx -P xxx --wallet getbalance default 0 locked dcrctl -u xxx -P xxx --wallet getbalance default 0 all dcrctl -u xxx -P xxx --wallet getstakeinfo dcrctl -u xxx -P xxx --wallet walletinfo and of course some other basic stuff such as: dcrctl -u xxx -P xxx --wallet setticketmaxprice xx
@_ingsoc @ceejep I think a way or a command to only unlock wallet for voting will be great and really useful if that can be possible, since there will be less security concerns about someone accessing an unlocked running wallet and messing with it's funds, it's fees, etc.
Feature request: I run a batch file containing both getstakeinfo and ticketfeeinfo. The info is quite comprehensive. However it would be nice if they also returned the current block number for which the info is valid.
Running ticketfeeinfo shows "feeinfoblocks" array of maps, each contains "height" - that is your block number for which the info is valid.
Try dcrctl --wallet ticketfeeinfo 1 0 Spoiler: result { "feeinfomempool": { "number": 0, "min": 0, "max": 0, "mean": 0, "median": 0, "stddev": 0 }, "feeinfoblocks": [ { "height": 36620, "number": 0, "min": 0, "max": 0, "mean": 0, "median": 0, "stddev": 0 } ], "feeinfowindows": null } Spoiler: help dcrctl --wallet help ticketfeeinfo ticketfeeinfo (blocks windows) Get various information about ticket fees from the mempool, blocks, and difficulty windows Arguments: 1. blocks (numeric, optional) The number of blocks, starting from the chain tip and descending, to return fee information about 2. windows (numeric, optional) The number of difficulty windows to return ticket fee information about Result: { "feeinfomempool": { (object) Ticket fee information for all tickets in the mempool "number": n, (numeric) Number of transactions in the mempool "min": n.nnn, (numeric) Minimum transaction fee in the mempool "max": n.nnn, (numeric) Maximum transaction fee in the mempool ... .... ...
Hi...i am a new user here. My best guess is that 3 phantom transaction are there due to funds being transferred between addresses within my local wallet. All "duplications" are there most probably due to the same reason which can actually be understood as transaction within the wallet has dual nature - one is the 'send' and the other the 'receive' part. What I don't understand is why the last actual transaction (sending 0.74 DCR from online wallet to the local one) is also duplicated. I would expect there to be only the 'receive' part but using listtransactions shows also the 'send' one:
it's all main ./dcrctl -u user -P password --wallet consolidate 99999 default ./dcrctl -u user -P password --wallet getbalance default 0 all ./dcrctl -u user -P password --wallet getbalance default 1 all