nozywallet.org

LEONINE DAO

Shielded Zebrad + lightwalletd Shielded Zebrad

Public lightwalletd for NozyWallet. Keys stay on your device. JSON-RPC is localhost only.

01 · Is it running

Zebrad

Checking…

Blocks: —
Chain: —

Lightwalletd

Checking…

Wallet server: lwd.nozywallet.org:443
Height: —

Companion API

Not deployed

Host: api.nozywallet.org
Status file: —

02 · What LEONINE DAO operates

Public compact sync

Light wallets compact-sync at lwd.nozywallet.org:443. Keys stay on your device. This is the mass-user door — same idea as other public lightwalletds.

LWD: lwd.nozywallet.org:443
JSON-RPC: localhost only (not public)
Operator API: api.nozywallet.org — one LEONINE wallet, not a shared store backend, not merchant settlement
Shielded invoices (ZekuraPay): detect on this node; settle to the merchant’s Nozy UA

Local path

Desktop and CLI stay first-class. Run NozyWallet on your PC with your own Zebrad if you want keys and the node under your control.

Product downloads and docs live on nozywallet.com.

03 · Builders

Public lightwalletd

When Lightwalletd above shows Online (not Syncing), other light clients may compact-sync at lwd.nozywallet.org:443. Beta targets are on SLA.

gRPC over TLS on 443
JSON-RPC stays localhost (not public)
LEONINE DAO sees IP and sync/submit timing

NozyWallet in your stack

We advise collaborators on wallet development and on putting NozyWallet (Local or Hosted) into their product or ops. That is relationship-based help, not an open consultancy.

Ask by email Lowo88@leoninedao.org or on X @LeonineDao.

Not project hosting

We do not host other people’s apps, sites, or companion APIs on this machine, and we do not run another wallet’s keys here. No multi-tenant app hosting.

Need your own node? Use Desktop / CLI (Local) or stand up Zebrad yourself.

04 · Trust

Do not depend on this box

Zcash privacy on-chain does not require believing LEONINE. Amounts stay shielded (Orchard / Ironwood) whether you use our node or yours. A stack you cannot leave is not security — it is a dependent.

Public compact sync at lwd.nozywallet.org:443 keeps keys on your device. We can still see IP and when you sync or send. That is metadata, not your amount, and it is not unlinkable. We will not pretend otherwise.

api.nozywallet.org is one LEONINE operator wallet — not a public vault, not merchant settlement, and not other people’s keys. Merchants who take shielded ZEC on this infra use invoice watch (ZekuraPay) against the public node; spending stays in their Nozy. We will not grow a bureau of users who cannot walk away from this VPS. Desktop and CLI with your own Zebrad stay first-class. Use them if you do not want to trust this machine at all.

05 · Service Level Agreement

What we promise — and how you can check

Without an SLA, people assume a joint hosted wallet, public JSON-RPC, or that P1 node-down is the same as a stale status file. It is not.

Public LWD path (lwd.nozywallet.org:443):

P1 (LWD unusable or Online but >1000 blocks behind): restore in 48h (provider/network excluded)
Availability target: ≥ 99.0% of monthly 5-minute samples with Zebrad Online (not Syncing) and LWD ok — status.json
Operator API is a separate target (99.5%). Downtime there does not count as public LWD failure.
Support: support.team@nozywallet.com — every issue is high priority; we respond within 72 hours

Community / beta, one VPS, no credits. Full tables, exclusions, and “what this is not”: SLA page.

Read the SLA status.json

06 · Learn Zcash

ZecHub wiki

Independent community docs for Zcash — shielded pools, running a node, and how the network works. Start there if you are new to ZEC.

Open ZecHub.wiki NozyWallet product