Réti Open Pooling now holds 725M ALGO staked by 8,693 users across 225 validators

The 30,000¹-ALGO barrier

Solo staking on Algorand became a high-barrier exercise in January 2025, when the network switched on protocol-level consensus rewards: participation demanded a 30,000² ALGO minimum, a node running on hardware you control, and the ongoing upkeep Pure Proof-of-Stake participation requires. Réti Open Pooling¹ was built by the three-person Algorand studio TxnLab² to let everyone else participate. It is a permissionless staking protocol: anyone can register as a validator, anyone can direct ALGO to one, and each pool's funds sit in its own smart-contract account rather than a third party's wallet.

The master contract on mainnet (app id 2714516089³) is a live census of how far that design has traveled. Its global state currently records 725.9 million ALGO staked by 8,693 stakers across 225 validators.

Non-custodial does not mean trust-free, though. The node-daemon documentation states plainly that 'the only accounts that can ever remove user funds are stakers removing only their (compounded) balance' — no validator, manager, or protocol operator can withdraw on a staker's behalf. What a staker still chooses is an operator: yield depends entirely on how well the validator runs its node and the Réti daemon, and the reference dashboard is hosted by Nodely, the infrastructure company whose co-founder Patrick Bennett also co-founded TxnLab. Anyone can deploy their own interface to the same contracts, but the default one is insider-run.

A pool is its own contract

A validator does not run one big pool. Registering through the master validator contract lets it create up to a defined limit of pools per node — the contract caps this at 3⁴ pools per node across up to 8 nodes — and every pool originates as a unique contract instance created from a pre-defined template, giving it its own Algorand account eligible for consensus participation. Stakers choose a validator by ID and the system routes the stake into a pool the staker already uses, unless that pool is full.

The protocol considers a pool full at the lesser of 15%⁵ of online stake divided by the validator's number of pools, and the per-account maximum that still earns incentive rewards (around 70 million⁶ ALGO today). A validator whose combined pools reach 15%⁷ of online stake stops accepting new ALGO entirely — a hard cap meant to keep any one operator from capturing a dangerous share of consensus.

Each pool's on-chain ledger tracks up to 200 stakers, recording who entered, when, with how much, and the rewards accumulated since. The entry timestamp is the anti-gaming mechanism: rewards are adjusted by time in pool, so a large stake dropped in moments before payout cannot capture an outsized share of that epoch. A minimum entry requirement — the docs cite 1,000 ALGO as a typical floor, while the contract's own minimum is 1 ALGO — keeps out dust, and every staker above capacity forces another pool, another node, and ultimately another validator.

Rewards: epochs, commissions, and time

Rewards are distributed at the end of each epoch, a fixed period the validator picks and which can be as short as roughly a minute. A pool earns only when it proposes blocks — it must clear the participation threshold noted above, stay under the ~70 million⁸ reward ceiling, and perform well. The validator takes a commission, a percentage fixed at registration and immutable afterward, and the remainder is split among stakers proportionally to their stake and their time in the pool during the epoch, then added straight to their balance to compound.

The time adjustment applies in both directions. A staker who adds stake 95%⁹ of the way through an epoch receives 5%¹⁰ of the reward they would have earned for a full epoch, and each addition resets the clock; removing stake before an epoch ends forfeits that epoch's accrued rewards. Stake can be removed at any moment, either the entire balance or anything above the pool's minimum entry.

Two further constraints shape the economics. First, saturation: a validator holding more than 10% of online stake is considered saturated — rewards are reduced proportionally to how far over the line it sits, the validator receives nothing, and the withheld remainder flows to the fee sink. The model, suggested by Stefano De Angelis during development, relies on an AVM opcode that lets contracts query the live online-stake figure. Second, token rewards: a validator can attach its own token as a bonus paid alongside ALGO — the docs name VEST, COOP and AKTA as examples, and live pools on the dashboard pay out GLIZZY, COSG, STEAK, ALC, ORA and aVoi. The reward token is fixed when the pool is created; the rate can change at any time.

The validator-side structure, and what each piece means for a staker:

The software layer that makes this run is the Réti node daemon, a CLI/service daemon for Linux, macOS and Windows that automates participation keys (short-lived, created only once a pool actually has stake) so pools stay online. Notably, any account can trigger an epoch update if a validator's daemon goes offline, so payouts do not stall on a single operator. Costs are bounded: registering a validator costs 10.4449¹¹ ALGO to the fee sink plus 6.1978¹² ALGO per pool in storage. The protocol itself charges no fees — but that statement covers only the protocol. Every validator takes a commission (the dashboard shows a spread from 0.4269% to a full 100%), and very short epochs burn transaction fees on each payout; the docs estimate 7–29¹³ ALGO a day for one-minute epochs.

Who runs it

Réti's contracts are written in TEALScript via AlgoKit, and the code lives under the Algorand Foundation's GitHub organization³ rather than TxnLab's — 44¹⁴ stars, still actively developed. The latest release, v1.5.0 on 2026-08-15, is a UI performance release: the dashboard previously issued roughly 900 algod requests on open and now collapses that into a handful of bulk reads, with no contract or node-daemon changes. v1.4.0 (September 2025) added an institutional support page and an xGov signup flow for pool owners. Earlier releases have also shipped workarounds for contract bugs — v1.3.4 disabled staking when a validator's first pool was full because of a bug in the findPoolForStaker logic.

