Node Operation
Single-binary workflow for wallet creation, encrypted key storage, database initialization, P2P networking, transfers, balances, diagnostics, and audit exports.
Protocol facts at a glance
The Remzar whitepaper defines the base protocol: node operation, storage, networking, post-quantum cryptography, Proof of Registry consensus, economics, security boundaries, and roadmap.
Project
Remzar Blockchain
Native Asset
REMZAR / ZAR
Mainnet Start Date
2026-06-26
Consensus
Proof of Registry
Block Cadence
30-Second Slots
Signature Model
ML-DSA-65 Block Attestation
Max Block Size
2 MiB
Maximum Supply
200,000,000 ZAR
Abstract
Remzar is a single-binary, post-quantum-oriented Layer-1 blockchain implemented in Rust. It is designed to make public blockchain operation practical from one executable while preserving bounded validation rules, deterministic block production, local wallet ownership, and built-in auditability.
Remzar replaces energy-race mining with Proof of Registry, a deterministic validator-participation model built around explicit registry membership, validator warmup, quarantine, heartbeat renewal, lease expiry, dead-peer eviction, deterministic leader selection, and failover rounds inside 30-second block slots.
Block batches are committed through Merkle roots and attested with one ML-DSA-65 post-quantum signature per block. This keeps signature verification bounded at the block level instead of turning post-quantum verification into a per-transaction bottleneck. The native asset, REMZAR, has a 200 million ZAR maximum supply and is issued through validator block rewards only.
What the whitepaper covers
The document explains Remzar as a working Layer-1 protocol and implementation, not only as a theoretical proposal.
Proof of Registry
Deterministic validator participation through registry membership, leader scheduling, activation delay, quarantine, heartbeat renewal, lease expiry, and deterministic failover.
Post-Quantum Cryptography
ML-DSA-65 block attestation, ML-KEM-768 roadmap support, Merkle-root batch commitments, BLAKE3-style hashing, and encrypted local wallet storage.
Block Model
30-second block slots, 2-second proposer pacing, bounded failover windows, 2 MiB maximum block size, and 8,192 transactions per block.
Economics
200 million ZAR capped supply, reward-only issuance, rewardless genesis block, no protocol-level premine, and deterministic reward ladder.
Security Boundaries
Defensive limits for malformed payloads, oversized batches, invalid signatures, replay attempts, double-spends, stale blocks, dead peers, and validator unavailability.
Whitepaper structure
The Remzar whitepaper is organized as a full protocol document covering technical design, economics, security, and operational roadmap.
- 1. Introduction
- 2. Design Goals
- 3. Protocol Facts at a Glance
- 4. System Overview
- 5. Cryptographic Stack
- 6. Block Model
- 7. Consensus: Proof of Registry
- 8. Transactions, Accounts, and State
- 9. Peer-to-Peer Networking
- 10. Storage, Logs, and Audit Exports
- 11. Economics and Tokenomics
- 12. Genesis and Initial Distribution
- 13. Performance and Benchmarks
- 14. Security Considerations
- 15. Roadmap
- 16. Conclusion
Download the Remzar whitepaper
Download the full Remzar whitepaper PDF for the complete protocol description, including consensus, cryptography, storage, economics, tokenomics, benchmarks, audit model, and roadmap.
Make sure the file in your GitHub repository is named exactly REMZAR whitepaper.pdf. The link on this page uses REMZAR%20whitepaper.pdf, which is the browser-safe version of the same filename.
Document status
Remzar is presented as a working Rust-based Layer-1 blockchain implementation. The whitepaper focuses on the base protocol rather than promotional claims: node operation, storage, networking, post-quantum cryptography, Proof of Registry consensus, economics, security boundaries, and operational roadmap.
Protocol Version: 1.0.0
Mainnet Start Date: 2026-06-26
Website: www.remzar.com
Explore Remzar
Learn how Remzar combines deterministic Proof of Registry consensus, post-quantum-oriented block attestation, Merkle batch commitments, local wallet ownership, transparent issuance, and built-in audit tooling into a sovereign Layer-1 blockchain.