Steak Pool burns 11% of STEAK supply with Réti validator commission

Proof of steak, on-chain

Four days after the STEAK token appeared on Algorand in mid-December 2024, its first burn arrived at BNFIREKGRXEHCFOEQLTX3PU5SUCMRKDU7WHNBGZA4SXPW42OAHZBP7BPHY¹² — a vanity-prefixed address whose private key, the project maintains, was never derived by anyone and therefore cannot be held. The transparency ledger³ on Steak Pool⁴'s site has since logged 274 separate burn transactions into that sink, which the project calls BNFIRE, as in bonfire.

The unusual part is the revenue behind the burning. STEAK (ASA 2595619475⁵⁶) is an Algorand Standard Asset — a token issued natively on Algorand's base layer, the same mechanism used for stablecoins and NFTs — built around a deflationary thesis: buybacks funded by validator earnings rather than a treasury set aside for burns. The pitch, in the project's own words: 'Burn the supply. Eat the gains.'

Validator commission as the burn engine

Steak Pool operates validator #13⁷ on Réti⁸, Algorand's open-pooling protocol, which lets any holder delegate ALGO to a validator pool without giving up custody. That non-custodial design is load-bearing for the whole model: stakers never hand their coins to Steak Pool, the Réti contract pays out block rewards each epoch, and the validator's commission is routed to a single destination — the buyback-and-burn path. Pool #13 currently holds 228,313 ALGO across 50 delegators, a fraction of its 70 million ALGO capacity, with a 300 ALGO minimum entry.

One delegation activates three streams at once:

Sources: 9 reti.nodely.io, 10 algostakepool.com

The pool's own account (LEADNO4W...) carries both the delegated ALGO and the undistributed STEAK reserve — one address, two jobs, and the conduit for all three streams. The 450¹²-STEAK payout is fixed regardless of pool size, so each delegator's slice dilutes as more ALGO joins; the project says early stakers capture a larger share per unit staked, while the commission-funded burn rate grows with the pool.

A burn ledger with two eras

The cumulative curve of burned STEAK hides two distinct histories:

In the first era, beginning with the first burn on December 17, 2024 (round 45,348,579), the burns were manual and lumpy: a single 500,000-STEAK transaction in January 2025, repeated burns from the account that would later deploy the automated contract, and a burst of dozens of 65-to-100-STEAK transfers from separate wallets in early February 2025 that reads as a coordinated holder event. The ledger's steady era is newer — daily contract-triggered cycles that appear in the transparency page's most recent entries. Today the supply lives in four buckets:

Source: 13 algostakepool.com

The burn wallet itself holds more than 8,500 different assets — the profile of a shared community burn sink, not a wallet Steak Pool controls — and its recent transaction history shows only inbound transfers.

The AutoBurn contract

The automated version arrived in May 2026, after a site rebuild that moved every dashboard onto live indexer reads. The validator commission now flows to the AutoBurn contract, an Algorand application (app 3551596743¹⁴) deployed May 10, 2026, that the project describes with two claims: 'no admin key, no operator override.' The flow is an atomic transaction group — once the contract holds enough ALGO, a trigger swaps 90%¹⁵ of its balance for STEAK on Tinyman v2 and forwards the STEAK to BNFIRE in the same group, so the swap and the burn either both happen or neither does. The project's framing is that this is 'an engine, not a budget': deflation scales with the pool's commission rather than a fixed treasury allocation.

Two nuances are visible on-chain. The contract's own counters show 41 burn cycles, about 266.8 ALGO swapped and roughly 33,500 STEAK burned through it since May — a small slice of the 1.9 million¹⁶ total, meaning the bulk of the historical burn predates the automation. And each cycle is initiated by a call from the validator's manager account (PAWG3I..., per Réti's dashboard), so the mechanism is automated but not fully self-executing: a keeper transaction starts every burn, and the contract account currently holds about 2.65 ALGO awaiting the next threshold.

The project says the contract cannot be upgraded or deleted and that its only mutable parameter — the Tinyman swap target — sits behind a 3¹⁷-of-5 timelocked migration multisig with a 30¹⁸-day on-chain notice period. The contract's global state confirms a migration authority address is set, with the proposed-migration fields currently zeroed — an inactive escape hatch consistent with the whitepaper's description, but evidence that 'immutable' has one defined exception rather than none.

The market reality

STEAK trades on Tinyman¹⁹ as a verified listing, and the live pool data is thin: about $3,916 of liquidity, a price near $0.000656, 24-hour volume of roughly $1.88 and seven-day volume of about $53.46. The site's own swap calculator shows a 0.66% price impact on a 10-ALGO swap — roughly eighty cents — after the AMM's 0.30% LP fee, which is what a constant-product pool of this depth does to trades. On Pact, STEAK appears in several pairs, all reading zero TVL in the listing snapshot. The token's burn engine is real; the market for it is not yet meaningfully liquid.

What the chain actually shows

The project's entire pitch is verifiability — after the rebuild, in its own words: 'The chain is the source of truth. This site just renders it.' Checking the asset's configuration against the mainnet indexer confirms part of the claim and complicates another. Clawback and freeze are indeed null (zero address), matching the site's 'clawback / freeze nuked' framing — no party can confiscate or freeze balances, and total supply is fixed at 17 million²⁰. But the manager role is still set to the creator address, not zeroed, so the creator retains reconfiguration authority over the asset's roles — not over supply, which cannot change. Full immutability of the asset's configuration is therefore not quite what the marketing language suggests.

Provenance is worth noting too. The token was minted from an address that has created 2,853 assets — a high-volume asset factory — and the ASA's url field points to rug.ninja, the fair-launch launchpad the project says it chose deliberately: no insider round, no team allocation, the team buying at the same price as everyone else. That framing is consistent with what the ledger shows, including the creator still holding zero STEAK.

The honest caveats

The store-of-value claim rests on two unshipped pillars. The treasury-backed floor — letting holders burn STEAK for a pro-rata share of an accumulated reserve — is 'still being designed' per the project's own FAQ, with an audit promised before it ships; the membership-tier NFT layer is likewise planned, not live. Until then, the price floor is narrative. The economics are also self-referential: delegators earn STEAK for staking ALGO, and the burn spends ALGO to buy STEAK, so the flywheel depends on pool growth — which simultaneously dilutes the per-staker payout noted above. The project acknowledges both dynamics on its own pages.

The project's own risk language is unusually direct: the whitepaper warns 'The price can go to zero,' and the terms page states 'STEAK is a cryptocurrency token; cryptocurrencies are volatile and can lose all of their value.' The pool depth above is the concrete reason that language matters — in a pool of roughly $3,900, even modest selling moves the price materially.

Finally, several verification gaps surfaced while researching this piece. The whitepaper points to a public repository with audited TEAL artifacts, but GitHub searches under the project's name found no such repository — the only match was an unrelated third-party Discord bot. The Discord invite linked in the site footer no longer resolves. The transparency page itself was showing the AutoBurn contract's live-state widget as 'temporarily unavailable.' And the 1.2M²¹ STEAK operator lockup — 7.05%²² of supply, locked until January 5, 2030 in a timelock vault (app 3551301332²³) that does exist on-chain — is displayed with a 'live balance verified on chain' checkmark, but that balance could not be independently confirmed with the tools used here. None of these gaps disprove the mechanism; they are simply places where a reader who wants to verify everything the site asks them to verify will have to dig further on their own.