Bezant - private digital cash, built for users.
This is a public draft. It states what Bezant is, what its protocol commits to, and where the project currently stands. It is not a marketing document. Numbers and design choices listed below are the ones the protocol actually ships.
1. What is Bezant
Bezant is a private, fair-launch, 100% Proof-of-Work blockchain. It ships as a single desktop application - Bezant App - that bundles a full node, a non-custodial wallet, a multi-algorithm miner, a Mining Hub, a Pool Hub, a local explorer and merchant tooling, in one window.
Bezant is privacy-first by construction. Amounts on the chain are confidential. Addresses are not first-class objects: the network surfaces what is genuinely public on chain - block headers, kernel counts, per-algorithm difficulty - and nothing more.
2. Why private digital cash still matters
Most digital payment rails today are surveillance rails. Every transaction has a real-world identity attached, a custodial intermediary in the middle, and a reversal channel that can freeze funds without due process. That is fine for some use cases. It is not fine for cash.
Bezant is for the parts of life where cash has always made sense: paying a friend, paying a small business, holding a personal balance without a counterparty, and accepting payment as a merchant without giving a third party the power to reverse it. The protocol takes no cut from any of that.
3. Fair launch principles
The Bezant network starts from zero - for everyone, at the same time.
- 0 premine. No supply is allocated to the team before the network starts.
- 0 ICO. No tokens are sold ahead of launch. There is no investor allocation.
- 0 mandatory developer tax. The protocol does not redirect any fraction of block rewards or transaction fees to the project, the maintainers or any foundation.
- Network fees go to miners and pools. Always. The project does not take a cut.
4. Monetary policy
| Asymptotic max supply | 21 000 000 BZT |
|---|---|
| Block time | 60 seconds |
| Halving curve | Geometric, era-based |
| Smallest unit | BZT base unit (8 decimals) |
| Premine / ICO / mandatory dev tax | 0 / 0 / 0 |
| Where fees go | Miners and pools only |
Full breakdown: monetary policy page.
5. Proof-of-Work model
Bezant uses a multi-algorithm Proof of Work so participation is not gated by specialized hardware. The protocol target distribution is:
| RandomX (CPU) | 40 % |
|---|---|
| ProgPow (GPU) | 55 % |
| Heavy Mining | 5 % |
The target balance is 40 / 55 / 5. The current devnet validates the CPU and GPU paths first; Heavy Mining is reserved for the full network target and ships as a dedicated audited release.
6. Privacy-first wallet model
Transactions hide amounts cryptographically. The chain does not publish sender or receiver addresses in the way most ledgers do. From a third party's point of view, you see block headers and kernel counts. You do not see Bob's balance.
The wallet inherits that posture and adds three things.
- Non-custodial. The seed is created and held on your machine. No remote service stores keys.
- Argon2id seed encryption. Memory-hard, modern key-derivation function. Single backup file. Never shown twice.
- Receive routes. Tor v3 hidden service, HTTPS endpoint, or file slate exchange. You pick the route, the wallet handles the rest.
7. Security model
Bezant App talks to the world through its own local REST API (loopback, with a per-instance secret). External tools - plugins, SDKs, merchant backends - connect via a scoped API key issued from inside Bezant App. Plugins never hold funds. The seed never leaves Bezant App.
8. Send Max - sweep balance
Two send modes are documented for the wallet:
| Exact amount | Recipient receives the amount you type |
|---|---|
| Send Max | Recipient receives Σ inputs − fees |
Send Max is documented as a planned feature today. The wallet backend is not connected on devnet.
9. Bezant App vision
The product is the desktop application, not the website. Bezant App bundles:
- Full node
- Wallet
- Miner (RandomX + ProgPow)
- Mining Hub - discover pools, fees, reliability
- Pool Hub - run your own pool from this same window
- Local network / explorer status
- API keys for plugins and merchant backends
- Merchant tools - scoped, opt-in
The website exists to distribute the installer, to host the docs and SDKs, and to coordinate with builders. It does not hold funds, it does not custody seeds, and it does not run a wallet.
10. Developer and merchant integrations
Builders interact with Bezant by talking to a local Bezant App instance, not to a remote service. The integration surface is:
- Local REST API on 127.0.0.1.
- Scoped API keys issued from inside Bezant App.
- SDKs for the typed clients (planned).
- Webhooks for confirmed credits (planned).
- WordPress / WooCommerce plugin (planned). The plugin holds no funds and never sees the seed.
- Optional public access via Cloudflare Tunnel (planned, entirely opt-in).
11. Future commerce layer
The longer-term direction is a clean commerce layer: seller stores, product catalog, shipping integrations, optional escrow with delivery confirmation, and optional fiat rails. Details on the commerce page.
The economic model stays simple:
- The Bezant protocol takes no cut.
- Network fees go to miners and pools.
- BZT direct payments can carry zero platform fee.
- Managed services - shipping automation, escrow, fiat bridges - may charge transparent service fees.
12. Risks and current status
Known limitations of this draft :
- The wallet binary is built but not wired to the live devnet node.
- Mining is opt-in and not started by default.
- The Mining Hub, Pool Hub, and merchant API are described above but not yet implemented.
- The commerce layer is direction, not a deliverable.
- Numbers in this document are protocol commitments; service-layer numbers (fees, rates) will be disclosed on each managed service when launched.