Token Staking
Pools, durations, and rewards — user and project views.
Term-based staking with deterministic reward math, in both the holder view and the project administration view.
- project
- Lunor Demo
- token
- LUNR
- module
- staking
- category
- utility
- status
- live · sandbox
Every figure in this module's demo is fabricated. No wallet connection, no signing, and no broadcast path exists from this site.
The problem
Most staking interfaces are consumer apps with no operator surface.
Staking gets built as a front end: a holder can stake, claim, and withdraw, and that is the whole product. The project side — creating pools, adjusting rewards, monitoring total value locked, seeing who is actually participating — happens in a database or a script, if it happens at all.
The second problem is reward math nobody can verify. An advertised APY that cannot be reconciled against what a position actually earns erodes trust faster than a lower rate would have, and the support burden of explaining it falls on the project.
The approach
Both sides of the product, on the same record.
Holders see a portfolio: total staked, rewards earned, current rate, active positions, and available rewards. Before staking, the interface shows amount, duration, rate, estimated reward, unlock date, and total at maturity — so the outcome is explicit rather than implied by a percentage.
The project view administers it: create pools, set durations and rates, monitor total value locked, and see participants. Reward calculation is deterministic and inspectable, so a position's earnings can be reconciled rather than trusted.
Capabilities
What the module does.
Term pools
Multiple lock durations — 30, 90, 180, and 365 days — with independent rates.
Portfolio overview
Total staked, rewards earned, current rate, active positions, available rewards.
Pre-stake projection
Amount, duration, rate, estimated reward, unlock date, and total at maturity shown before confirming.
Position lifecycle
Stake, claim, re-stake, and withdraw once the lock duration permits.
Deterministic rewards
Reward math is inspectable so earnings reconcile against the advertised rate.
Project administration
Create pools, update rewards, monitor total value locked, view participants.
Dual views
Holder view and project view over the same pool and position records.
Emission budgeting
Reward liabilities projected across pools so an emission schedule is sized before it is offered.
How it works
The workflow, step by step.
- 01Choose a pool
Select a lock duration; each term carries its own rate.
- 02Enter an amount
The projection updates immediately with reward, unlock date, and maturity total.
- 03Stake
The position is created against the pool and appears in the portfolio.
- 04Claim or re-stake
Take rewards as they accrue, or compound them into the position.
- 05Withdraw at maturity
Principal and remaining rewards released once the lock duration permits.
- 06Administer pools
In project view, create and adjust pools and monitor participation.
Specification
At a glance.
- Lock durations
- 30, 90, 180, 365 days
- Demo rates
- 4% / 7% / 12% / 18% — sandbox figures
- Holder actions
- Stake, claim, re-stake, withdraw
- Project actions
- Create pools, update rewards, monitor TVL, view participants
- Reward model
- Deterministic and inspectable
- Public environment
- Sandbox — demo balances only
Security
Reward math is inspectable, and pool changes are versioned rather than silent.
- Reward calculation is deterministic so a position can be reconciled independently
- Pool configuration changes are versioned and recorded with an operator
- Withdrawal is constrained by the lock duration the holder agreed to
- Production custody remains in the staking backend, never in this site
- Public Console uses demo balances with no wallet connection
Full posture, including what we deliberately do not claim, is on the security page.
Use cases
Where it gets used.
Utility launch
Giving holders a reason to hold beyond price expectation, with terms stated precisely.
Duration experiments
Testing which lock terms actually attract commitment before committing to a rate card.
Treasury emissions
Distributing treasury as staking rewards on a predictable schedule.
Retention programmes
Longer-term pools aimed at reducing circulating float during a specific period.
Solution paths
Where this module sits in a bigger job.
FAQ
Questions asked before adopting this module.
Are the APYs real?
No. The 4, 7, 12, and 18 percent figures are sandbox values for the demo token, chosen to show how term and rate interact. Real rates are a function of your emission budget and the float you are trying to lock.
Can holders withdraw early?
Not by default — the lock duration is the commitment being rewarded. Whether an early-exit path with a penalty exists is a pool configuration decision, made deliberately rather than inherited.
How is the reward calculated?
Deterministically from amount, rate, and elapsed duration, and the projection is shown before staking. A holder should be able to reconcile their earnings without contacting support.
What can the project side actually do?
Create pools, set durations and rates, update rewards, monitor total value locked, and see participants. It is an administration surface, not a read-only dashboard.
Where are staked tokens held in production?
In the staking backend and its contracts, which are separate systems from this site. The public Console holds nothing and connects to no wallet.
Other modules
Same Console, same project record.
Next step
Run it before you ask us anything.
The Console needs no signup and no wallet. Open the module, use it against sandbox data, then bring us the specific questions.