Enable/Disable Staking

Published: January 2025 | Last updated: April 2025

Overview

When a Lynx daemon has staking enabled, transactions may experience delays. This document explains how to manage staking settings and avoid transaction delays.

Configuring Staking Settings

In your ~/.lynx/lynx.conf file, use the disablestaking parameter to control the staking function:

disablestaking=1  # Staking will be disabled after daemon restart

or

disablestaking=0  # Staking will be enabled after daemon restart

Important: Always restart the daemon after changing this setting for changes to take effect.

Understanding Transaction Delays

When staking is enabled, send transactions may be delayed due to the 30-block maturity requirement for each Lynx coin earned through Proof of Stake.

Recommended Process for Unimpeded Transactions

1. Turn off staking by setting disablestaking=1 in your configuration file

2. Restart the Lynx daemon

3. Wait for all Lynx coins to mature (30 blocks × 5 minutes each = 150 minutes or 2.5 hours)

4. After the maturity period, you can safely send Lynx coins to another address

Consequences of Not Waiting for Maturity

If you attempt to send transactions before your coins mature:

• Your transaction may be held by the network for up to 24 hours

• Your coins will not be lost

• The transaction will remain "stuck" in the mempool until verified

• Once a transaction is stuck, it cannot be undone

• The recipient won't receive the coins or know they were sent until verification completes

• The coins will eventually arrive at the destination.

If you review your debug log and see you have not won any stakes in the previous 35 blocks, you should be able to send coins without having to change the parameter and restarting the daemon.

Identifying Staking Activity

You can verify staking activity by checking for Proof of Stake block records in the debug log.

The record of a Proof of Stake block in the debug log.