Token and contracts

Contracts overview

$LIQTERM exists on chain today. The contracts that will use it to grant access — staking, burning, the bonding curve phase and the buyback vault — are designed but none of them are deployed. These pages describe that design and mark the status of every part of it.

How to read the status badges

BadgeMeans
Live Exists now and can be verified independently — usually on the block explorer.
Planned The design is decided, but no contract implements it yet. It can still change.
Undecided Deliberately not fixed. Usually a number that depends on market conditions at the time.
Planned is not a promise

Anything marked Planned may change, be delayed, or not ship. Nothing on these pages is an offer, a guarantee of delivery, or financial advice.

Where things stand

ComponentStatusPage
$LIQTERM tokenLive$LIQTERM
Access keysLiveAccess and licence keys
Bonding curve phase contractPlannedBonding curve phase
Licence control contractPlannedLicence control
Buyback vaultPlannedBuyback vault
Wallet login in the appPlannedAccess and licence keys
What “Planned” covers right now

Two of those rows have moved further than the word suggests, and it is worth being exact about how far. The bonding curve phase contract is written and tested — it runs on a local throwaway chain with its own test suite — and wallet login is built into the app and the API behind a switch that is off. Neither is deployed to any network, neither is reachable by anyone, and both can still change. They stay marked Planned until they are live, because that is the only distinction that matters to somebody deciding whether to rely on them.

Why access keys came first

Access is granted by a key today rather than by an on-chain position, and that ordering is deliberate. While the token is small, buying enough of it to unlock the terminal would move the price against the buyer — the fee would be unpredictable and mostly slippage.

So the sequence is: run access on keys, let the market deepen, and move the paying tiers on chain once that can be done without the purchase itself distorting the cost. The key system is designed to carry over — a key binds to a device now, and the same binding moves to a wallet address when wallet login arrives.

Two contracts, kept apart

The bonding curve phase is handled by its own contract, separate from the licence control contract. They have different lifetimes: the curve phase is a one-time window that ends at graduation and then only needs to release what it holds, while licence control is meant to run indefinitely.

Keeping them separate means the one-time contract can be simple and finish its job, instead of being carried forever inside the contract that everything else depends on.

Verify it yourself

Do not take the token details here on trust. The contract address is published on the home page and can be inspected on RobinScan.

Beware of lookalike explorers

Use robin.etherscan.io, which is Etherscan’s own subdomain. Several similarly named community sites exist on other domains and are unaffiliated with Etherscan. New chains attract impersonation; check the domain before trusting what it shows you.