Vestige Labs to shut its Algorand swap platform on December 31, 2026
Vestige Labs will take its Algorand swap aggregator, frontend and API offline on December 31, 2026, saying chain-wide volume has not covered running costs. Vaulted assets stay in their contracts and Vestige says legacy.vestige.fi stays up; VEST holders get a burn, not a payout.

Vestige Labs will take its Algorand trading and data platform offline on December 31, 2026. The post on its own account1 on November 14 named the vestige.fi2 frontend, the API, the swap aggregator and 'all related services✓1'. It gave the reason: Algorand-wide trading volume has not covered the cost of running Vestige for the past year. The part addressed to users was narrower than the scope. Assets in a personal wallet are unaffected, and vaulted assets stay reachable through legacy.vestige.fi3.
What the deadline covers
The platform being switched off began as TinyChart, a tracker for Algorand Standard Assets. It grew into a swap aggregator and DeFi explorer. Algorand Ventures announced an investment in Vestige Labs in December 2023. The Algorand Foundation's Algoland campaign later named Vestige among the chain's swap venues, alongside Tinyman and Haystack.
Its counters are the plainest measure of what it did. Read on November 15, a day after the announcement, they showed 1,516,235✓2 swaps and USDC 209,125,638✓3 of cumulative volume. In our August profile of the router, the same counters read 1,478,882✓4 swaps and $207,326,215✓5, and that article recorded each swap in the tally as an Algorand transaction the service routed.
The announcement names its audiences directly: builders and integrators whose apps, bots or dashboards pull from the Vestige API, users, and VEST holders. It does not say whether the Launchpad, the rug.ninja coin launcher or the on-chain asset metadata manager fall inside 'all related services', so anyone with assets in those products has no statement either way.
1,336 vaults, and the one page that reaches them
Vestige's vaults are time-locked escrow accounts built on paired Manager and Vault contracts, as its documentation4 describes them. The Manager contract sets fees and keeps a queryable list of every vault launched. Each vault contract holds the assets in escrow and releases them only when its conditions are met. Vestige's API enumerates 1,336 of them. Each entry carries:
- a deployer
- a single claimer address
- an asset
- a set of release steps
- a next release time
The recent entries are project locks rather than retail deposits, named for Sparky, Criptomedia, Algohood, Cents and Steak Pool.
These are the positions the announcement had to carve out, and the carve-out is doing real work. A release is executed by the contract, not by a server. One Cents vault took in its tokens and returned the full balance to its creator by inner transfer on May 19, 2026, with no ALGO leaving the escrow. Another still holds its assets with a release two years away. The terms do not change when Vestige's machines stop. What a holder loses is the page that builds the claim transaction, which is why the notice had to promise one.
legacy.vestige.fi's vault list5 is that page, and it loads scripts from the same Vestige Labs host that serves the API going dark on December 31. The company has not said what that host does afterwards. A vault holder should open their own vault there now, claim anything already unlocked while the page is known to work, and note the vault's contract ID for any later release.
Vestige's own protocol index already lists its vault product as inactive.
A burn, not a rescue, for VEST holders
All remaining VEST in the treasury will be burned, together with the VEST liquidity tokens the company holds, and that had not happened by November 15. The treasury account held 57,719,144.9 VEST that day, 57.7 percent of the token's 100,000,000 supply and the same share the account held in August.
That account signs with a single key. It is also VEST's creator, manager and reserve. One reassurance comes from the token rather than the team: the freeze and clawback roles are empty and, in the asset record's wording, can never be set again. Nobody, the team included, can freeze or seize VEST from a holder's wallet. What the burn does is shrink supply. It returns nothing to anyone holding the token.
The same key is the only manager on the contract other projects use to put asset descriptions, social links and supply labels on chain. No successor is named for that registry.
Integrators have a migration to run
The announcement gives anyone pulling from the Vestige API until December 31, after which, it says, all endpoints stop responding. Vestige's API documentation6 still sends developers to a free endpoint described as unlimited, protected by Cloudflare and cached for a minute. That address returned a server error on November 15, and the same error was recorded in August. The separate host that serves the live API answered normally. Test a migration against the host that responds, not the documentation page that points elsewhere.
Why: the arithmetic behind the reason
- Swaps routed, lifetime: 1,516,235 (Vestige's own counter, 15 Nov 2026).
- Volume routed, lifetime: 209,125,638 USD (Vestige's own counter, 15 Nov 2026).
- VEST in the treasury, to burn: 57,719,144.9 VEST (On chain, 15 Nov 2026; 57.7% of supply).
- Algorand DEX volume, last 24h: 1,056,771 USD (DefiLlama, 15 Nov 2026).
The counters make the stated cause easy to check. From $207,326,215✓6 of routed volume on August 9 to $209,125,638 on November 15 is about $1.8 million in roughly three months. From 1,478,882✓7 swaps to 1,516,235✓8 is about 37,000, on a router that charges no fee of its own. In the 24 hours to November 15, every DEX DefiLlama tracks on Algorand7 traded $1,056,771, and $10,938,070 over 30 days. Three months of Vestige's routing were worth less than two days of the market it routed into.
The reason is the team's own. What the record supports is that the model was thin: a router that takes no cut from swaps needs volume it never saw.
What the thread says, and what a reader can do
A post on r/AlgorandOfficial reproduced the announcement in full, with a note from its author that they are not affiliated with Vestige and know no further details. Comments ran from gratitude for the tool to one asking what to convert ALGO into, one worrying about vaults (answered by quoting the legacy frontend line), and several recommending Haystack instead. Others read the closure as a verdict on Algorand's DeFi market rather than on one product. The thread's last activity came on the evening of November 14.
What to do depends on where you sit. Vault holders should open their vault on the legacy page, claim anything already unlocked, and note the vault's contract ID. Vestige says that page stays up, though it currently loads its data from the API being switched off; the assets themselves are held by the vault's contract, which releases them on its own schedule with or without the site. VEST holders have nothing to claim: the burn shrinks supply, it does not buy anyone out. Traders have until December 31, and the thread's answer for a successor is Haystack8, which commenters rate on price accuracy and integrations.
8 figures in this story are checked.See every check
Sources
- 1X post by Vestige Labs x.com↩
- 2vestige.fi vestige.fi↩
- 3legacy.vestige.fi legacy.vestige.fi↩
- 4Vault | Vestige Docs about.vestige.fi↩
- 5Vaults – Vestige legacy.vestige.fi↩
- 6Vestige's API documentation about.vestige.fi↩
- 7api.llama.fi/overview/dexs/Algorand api.llama.fi↩
- 8Haystack | Swap hay.app↩