Logos KitFAQ
Short answers to the questions people ask first.
No. Logos Kit runs on LEZ testnets and hasn't been audited. Use test funds only.
In the wallet's encrypted vault on your machine (Argon2id and XChaCha20-Poly1305). No app, and no Logos Kit server, ever sees them. See the security model.
It's proved on your own machine with RISC Zero, so your keys never leave it. That takes minutes on a laptop. Public transfers take seconds.
The official LEZ testnet (https://testnet.lez.logos.co, LEZ v0.3.0), by
default in the wallet, the CLI and the SDK.
Details.
LGO is the symbol of LOGOS, the native token. LEZ is the name of the execution zone (the network), not of the token. 1 LGO = 10^9 lepta: the wire, JSON and the SDK use lepta, and the wallet, the apps and the CLI show LGO with up to 9 decimals, nothing rounded. Details.
Logos Kit's own public LEZ 0.3 network (v0.3.0-rc1, real proofs), from
before the official testnet moved to 0.3. It's no longer the default; it stays
listed for wallets that saved it, as a legacy rehearsal network.
Details.
No. The prize counts testimonials on the official LEZ testnet, where the
program is deployed as 5YoH3xjhgeKt2mcJXW7c31bqDNCWWA4CRJxVdvzFvVef.
Not yet. Today @logos-kit/client is Node and transport tooling: typed chain
reads, encoding, and the Basecamp module bridge. It has no browser wallet
connector. It can read the testnet from a browser through Logos Kit's relay,
https://lez-testnet.84.46.247.92.sslip.io, which sends CORS headers (the
official RPC doesn't). A web connect kit (React), React Native, and an embedded passkey
wallet are planned, not shipped.
Your users need a wallet that answers the LWS-0 intents; Logos Kit Wallet is
one. During development you can also test against the conformance fake
(modules/logos_kit_wallet_fake, just conformance <dapp>).
Yes, MIT or Apache-2.0, at github.com/logos-kit/logos-kit.