Logo

LUKSO Staking Services

Choose between pooled staking and operating your own validators with setup or ongoing assistance. The website services page introduces the current offer; these docs explain responsibilities and preparation.

Non-Custodial Staking Pool

The LUKSO staking app lets you deposit LYX into a staking vault. Review the current fees, capacity and restrictions before depositing. Liquid token conversion is optional, and withdrawal availability depends on the applicable contract and network process.

Follow the LUKSO deposit and withdrawal guide for the operational checklist and risks.

Home Staking

Running your own validators requires reliable infrastructure, secure keys, monitoring, updates and an exit plan. Setup assistance does not remove those responsibilities. Never operate the same validator signing keys in two active instances; plan migration and recovery carefully.

1) White Glove Service

A tailored ongoing service can cover validator-server management or assistance with infrastructure you maintain. Confirm eligibility, supported setup, recurring charges and responsibilities in a written offer before proceeding.

2) Set-Up Service

Setup assistance can cover preparing the node, planning validator generation and deposits, configuring clients, restart behavior and monitoring. Agree who performs each action and controls each key before work starts. Do not send recovery phrases or withdrawal credentials' private keys through a contact form or support chat.

3) Consultation Service

For troubleshooting, prepare the network, client versions, symptoms, relevant public validator identifiers and redacted logs. Remove passwords, tokens, private keys and other secrets. Agree the scope, billing basis and any access required before the session; diagnosis does not guarantee a fix within a particular time.

Before Booking

  • Explain whether you want a pool deposit, your own node setup, troubleshooting or ongoing management.
  • Specify the network, existing hardware or hosting, client versions and the outcome you need.
  • Confirm the current price, taxes, prepayment terms, support period, cancellation terms and any recurring charge in the offer. Historical documentation prices should not be treated as a quote.
  • Agree key custody, signing and withdrawal control, remote-access scope, handover documentation, backups and recovery responsibilities.
  • For a new validator, use the network's current official launchpad and instructions; do not reuse deposit data intended for another network.

Request a current offer through the contact form. For public explanations and service options, see stakingverse.io/services.

Pool or Solo Staking

  • Pool staking: the operator runs validators, while you manage your wallet, deposit and exit. You pay the configured reward fee and transaction gas, and depend on vault contracts, privileged roles, validator operations and withdrawal liquidity. A liquid token is optional and adds conversion and market considerations.
  • Solo staking: you fund validators under the network's current requirements and take responsibility for hardware or hosting, power, bandwidth, secure keys, updates and incident response. There is no pool reward fee, but operating expenses and time reduce the net return. You also manage activation and exit procedures.
  • Assisted solo staking: setup or management support can reduce the operational workload. Confirm fees, access and key-control responsibilities explicitly; paying for assistance does not automatically transfer every risk or maintenance duty.

Compare expected rewards after all costs, without assuming a fixed APY. For pool fees use the current app; for assistance use a written quote. Both routes expose funds to validator penalties and delayed exits.

LUKSO Solo Validator Checklist

Use this as a preparation and verification checklist alongside the current official guides. Network rules and supported software change; follow the linked instructions for exact versions and commands rather than relying on an old copied command sequence.

1. Rehearse on testnet

Practice setup, key import, deposit, monitoring and exit using the LUKSO testnet. Keep testnet keys, directories and deposit data separate from mainnet. A successful rehearsal is useful preparation but does not guarantee mainnet safety.

2. Plan hardware and availability

Check the official node requirements for the clients you choose. Budget for storage growth, reliable connectivity and ongoing operation. Decide who responds to alerts, restores service after outages and maintains backups.

3. Install and synchronize the node

Choose a supported installation route, such as the LUKSO CLI, Dappnode or Docker, from the official node guide. Set up a dedicated data directory, select compatible execution and consensus clients and initialize the intended network. Verify both layers are synchronized and connected before relying on the validator process.

4. Generate keys and verify destinations

Follow the official validator guide for the current key-generation flow and funding requirements. Use the official key-generation instructions and secure the recovery material offline. Verify network, public keys, withdrawal credentials and intended deposit amounts before producing or uploading deposit data. The execution fee recipient and withdrawal destination serve different purposes; check both.

5. Import and prepare the validator

Import the intended keys using the supported client flow, check the imported public-key list and configure the execution reward recipient. Verify that only one active validator instance can use each signing key. When moving an existing validator, follow the client's slashing-protection and migration procedure before enabling the replacement.

6. Deposit through the official launchpad

Reach the LUKSO deposit launchpad from the official validator instructions. Review the network, deposit data, public keys, amount and withdrawal destination before submitting any transaction. Keep the transaction hashes and monitor activation status. A deposit confirmation and an active, correctly performing validator are separate milestones.

7. Monitor, update and test recovery

Track client health, synchronization, connectivity, disk space and validator performance. Arrange alerts and review official network upgrade notices. Use supported releases, plan maintenance and verify duties resume afterward. Protect backups without creating a second active signer. Redact secrets before sharing diagnostic logs.

8. Understand and verify the exit

Read the current official exit procedure and withdrawal requirements before depositing. Confirm which credentials and keys are needed, where funds will arrive and how to monitor completion. Network processing affects timing; neither a submitted exit nor an explorer status by itself proves the final withdrawal has arrived. Reconcile the destination balance and transaction history.

For assistance, provide the stage you have reached and the public error or transaction details through the contact form above. Never upload mnemonic phrases, keystores or private credentials as troubleshooting attachments.