VALUE RECOVERY INFRASTRUCTURE FOR TOKENS

Your token, backed from the first block.

Launch with reserves beneath the token, optional escrow for project runway, and end of life rules defined before trading. Backing can grow while the token is active.

TOKEN LIFECYCLE ON-CHAIN
Market value and recoverable value across a token lifecycleThe recoverable amount per token, counted in the base asset, climbs in steps as fees and reserve mints add to it, and never falls.END OF LIFEMARKET VALUERECOVERABLE VALUE
LaunchBuildTradeEnd of life

The recoverable amount per token, counted in the base asset, climbs in steps as fees and reserve mints add to it, and never falls.

SCROLL THROUGH THE LIFECYCLE

Built for Solana. Defined before trading.

An isolated treasury from the first blockContract-owned liquidity, not a team walletAn escrow schedule or none, fixed at launch

THE PROBLEM

Launching is easy. Protecting holders afterward is not.

01Liquidity can disappear.

If liquidity is unlocked or controlled by the team, it can be removed, leaving holders with thin or unusable markets.

02Teams can stop building.

A project can raise capital, release funds, then slow down or abandon development. Holders have no built-in way to force delivery.

03Holders can get stuck.

When a project dies, the token may keep trading, but its liquidity pools get drained within minutes, with no defined path to return value to holders.

THE CONTRACT BOUNDARY

The fewer ways to cheat, the less trust you need.

See which decisions the team, Transmuter, and the protocol are actually permitted to make.

Explore the contract constraints
ActionTeamTransmuterProtocol
Move the treasuryNoNoProtocol-defined end of life
Pull scheduled escrow at willNoNoRules and governance
Release the next team trancheNo unilateral early releaseNoSchedule or holder vote
Force a holder payout amountNoNoOn-chain ratio
Trigger end of life unilaterallyNoNoHolder vote and safeguards
Rewrite the escrow scheduleNoNoFixed at launch

The current design is described in the docs and is being revised. A liquidation halt can stop an end of life, and cannot force one. It cannot move a treasury, mint a token, alter a balance, or block a redemption.

THE FLOW

Scroll through the token lifecycle.

Scroll from launch to end of life and see what changes at each stage.

01
LAUNCHToken starts live
02
BUILDScheduled tranches release
03
TRADEBacking grows with activity
04
END OF LIFEDefined ending
RESERVEIsolated treasury
MARKET DEPTHContract-owned liquidity
RUNWAYOptional escrow
Unlocks automaticallyPauseUnpauseAdvance next tranche
Transactions feed reserves
Mint to Scale adds backing
RESERVE ASSETcSOL / cBTC
OPTIONALGold variant
TreasuryLiquidityUnspent escrow
Holders redeem pro rata
01

LAUNCH

The token starts with something underneath it.

An isolated treasury and contract-owned liquidity sit beneath the token from launch. Escrow is optional; if used, its schedule is fixed before trading.

02

BUILD

Runway releases automatically.

If escrow is used, tranches unlock on schedule without a vote. Holders can pause, resume or advance the next tranche, but nobody can rewrite the schedule.

03

TRADE

Activity leaves something behind.

Transactions and Mint to Scale add backing while the token is active. A minter pays into the reserve and receives tokens in return.

04

END OF LIFE

The ending is already written.

After governance approves end of life, liquidity and unspent escrow consolidate into the treasury, unsold and unvested tokens burn, and holders redeem their pro rata share.

THE LAYER UNDERNEATH

A reserve asset needs its own contingency.

01 · PROJECT LAYEREOL token

Backed by its own isolated treasury.

02 · RESERVE LAYERcSOL / cBTC

Backed by its base asset and strengthened across the protocol.

03 · CONTINGENCY LAYERTokenized gold

Optional, where the project chooses the gold variant: a secondary contingency if the base asset itself fails.

Each project keeps its own treasury. Beneath it, the cToken layer adds a shared reserve asset. Projects can choose a variant with gold as a secondary contingency for base-asset failure.

TWO WAYS IN

Launch with it. Or integrate it.

A · NATIVE

Launch with Transmuter.

Launch with the full Transmuter stack already configured.

Open the launchpad →
B · INTEGRATED

Bring your own launch stack.

Launch platforms can add Transmuter rails beneath their own product.

For launch platforms →
TRANSMUTER PROTOCOLRESERVES · ESCROW · LIQUIDITY · END OF LIFE
ReservesGoverned escrowContract-owned liquidityEnd of life

FAQ

The essentials, answered directly.

The short version before you go deeper.

Transmuter is value recovery infrastructure for tokens on Solana. An isolated treasury and contract-owned liquidity sit beneath each token, with end of life rules defined before trading.

Escrow is optional. If used, its schedule is fixed before trading.

No. We cannot move a project's treasury, take its reserves, mint its token, alter holder balances, block redemptions or force an end of life.

At the financial governance layer, the founder safeguard is cancel-only: it can stop an end of life, but it cannot create or accelerate one. The system is deliberately designed so that intervention cannot become a route into user funds.

A team cannot withdraw its project’s treasury at will. If configured, escrow unlocks on the schedule fixed before launch, by time or by milestone, without a vote for each payment.

If the work defined in a milestone is not delivered, holders can pause the escrow. Holders can also resume it or advance the next tranche, without rewriting the schedule. Paused escrow stays in escrow until it is released or joins the treasury at end of life.

Transmuter does not stop projects from failing, vet teams or make statements about token price. Reserves are worth what their assets are worth.

Escrow is optional and can be set to zero at launch. Governance cannot rewrite an escrow schedule once trading begins.

BETA TESTING

Launch with the ending already written.

Beta testing is open.