Compile List Of Useful Pos Commands

Some linux specific commands:

./dcrctl --wallet gettickets 1 |grep "," -c

Gets you the number of (mature and immature) tickets in your wallet

./dcrctl --wallet gettickets 1 >temp;for line in `./dcrctl --wallet missedtickets|grep ","`;do cat temp|grep $line;done

This will save all the tickets you own to a file called "temp" then check to see if any of them are in the missedtickets list. If this command gives you any hashes, they have been missed tickets.

 

It might also be useful to compile a list all in one place of relevant block time frames such as ticket maturity, stake and stake reward return, difficulty change rate, avg/max stake vote time, etc etc.

Here is an explanation of pool size and difficulty change from another thread https://forum.decred.org/threads/wh...ulty-will-be-after-block-4096.771/#post-11398

 

Great initiative, this thread, thanks for the effort of making it. It will help us noobs.

The --walet getbalance "default" 0 all command shows different values at different times, and it's less than it should be, it's less than my total DCR I had before staking, is this how it's supposed to be? Shouldn't it be equal to my total amount of DCR staked and not ?

The blockchain explorer shows I got 2 transactions of 2 DCR each, but that happened in the first 2 hours of my mining, and after that, I got nothing for 12 hours. I'm confused - what are good ways to monitor how your stake mining is going ?

 

I did this small bash script that shows me some info. but you have to run your wallet like this

Code:

./dcrwallet --enablestakemining --balancetomaintain=(yours) --ticketmaxprice=(yours) | tee -a wallet.log

Code:

#! /bin/sh

cd (to location of your decred folder)
balanceall=`./dcrctl --wallet getbalance 'default' 0 all`
balancelocked=`./dcrctl --wallet getbalance 'default' 0 locked`
balancespendable=`./dcrctl --wallet getbalance 'default' 0 spendable`

ticketsallcount=`./dcrctl --wallet gettickets 1 | grep "," -c`
ticketsmaturecount=`./dcrctl --wallet gettickets 0 | grep "," -c`

votescount=`cat wallet.log | grep Voted | wc -l`
buycount=`cat wallet.log | grep SStx | wc -l`
failedvotescount=`cat wallet.log | grep Revoked | wc -l`

echo ""
echo "########## Decred report ##########"
echo ""
echo "             **Money**"
echo "   All: $balanceall"
echo "   Locked: $balancelocked"
echo "   Spendable: $balancespendable"
echo ""
echo "            **Tickets**"
echo "   All: $ticketsallcount"
echo "   Mature: $ticketsmaturecount"
echo ""
echo "            **Votes**"
echo "   Done: $votescount"
echo "   Failed: $failedvotescount"
echo "   Bought: $buycount"
echo ""
echo "###################################"
echo ""

 

I like this. I was doing something similar just at the CLI. But no reason to log to a file. You would not get everything from start, only session? There is a log at .dcwallet/wallet/logs/mainnet you could use for this. I think I might actually switch to yours and modify the data location. Then cron it every 5 mins or something.

 

I did it that way since I didn't knew about this . Thank you @drunkenmugsy. I'll do some updates as well

 

Linux commands for remote servers:

When you want to run the wallet and dcrd and have them stay running after you logout, you need to get it to run in the background, and disown the process. You do this as follows:

Code:

./dcrd > /dev/null &
disown
./dcrwallet --enablestakemining > /dev/null &
disown

Then when you logout and login, you should see dcrd still running merrily. I think piping the output to /dev/null is good practise, since the output is logged to ~/.dcrd/logs/mainnet anyway. Don't want the output to stdout to clog up a buffer or take up excess RAM.

If you already have the programs running and you want to change them to background mode, you can do "Ctrl+z" to suspend them, then enter "bg" to set them to run in the background. Then type "disown" to keep them alive after you logout.

An alternative to this is to use screen to launch and keep jobs running after you logout, but that's slightly more complicated than the background and disown method.

 

Yay, just got my first vote ... "Voted on block ... " - does this mean it was successfully completed and I got a reward ? How can I verify this, and is the reward always worth 2 DCR ?

 

This is how I run mine, I put in cron jobs to automatically start the daemon & wallet using screen and then unlock my wallet on boot. I rarely need to actually access the screen, I just cat the log file whenever I want to see what's going on.

 

I'm a lubuntu person, so no screen installed by default. Keep it lean and fast! & disown does the job!

 

Eh, can't argue with that approach! I guess it doesn't matter how you get it done so long as it works for you and meets your needs.

 

I did some updates to my script it gives more information now. I hope someone will find it useful.
If you have any fixes or ideas how I can improve it pleas do tell I want to make it a bit more useful and a bit better

Code:

#! /bin/sh

dcrwalletLogFolder="/home/(YOUR USER)/.dcrwallet/logs/mainnet/"
decredFolder="(YOUR PATH TO DECRED)"

cd $dcrwalletLogFolder
votescount=`cat dcrwallet.log | grep Voted | wc -l`
votedticketsperday=`cat dcrwallet.log | grep Voted | grep -o "[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]" | uniq -c`
buycount=`cat dcrwallet.log | grep SStx | wc -l`
boughtticketsperday=`cat dcrwallet.log | grep SStx | grep -o "[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]" | uniq -c`
failedvotescount=`cat dcrwallet.log | grep Revoked | wc -l`
failedticketsperday=`cat dcrwallet.log | grep Revoked | grep -o "[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]" | uniq -c`

cd $decredFolder
balanceall=`./dcrctl --wallet getbalance 'default' 0 all`
balancelocked=`./dcrctl --wallet getbalance 'default' 0 locked`
balancespendable=`./dcrctl --wallet getbalance 'default' 0 spendable`

ticketsallcount=`./dcrctl --wallet gettickets 1 | grep "," -c`
ticketsmaturecount=`./dcrctl --wallet gettickets 0 | grep "," -c`
ticketprice=`./dcrctl getstakedifficulty`

echo ""
echo "########## Decred report ##########"
echo ""
echo "             **Money**"
echo "      All:          $balanceall"
echo "      Locked:       $balancelocked"
echo "      Spendable:  $balancespendable"
echo ""
echo "            **Tickets**"
echo "      All:          $ticketsallcount"
echo "      Mature:       $ticketsmaturecount"
echo "      Price Now:   $ticketprice"
echo ""
echo "       **Bought Tickets Per Day**"
echo "$boughtticketsperday"
echo ""
echo "            **Votes**"
echo "      Done:         $votescount"
echo "      Failed:       $failedvotescount"
echo "      Bought:       $buycount"
echo ""
echo "       **Voted Tickets Per Day**"
echo "$votedticketsperday"
echo ""
echo "       **Failed Tickets Per Day**"
echo "$failedticketsperday"
echo ""
echo "###################################"
echo ""

 

You can call ./dcrctl getstakedifficulty rather than parsing the last block and looking for the sbits string in the getblock of that!

 

Thank you for this and will fix it in the previous post code as well.

 

if you update to newest binaries, you can use --wallet getstakeinfo for alot of this info

 

If you can do the same for windows, i will send you 2 stake rewards - exorbitant tx fees. Is that reasonable?