Staking v6.2.2

Release Date: August 27, 2026 Tags: LANDING PAGE, REWARDS, TRANSLATIONS, FORMATTING

Overview

A public-page release. The staking landing page is now built on the server, so a visitor's first paint carries the real pool and APR figures rather than placeholder bars, and two lines on that page that promised customers they could claim rewards whenever they liked have been rewritten to describe the payout schedules the product actually offers.

Nothing here touches a rate, a balance or an accrual, and there is no existing figure to re-check. Requires Core v6.7.3.

Update Instructions

pnpm updator

Ship the frontend build. There is no database change and no configuration.

Changed

The landing page arrives with its numbers already in it

• Changed the staking landing page to build its featured pools, its high-yield, flexible and upcoming pool tabs, its token grid, its recent-activity feed and its headline APR and staking figures on the server. The page a visitor first sees already carries the real numbers, instead of placeholder bars that then pushed every section beneath them down the page as the data landed.
• If the server cannot reach the staking data while rendering, the page falls back to the browser-side request it has always made and shows the same outage message as before.

Thousands separators on the landing page and the pool browser

• Changed five figures on two screens to use American thousands grouping for every visitor instead of following the visitor's browser language. On the public landing page that is the active-stakers count — which appears twice, in the hero and in the metric strip — and the example amount in the earnings-calculator preview. On the pool browser it is each pool card's total-staked and available figures. A visitor whose browser is set to German or Brazilian Portuguese read 1.234 in those places and now reads 1,234.
• A fixed separator is what keeps the landing page's first paint and the settled page reading the same, now that those figures come from the server.
• Ten other staking figures still group by the visitor's browser language — the pool detail page, the stake form on it, the positions page, and the admin pool and position screens — so staking numbers remain mixed.

Fixed

The landing page told visitors they could claim rewards whenever they liked

Two places on the public staking landing page told every visitor that rewards could be claimed the moment they felt like it, no matter how the operator had configured their pools. The trust row read "Rewards accrue daily — Claim whenever you like", and the panel below it promised rewards "accrue continuously and can be claimed or compounded whenever you want, including mid-term on flexible pools". Pools on this platform pay daily, weekly, monthly or only once at the end of the lock term, and a position set to auto-compound returns its rewards with the principal at maturity. An operator running a locked term-end pool therefore had a public page advertising a freedom their own pools did not offer, and a customer who staked on that promise found no claim control on the position at all.

• Fixed the trust row to state the four payout schedules that actually exist — daily, weekly, monthly or at term end — and the panel to say plainly that pools paying at the end of the term, and positions set to auto-compound, have nothing to claim until they mature. The new wording is translated into all 90 languages.
• The "how it works" strip further down the same page is unchanged and still carries a step headed "Claim anytime", so the page has not yet been cleared of the overclaim entirely.