A lot of times you will hear (or see) people in chat rooms and forums point to getting Staking Rewards as a "lottery". Indeed it is, but if you are into looking at the right input stack size for staking, you probably are wondering what is the sweet spot.
Like you, am also finding out what that number is.. (and the default input stack size of the WORX wallet is 30). So I took to the blockchain information to find out that number. By the way, to get to this 30, you may execute this command on your VPS.
worx-cli getstakesplitthreshold
For a general review of the posts involving WORX coin, you may want to visit any of the posts below:
* WORX Masternode Debugger
* WORX Wallet "bootstrap.dat" File (Alternate Method)
* Create a WORX Wallet "bootstrap.dat" File
* Worx-Calculator Spreadsheet Shared
* Conclusion: WORX Staking vs MasterNode Study
* PoS: Setup Staking Wallet with Worx Coin
* Data-Driven Decision: Stake Coins vs Masternode Collateral
This decision is likewise data driven. So I wrote a Python script to gather that information from the blockchain. And to visually paint the stack sizes of the last 100k blocks of WORX. It doesn't look too good, so I reduced the number of data points to 25k, as you will see below.
(then last 5,000 blocks..)
And eventually I settled with the last 2,500 blocks. The visual picture below gives it a little bit of justice -- it is just pretty!
At this point it is notable that the average input stack size is 108 WORX (median standing at 37). Given these information, I set my stack size to 70 (the closest round number to AVERAGE less the MEDIAN). I'm guessing the sweet spot must be between these numbers.
To set yours, on the VPS terminal of your hot wallet, execute this command:
worx-cli setstakesplitthreshold 70
Or, on the "Debug Console" of your hot wallet, execute this:
setstakesplitthreshold 70
If this information has helped you in any way, send me a tip via this WORX address: WShjWUBHmXaiuqauauhMeDK93S3ac2xDXC
Considering Bitcoin has maintained a $6,000 support ...
