LEZ 0.3 testnet

The private wallet for Logos.

Public and private accounts, approvals that say exactly what they do, and the SDK your Basecamp app uses to ask for them. Keys never leave the wallet.

Install the walletBuild an app
Wallet home: the balance in LGO, Send, Receive and Test LGO, tokens and activity
Approvals

Every approval says what it does.

Decoded from the exact message being signed, never from what the app says it does.

  • Who is asking: the app, its name checked by Basecamp
  • What moves: the amount, the asset and the full destination
  • Which program: source-verified or flagged, and whether it can still change
An app's request in the wallet: Send 0.000000005 LGO to Savings, with the network fee, the account it comes from and Reject / Approve
Privacy

Private by default.

Private balances only you can see. Private sends are proved on your own machine, before anything leaves it.

  • As many public and private accounts as you like
  • Receive privately with a code that reveals nothing about your balance
  • Apps can read a private balance only if you tick it, and never spend
Receive privately: the private account's receive code as a QR, which reveals nothing about the balance
Outcomes

Included isn't done.

LEZ includes failed transactions too. Logos Kit checks the effect against chain state before it says success.

  • Success only when the balances moved the way you approved
  • A slow network keeps the send pending, never silently failed
  • Every step on screen, with the block it landed in
Sending privately: a ring with the elapsed time and the steps Approved, Preparing, Proving on this device, Signing, Waiting for a block
For Basecamp builders

A wallet in your app in ten minutes.

Start from the template: connect, balances, test funds in the flow and a receipt, already wired. Your app asks; the wallet shows the user exactly what they approve.

$
nix flake init -t github:logos-kit/logos-kit#dapp
import "LogosKit"

LogosKit { id: kit; visible: root.visible }

// The wallet asks the user which account to share.
kit.api.connect({ accountKinds: ["public", "private"] })
    .then(function (s) { account = s.accounts[0].address })

// The user approves in the wallet. You get a handle and follow it.
// Amounts are lepta: parseUnits("0.5", 9) is half an LGO.
kit.api.transfer(account, to, "500000000").then(function (r) {
    kit.api.watchTransaction(r.handle, function (s) {
        if (s.lifecycle === "included")
            done = s.outcome === "success"   // proved from chain state
    })
})
Start the quickstartEvery QML callSend a transaction

Tried it? Leave a testimonial.

One sentence about what you used it for, stored on the Logos testnet. It helps this independent project's λPrize entry.

How it works
The Testimonials app: say what you use it for, with suggestions

Questions

Which network does it use?
The official LEZ testnet 0.3 (https://testnet.lez.logos.co, LEZ v0.3.0). It is the default in the wallet, the CLI and the SDK. Testnets only: tokens have no value. Networks
What is LGO?
LOGOS, the native token, written LGO. 1 LGO is 10⁹ lepta, its smallest unit. The wallet shows LGO; apps and the SDK pass lepta, so nothing is ever rounded.
How do I get test LGO?
Press Test LGO in the wallet: 1 LGO, once an hour per account. Apps can open the same sheet with requestFunds. A private account is funded through a public one, then shielded.
Can an app see my private balance?
Only if you tick that account and allow it when you connect. Even then it can read, never spend: every transaction still needs your approval in the wallet.
Is it safe to use?
Keys are encrypted at rest and never leave the wallet; approvals live in the wallet's engine, not in apps. It is unaudited and runs on testnets only. Security model
Rust engineQt / QMLTypeScript client@logos-kit on npmNix buildsRISC Zero proofs