From click to chain
Every Kadia app follows the same path. Each step is something you can check.
- The app reads the chainPools, markets and your positions come from an Ergo node and the kadia-explorer indexer, through the same site that serves the app. Run your own and point the app at them in Settings.
- You choose a walletNautilus in the browser, or a mobile wallet through ErgoPay. Nothing connects until you pick one.
- The app builds the transactionIn your browser, from the chain's own boxes. The lending builder is a pinned WebAssembly module whose hash the app checks before running it.
- You review it in plain wordsWhat you send, what you get, what is a fee and what stays yours, and why anything would be refused.
- Your wallet signsKeys never leave the wallet. The app checks that the signed transaction is the one it built before sending it.
- The contracts enforce the restFloors, refunds, deposits and liquidations are rules in the contracts, not promises from this website.
Run it yourself
The apps are static files. They work under any address, from your own machine or a copy of the site, against your own node and indexer. Builds are reproducible, and each build lists the hash of every file it contains, so you can check what you're running.
What isn't true yet
Nothing is live. Signing is turned off in today's builds, and the contracts are in review, not audited. The roadmap tracks what changes.