On audits, what is published is thinner than the 'audited' label implies. The repo's audit folder contains one named report — CoinFabrik's 'Réti Audit 2024-08' — and DeFiLlama lists two audits pointing at that folder, without identifying a second. Institutional adoption is real: staking provider Kiln⁴ runs its Algorand validators on Réti pools (auto-compounding, rewards every three hours, instant unbonding, no slashing), and P2P.org launched ALGO staking on its validator in May 2025 pointing customers at the same dashboard. Kiln's docs describe the contracts as 'audited, controlled and deployed by the Algorand foundation'.

The governance contradiction

That last phrase is where the tension sits. The Foundation stewards and deploys Réti's contracts — and the Foundation also runs the governance program that, as of June 2025, excludes every Réti pool. Ahead of governance period 15¹⁵, the Foundation announced⁵ that the Réti smart contract 'does not provide a way to integrate with governance': voting requires a zero-ALGO transaction carrying a note field, and a pooled application account cannot produce one that the off-chain governance indexer can attribute to individual stakers. Supporting Réti, the Foundation said, 'would require a custom implementation', unlike liquid-staking tokens which share a common standard. One forum critic at the time wrote that '400M¹⁶ staked Algos disapproved, the place where those with smaller bags can participate in a collective manner is kicked out of governance' — a contemporaneous community claim, not a verified figure, but the frustration it captures is documented throughout the thread.

The gap has since been bridged from outside the Foundation. Valar Solutions⁶, the Swiss staking company, shipped an xGov integration for its fork of the Réti UI in May 2026: stakers signal their view on proposals with zero-payment note transactions, the validator aggregates those signals and votes, and stakers who do not express an opinion see their voting power delegated to the validator owner. The xGov Council backed the proposal⁷ 10–0 with one abstention. What this means in practice: a Réti staker's governance voice depends on which validator they chose and whether that validator enrolled in third-party tooling like Valar's — not on anything the base protocol provides. Whether all 225 registered validators are independent operators is likewise unattested: they are permissionless on-chain records, and the dashboard shows a long tail of community-run pools alongside project-run ones such as pool.valar.algo and node.cosmicchamps.algo.

The scale, in numbers

DefiLlama⁸ tracks Réti as a staking-pool protocol and puts its current TVL at $61.3 million — down from an August 2025 peak of $103.7 million, ranking fifth among the 73 staking-pool protocols it tracks, 0.5% of that $12.7 billion category. The comparison that puts the number in perspective is internal to Algorand: DeFiLlama's headline figure for all of the chain's core DeFi is $28.5 million, so Réti alone locks more than twice what every other application on the network holds. Measured against the chain itself, the stake noted above is roughly 36% of the ~2.01 billion ALGO currently online — itself 20.6% of total supply.

The curve shows the shape of the launch: TVL went from roughly $2.5 million in January 2025 to more than $100 million within seven months, then drifted down with ALGO's price through late 2025 before stabilizing in the $57–78 million band this year.

What a staker actually does

Getting in is a wallet connection: the dashboard⁹ supports Defly, Pera, Lute, WalletConnect, Kibisis, Exodus and W3 Wallet. Pick a validator, enter at least its minimum entry amount, sign, and the position appears under 'My Stakes'. Unstaking is immediate, subject to the whole-balance-or-above-minimum rule. The honest caveat in the docs: the APY estimates shown per validator are a work in progress and 'may not be 100% accurate', so comparison shopping against the live fee, token-incentive and payout-frequency columns matters.

Réti has delivered something rare on Algorand: scale the rest of the chain's DeFi does not approach, on contracts whose parameters are immutable and knowable in advance. The open questions are the ones its own architecture cannot answer — who you picked as your operator, and when the Foundation that stewards the protocol will also let it vote natively.

Source (21)

• txnlab.gitbook.ioRéti Open Pooling documentation
• reti.nodely.ioRéti Pooling dashboard
• github.comalgorandfoundation/reti on GitHub
• defillama.comDefiLlama: Reti Pooling
• docs.kiln.fiKiln docs: Algorand (ALGO)
• forum.algorand.coAlgorand Foundation announcement: Réti Pooling and Governance Period 15
• forum.algorand.coValar xGov integration for Réti Pooling
• reti.valar.solutionsValar Réti Pooling dashboard
• p2p.org
• txnlab.gitbook.ioDISCLAIMER | Réti Open Pooling
• txnlab.gitbook.ioRewards | Réti Open Pooling
• txnlab.gitbook.ioSmart Contracts | Réti Open Pooling
• txnlab.gitbook.ioRéti Pooling Overview | Réti Open Pooling
• txnlab.gitbook.ioRewards | Réti Open Pooling
• docs.kiln.fiAlgorand (ALGO) | Kiln docs
• txnlab.gitbook.ioQuick Start For Stakers | Réti Open Pooling
• txnlab.gitbook.ioValidators | Réti Open Pooling
• txnlab.gitbook.ioReti Node Daemon | Réti Open Pooling
• txnlab.gitbook.ioMainnet Deployment | Réti Open Pooling
• txnlab.gitbook.ioKey Features For Validators | Réti Open Pooling
• txnlab.gitbook.ioFAQ | Réti Open Pooling