Start here
Access and licence keys
Today the terminal is opened with an access key. Wallet login and on-chain staking are designed but not deployed — see Licence control for where this is going.
Unlocking the terminal
When you open the app without a key you get the access screen instead of the dashboard.
Enter your key in the form LT-XXXX-XXXX-XXXX and press Unlock.
Lower case and missing hyphens are accepted.
Until a key is accepted the terminal is not loaded at all — no exchange connections, no data requests, nothing to reveal. The access screen is the whole page, not a cover over a running app.
A key binds to the first device that uses it
The first time a key is redeemed it is tied to that device, and from that moment its validity period starts counting. Using the same key somewhere else is refused.
- A time-limited key does not start expiring when it is issued — it starts when it is first used.
- A permanent key never expires but is still bound to one device.
- Clearing your browser storage loses the session. Ask for the key to be re-bound if you need to move device.
Sessions
Redeeming a key exchanges it for a session token that the app stores separately from your settings. That separation is deliberate: a backup file contains your settings, layouts and sounds, but never your licence. Sharing a backup does not share your access, and resetting your settings does not lock you out.
Expiry and revocation
Access ends the moment a key expires or is revoked — not at the end of some cached period. Open data streams are closed with it, and the app returns to the access screen.
That is the expected behaviour when a key has expired or been revoked. It is not a bug and reloading will not restore access.
Wallet login Planned
The binding above is designed to move from a device to a wallet. A key is entered once while a wallet is connected, and from then on that wallet opens the terminal — on any machine, with no key to carry and nothing to lose when browser storage is cleared. This is built but switched off; today a key still binds to a device.
When it is on, three things can open the terminal:
- A key linked to your wallet. The key's own expiry still governs; linking changes where it is held, not how long it lasts.
- A bonding curve stake. The API reads your position on chain. See Bonding curve phase.
- A trial, described below.
Signing is not a transaction and costs no gas. It proves you control the address and nothing else — the text you are asked to sign says so, and you can read it in your wallet before agreeing.
Looking around first Planned
Two ways in without paying anything: 15 minutes with no wallet at all, and one day after signing with a wallet. Each is offered once, permanently — not once a day, not once a week.
The 15-minute look-around has no wallet to count, so it is counted per IP address. The one-day trial is recorded against both the wallet and the IP, and either one having been used already is enough to refuse a new trial.
A trial that is still running can be re-opened from anywhere. Signing out and back in, or moving to another network, hands back the same trial with its original expiry time — never a fresh day. What was sold was a day, not a single sitting.
Neither count works alone. Wallets are free to create, so counting only wallets is not a limit at all. Counting only IP addresses is barely better: switching networks takes seconds on a phone, and one wallet could collect a fresh day every time it moved.
Recording both closes the cheap version of that. A wallet that has spent its trial cannot find a new one by changing address, and a person who has genuinely moved keeps the time they were already given instead of losing it to somebody else’s spent quota.
What it does not catch is a new wallet on a new address — that combination still gets its one trial, and no arrangement of these two counts can tell it apart from a new person. The aim is not to seal the door but to make the cheapest way through cost as much as the honest one. The remaining cost is unchanged: a shared or reassigned address can arrive with its single look-around already spent by somebody else.
The beta channel Live
There are two builds of the same app. app.liqterminal.xyz is the release channel described above. beta.liqterminal.xyz is a separate build that receives changes first, and it has its own door: you sign in with an email address, not a wallet and not a key.
- The beta list is written by hand. Only addresses registered by StellarMom can get in; there is no self-service sign-up.
- No wallet is needed. Nothing on the beta channel reads a wallet, so there is nothing to connect and nothing to sign.
- The session does not expire. It lasts until you sign out. Sign out of all devices works as it always did and deletes every session token you hold.
- Losing beta access is immediate. Revoking an address also closes the sessions already open on it, exactly as revoking a key does.
Signing in asks for a six-digit code, which is mailed to the address you typed and is valid for a few minutes. Five wrong attempts throw that code away and you have to request another.
The screen does not tell you whether an address is on the beta list — the reply is identical either way, and only a registered address actually receives mail. If it answered differently, anyone could learn who the beta testers are by typing addresses into the form.
So if no code arrives, that is the expected outcome for an address that is not on the list. Ask in the VIP channel rather than retrying.
Where access is actually enforced
The app is open source under GPL-3.0, so a screen lock in the client would be meaningless — anyone could remove it and rebuild. The real boundary is the API: requests without a valid session are refused, which is what makes the aggregated liquidation history the thing a copy cannot reproduce.
This is worth understanding because it explains the product honestly: you are not paying for a locked binary, you are getting access to collected data and the work that maintains it.
Getting a key
Keys are issued by StellarMom. During the bonding curve phase, staking $LIQTERM is planned to write permanent access — that window closes when the token graduates. See Bonding curve phase.
Access keys Live · Beta channel, email sign-in Live · Wallet login Planned — built, switched off · Trials Planned — built, switched off · Staking and burn Planned — contract written and tested, not deployed