Try the testnet prototype

Testnet prototype

Kadia DEX runs on Ergo testnet for testing: not audited, and not on mainnet. Every page says “TESTNET: test coins, no real value”. Nothing here involves real funds. The markets’ ids are in the testnet DEX record.

What you’ll need

• An Ergo testnet wallet in your browser. Nautilus publishes separate testnet builds: get nautilus-testnet-chrome.zip or nautilus-testnet-firefox.zip from Nautilus’s GitHub releases.
  • Chrome: turn on Developer mode in chrome://extensions, then load the unzipped folder.
  • Firefox: load it as a temporary add-on from about:debugging.
  • Use a new wallet made for testing, never one that holds mainnet funds.
  • Keep only one Nautilus on. If you also have the mainnet build installed, turn it off while you test, or use a separate browser profile. With both on, they block each other: the connect waits and no Nautilus window opens. Turn one off, or use a separate browser profile, then reload the page.
• ERG on testnet, and the test tokens tUSE, tBTC, tADA, tETH, tBNB, tDOGE, tFIRO, tXMR, tLTC and tSOL. None of it has value. See Get test coins.
• Kadia on testnet. Use the hosted prototype (pick Testnet in the switch at the top of the page). Most testers should start there. Running it on your own computer needs a DEX service and a signing build; see Run Kadia on your computer.

What’s real and what isn’t

	Status
DEX	Live on testnet, with 11 markets: ERG against each of the ten test tokens (tUSE, tBTC, tADA, tETH, tBNB, tDOGE, tFIRO, tXMR, tLTC and tSOL), plus tUSE / tBTC. You can swap either way, place limit, DCA, grid and route orders, add liquidity (with both assets, or with ERG only as a zap on the ERG markets) and remove it, and create a pool. The hosted prototype is a signing build: you approve each transaction in your wallet, and it’s sent on testnet. Signing builds never sign on mainnet.
Lending	Not live. Lending v1 is in development, and the hosted lending app has no markets connected yet.
Explorer	Reads Ergo mainnet only, for now. It isn’t part of the testnet prototype.
Site and docs	Real.
Wallet	Nautilus (EIP-12) in your browser, or ErgoPay with a wallet on your phone. Kadia never asks for a seed phrase.
Not live yet	The keep box, maker and firm vaults, the Kadia oracle network’s feeds, lending v1, and anything on mainnet.

• Review screen: every action ends there. It shows what you send, what you get, which lines are fees and what stays yours, such as the rent reserve or a lending deposit.

• Approving a transaction: in the signing build, you approve it in your wallet. Before anything is sent, Kadia checks two things. The wallet must have signed exactly the transaction Kadia built. And the site, the node, the DEX service and your wallet must all be on testnet. If anything differs, nothing is sent.

• When the service falls behind the chain, after a reorganisation or for a moment between blocks, the DEX pauses quotes and says so (“The service is catching up with the chain”). Quotes come back by themselves, and a quote or order that meets a just-updated pool is asked again automatically.

• The badges on a market:

  • “Checked by one node (testnet only)”: on testnet one node checks the DEX service’s answers; the full design checks them with two different nodes.
  • “Registry verified” or “Not registry verified”: whether Kadia’s registry admitted the market. Kadia trades only verified ones.
  • “Verified Rosen token” or “Unverified token”: whether a token named like a Rosen token (rs…) is on Rosen’s official list, by its token id.
  • “test”, on a coin’s icon: one of Kadia’s test tokens, matched by its exact id.

• Creating a pool takes two transactions, signed one after the other. The second can take up to about a day (720 blocks) to confirm; until then the pool is pending, not failed.

Reporting a problem

Report problems in the channel your tester invitation came from. Include:

• what you did, step by step;
• what you expected and what happened instead;
• the app (DEX, Lending, Explorer, site) and its address;
• the browser, the wallet and its version;
• any transaction or box id shown;
• a screenshot of the review screen, if there was one.

Security problems: don’t post them publicly. A security contact will be published on the security page. Until then, send them privately to whoever invited you.

Never send your seed phrase, private keys or wallet password to anyone, including Kadia. Nobody from Kadia will ask for them.