← Back

Frequently asked questions

Each decision the bot records carries one of these:

Held
Your bucket is with a validator that holds a consensus seat and is earning, so it is left alone. Moving forfeits a full epoch of rewards, and only jail justifies that.
Waiting for a seat
No validator that passes the rules has room right now. Six seats rotate every epoch, so the bot looks again at each boundary.
Kept
A move was considered and the current position was still the better one.
Not worth it
The improvement would not cover what moving costs. That cost recurs, because a seat lasts about three and a half epochs before rotation takes it away.
Better yield · Placed · Rescued
The bucket was moved. The card names where it went and why.
Waiting (jailed)
The validator is jailed but the epoch still has time to run. Jail is often lifted before it ends, so the bot waits rather than spend a move.
No gas · No service balance
A move was decided but not made: your wallet could not cover the network fee, or your prepaid balance could not cover the service fee.

Only one that currently holds a consensus seat: a validator in the eligible pool produces no blocks and earns nothing. On top of that it must meet all of the following.

Delegation cap between 10 and 70 million KLV
The cap is what bounds dilution — it fixes the smallest share your bucket can fall to. No cap means no floor. A cap under 10 million bounds the stake the validator itself can hold, and one that cannot accumulate stake does not keep its seat for long.
Commission of 70% or less
Commission is the validator's cut of the block rewards your delegation earns. It does not touch the staking half.
At least 1,500,000 KLV of its own stake
That is the network minimum. Falling below it means the operator is deregistering or has been slashed.
Open to delegation, with room for your bucket
A validator can have free capacity and still refuse new delegations, in which case the transaction is simply rejected.
In its first epoch of a seat — for yield moves only
That is when capacity on a good validator actually exists; delegators fill new seats within minutes. A bucket that is earning nothing is exempt, since it cannot afford to wait for the perfect entry.

Because moving costs money and forfeits an epoch of rewards, and a consensus seat is not permanent — about six of twenty-one rotate every epoch, so the cost recurs. The bot compares what a move would earn over the life of a seat against what simply staying is worth, and acts only when the difference clears both. A history full of held decisions means your stake is already in a working position.

On KleverChain, staking rewards expire after 100 epochs (about 25 days). If you don't claim them in time, they start to burn and are permanently lost. Klever Pocket solves this by automatically claiming rewards before they expire and optionally reinvesting them back into staking.

Klever Pocket is an automated reward manager for KleverChain. It can claim staking rewards on schedule and optionally restake them to compound your earnings.

Yes. The bot receives a strictly scoped permission limited to Claim and Freeze operations only. It cannot transfer, withdraw, or unstake your tokens. The permission module is fully open-source — you can review the code at github.com/xportdao/klever-permission-module. You can also verify your account permissions directly on the blockchain at any time.

All rewards go directly to your wallet. The bot only triggers the transaction from your account.

Network fees for claim and freeze transactions are paid directly from your wallet. The service fee applies only to automated operations and is deducted from your balance inside the app.

No. Once permissions are granted, the bot runs independently. You can check your dashboard anytime to see claim history and upcoming schedules.

Connect your Klever Wallet, select the tokens you want to manage, and grant the required permissions. In the basic setup the bot automatically claims rewards before they expire. If you also grant Freeze permission, it can automatically reinvest rewards back into staking.

By default the bot claims rewards about every 20 days, leaving a safety buffer before the 25-day expiration window. If reinvest is enabled, rewards are frozen back into staking right after the claim.

Yes. You can configure your own claim and reinvest interval. Keep in mind that in manual scheduling mode the bot does not evaluate reward value, so rewards could sometimes be smaller than the combined network and service fees.

Granting permission to the bot is a one-time transaction that requires about 1000 KLV in network fees. After that you only pay normal network fees for claim and reinvest transactions.

You receive a welcome bonus with several free automated operations. After the bonus is used, you need to top up your service balance so the bot can continue claiming and reinvesting rewards automatically.

Klever Pocket supports all KleverChain tokens that generate staking rewards, including KLV, KFI, and any KDA token with APR or FPR staking.

Yes. If you trigger claim or freeze manually inside the app, there is no service fee. You only pay the standard network fee.