Single-Binary Operation
A Remzar node is designed to combine wallet generation, encrypted key storage, database setup, P2P networking, validator registration, transfers, chain inspection, diagnostics, and audit exports into one guided node workflow.
Simple to operate. Bounded to validate. Built to audit.
Remzar is designed around a practical principle: public blockchain infrastructure should be understandable, locally operable, and directly verifiable without depending on hidden services or energy-race mining.
Deterministic Consensus
Proof of Registry selects eligible validators from an explicit registry using deterministic slot timing, leader selection, heartbeat renewal, lease expiry, quarantine, and failover rules.
Local Auditability
Blocks, transactions, rewards, logs, Merkle roots, validator data, and cryptographic fingerprints can be inspected and exported through built-in audit tooling.
A base layer for ownership, verification, and transparent operation.
Remzar avoids open-ended mining competition and keeps core protocol behavior visible through explicit constants. Block size, transaction counts, validator timing, reward issuance, storage boundaries, and validation rules are designed to remain predictable and inspectable.
The result is a chain architecture focused on direct operation: one program, one chain, bounded rules, deterministic participation, post-quantum-oriented cryptography, and repeatable auditability.
Core Protocol Facts
- Mainnet Start Date: 2026-06-26
- Default Node Port: 36213
- Max Block Size: 2 MiB
- Max Transactions: 8,192 per block
- Signature Model: one ML-DSA-65 block-batch signature
- Commitment Model: Merkle root over transaction IDs
How Remzar works
Remzar keeps the base protocol focused: register, participate, verify, and audit through deterministic rules and bounded local state.
1
Operate a Node
The node workflow is designed to initialize local storage, create or load wallets, connect to peers, inspect the chain, and manage local operator tasks from one executable.
2
Participate Through Registry
Validators participate through an explicit registry. Eligibility is controlled through deterministic timing, warmup, quarantine, renewal, lease expiry, and peer-liveness rules.
3
Verify and Audit
Blocks are committed through Merkle roots and attested at the block level. Operators can inspect chain data and export structured audit artifacts without relying entirely on third-party explorers.
Post-quantum-oriented security without per-transaction signature overhead.
Remzar commits transaction batches through Merkle roots and signs the block-level commitment once with ML-DSA-65. This keeps post-quantum signature verification bounded at the block level instead of requiring a post-quantum signature verification for every transaction in a block.
ML-DSA-65 Block Attestation
The protocol uses post-quantum-oriented block attestation so validators can authenticate block-batch commitments under a modern cryptographic design.
Merkle Batch Commitments
Transactions are hashed into transaction IDs, committed into a Merkle root, and validated against bounded block and transaction limits.
Encrypted Local Wallets
Wallet storage is designed around local ownership, passphrase hardening, authenticated encryption, and careful handling of sensitive key material.
REMZAR Tokenomics
- Native Asset: REMZAR / ZAR
- Maximum Supply: 200,000,000 ZAR
- Genesis Reward: 0 ZAR
- Issuance Source: validator block rewards only
- Initial Reward: 50 ZAR per block
- Reward Step Interval: 500,000 blocks
Transparent issuance. No protocol-level premine.
Remzar’s current monetary design has no protocol-level founder mint, treasury mint, development reserve, staking bucket, or gaming allocation. Supply enters circulation through validator block rewards until the 200 million ZAR maximum supply is reached.
The reward ladder steps down through fixed 500,000-block eras and then stabilizes at 1 ZAR per block until the maximum supply is exhausted.
Designed for practical verification use cases
Remzar is built as a sovereign base layer for verified data, local ownership, auditable settlement, and protocol-level transparency.
Verified Data Records
Hash files or data objects, anchor records, and produce receipts that can later prove existence within a committed chain context.
Merchant and Operator Audits
Export chain ranges, logs, transaction summaries, rewards, validator identifiers, and cryptographic fingerprints for direct review.
Future Sidechain Expansion
Remzar’s roadmap keeps the base layer conservative while allowing optional mini-chains, sidechains, and future anchored verification tools to develop around it.
Remzar’s goal is not to claim unlimited scalability or completed decentralization. Its goal is to preserve a disciplined base layer: bounded validation, deterministic consensus, transparent issuance, local auditability, and a clear path for continued hardening.
Read the Remzar whitepaper
Explore the full protocol design, including node operation, Proof of Registry consensus, cryptographic stack, block model, storage layout, economics, benchmarks, security boundaries, and roadmap.