Enable/Disable Staking
When a Lynx daemon has the staking function enabled, send transactions can be delayed.
Last updated
When a Lynx daemon has the staking function enabled, send transactions can be delayed.
Last updated
In the ~/.lynx/lynx.conf file, set the value to 1 to disable staking or 0 (zero) to enable staking thread on startup. Be sure to restart the daemon after changing this setting.
This RPC function is important. When a Lynx daemon has the staking function enabled, send transactions can be delayed. This results from the 30-block maturity required for each Lynx coin earned via Proof of Stake. The recommended steps for unimpeded send transactions are to turn off staking, restart the Lynx daemon, and wait for all Lynx coins to mature (30 blocks X 5 minutes each = 150 minutes). After 150 minutes, it is safe to send Lynx coins to another address. If you don't wait for all your Lynx coins to mature, your send transaction might be held by the network for 24 hours. Your coins will not be lost, but it can be frustrating being forced to wait by the network rules. The transaction will eventually be verified, but the recipient won't receive them or know they were sent until then. The transaction remains 'stuck' in the mempool, waiting to be verified, but it will eventually settle and clear itself. Once a transaction is stuck, it can not be undone.
Power users will run two Lynx daemons: one for staking and another as a hot wallet (for sending and receiving). Occasionally, the user will stop the staking process on the staking node, send the coins to the hot wallet node, and then resume staking. Make sure to retain enough coins on the staking node - the more coins staking, the greater your staking returns will be.
