THE RULES
1 · Using it means agreeing
Opening or using any part of LIQUA means you agree to these rules. That covers this site, the relayer API, the contracts at the addresses in shared/deployment.json, and the software around them. If you do not agree, do not use it.
2 · What the exchange is
A hybrid order-book DEX. Orders are signed off-chain and settled on-chain by smart contracts, so nobody takes custody of your tokens. A relayer lists orders to make the book easy to browse. It cannot move anything of yours. Only a transaction signed and sent by you, or by someone taking your order, moves tokens. The exchange has not opened, and it does not run on the Liqua chain yet.
Opening waits on work that has not shipped. Settlement has to move onto the Liqua chain and read through the RPC. Bridge deposits have to arrive as tradeable assets. An outside audit and a bug bounty come before mainnet. No date is set.
This website is a window onto the contracts. Most of it runs inside your browser. Settlement happens on-chain.
3 · Experimental, all the way down
LIQUA comes "as is" and "as available". It may hide bugs, security holes or design mistakes that could wipe out whatever you put in, for good. Once a contract is deployed, nobody on the project can pause it or roll it back. You take that risk yourself.
What runs today is a testnet. Test tokens carry no value, no peg and no listing. Use it to learn and to build.
4 · No advice, no offer
Nothing on this site, in the docs, or in anything the project posts is financial or trading advice. Nothing here is a recommendation from LIQUA, its contributors or anyone connected to them. No page offers to sell you tokens, and no page promises you will get anything back. Judging a decision is your job, every time.
5 · No guarantees
As far as the law allows, LIQUA and its contributors make no promises, stated or implied. Not that it works. Not that it suits your purpose. Not that it steers clear of anyone's rights. You use it with every risk resting on you.
LIQUA, its contributors, partners, agents and licensors are never liable for indirect, incidental, special, consequential or punitive losses that come from using it. That covers missed gains and lost data. It holds even if someone warned that it could happen.
6 · Your wallet, your job
LIQUA never holds your private keys, your recovery phrase or your tokens. Everything is signed by a wallet you control, such as MetaMask or a hardware wallet. Nobody on the project can recover, reset, freeze or seize anything inside it.
Lose your recovery phrase, sign something malicious, or send to the wrong address, and it is gone. No one can undo it.
7 · Where the design bends
Two trade-offs sit in the design, and neither is hidden.
- One relayer hosts the book. It can hide or skip orders. It cannot touch your tokens.
- A mirror keeper key can live on the host machine. The relayer may run a wallet that signs orders, holding its own tokens and permits. If you host, guard that key like cash.
8 · Play fair
Do not:
- Use LIQUA to break any law that applies to you, sanctions and anti-money-laundering rules included.
- Attack, exploit or jam the contracts or the relayer.
- Post anything in the lobby chat that is illegal, harassing or threatening.
- Try to get into anyone else's wallet, session or data.
Reporting a vulnerability responsibly is welcome, through a bug bounty once one exists. Nothing on this page stands in the way of that.
9 · What can change
The off-chain parts can be changed, paused or switched off at any moment, without warning. That means this site and the relayer. Deployed contracts cannot be edited by anyone. A newer build would live at new addresses, and you choose whether to use it.
10 · These rules can change too
The rules may get updated. The date line at the top shows the latest edit. Keep using LIQUA after an update and you agree to the new version. Big changes get announced on the project's official channels.
11 · Which law applies
[Still open. A lawyer fills this in: the governing law of [JURISDICTION], with disputes settled by [ARBITRATION FORUM] in [VENUE]. This has to be finished before any public launch.]
12 · Reaching the project
Project channels, a security contact and an abuse contact are announced before mainnet. Until then there is no support desk.