If you have staked any crypto currencies you know that you have to (with many projects) run what is called “Coin Control” to place all your coins back in one input to get rewards faster. I decided to build out a .NET Core Control Control application that includes a class library that will communicate with any wallet that uses Bitcoin type RPC commands. I am currently using this on a staking wallet for the crypto LINDA Project ($LINDA).
Coin Control Process
The coin control process can be time consuming since you do not know when you will get a reward and you have to continue to check your wallet. Doing this automatically would help get rewards more consistently and without any lags.
Screen shot of the Coin Control App (CC) (Microsoft Windows Example). In this case the CC app will run every 30 minutes checking for a reward. Once a reward is found the CC process runs to send all the coins to the main staking address in the wallet and unlocks the wallet for staking again.
- Wallet Passphrase is encrypted by a feature in the app and cannot be decrypted.
- Email password is encrypted by a feature in the app and cannot be decrypted.
- The app will not send coins to any address if it does not exist in the staking wallet.
Configuration is very flexible you setup your RPC Information, your staking address, and (using a feature of the app) encrypt your wallet passphrase to make it secure.
There are security features in the app that only allows the Coin Control sending of transactions to an address that exists in the wallet. If you change the “WalletStakingAddress” to an address that does not exist. The app will show an error and the process is halted.
Logging and Email
The application logs all processes and errors and sends emails once a Coin Control cycle is complete.
Use with Other Staking Wallets
We are testing and using this currently for LINDA. Any wallet that supports the following RPC commands would work with this process.
This process has worked so well that I moved any LINDA Master Nodes to all staking. This way I do not have to monitor any issues with a master node.