About Remzar Blockchain

What is Remzar?

Remzar is a sovereign base-layer blockchain built around one core idea: a public blockchain should not require hidden services, complicated infrastructure, or energy-race mining to be useful. A Remzar node is designed to run from a single compiled Rust binary that includes wallet creation, encrypted key storage, local database setup, peer-to-peer networking, validator registration, block production, transfers, chain inspection, diagnostics, and audit exports.

Why Remzar Exists

Many blockchain systems place a gap between public participation and the practical work required to operate a node. Remzar is designed around the opposite assumption: users, validators, merchants, and organizations should be able to run infrastructure directly, inspect what the node is doing, and verify the chain with clear local tools.

• No open-ended mining race: Remzar avoids Proof-of-Work hash competition and uses deterministic validator participation instead.
• No hidden operational stack: wallet tools, node runtime, registry logic, logs, balances, transfers, and audit exports are exposed through the Remzar node workflow.
• No protocol-level premine: the current monetary design starts with a rewardless genesis block and releases supply through validator block rewards only.

Protocol Facts at a Glance

Remzar keeps its base protocol understandable by using clear constants for timing, block limits, validator participation, cryptographic commitments, and monetary issuance.

Proof of Registry Consensus

Remzar uses Proof of Registry, an energy-efficient validator participation model based on explicit registry membership, deterministic eligibility, leader selection, validator warmup, quarantine, heartbeat renewal, lease expiry, dead-peer eviction, and deterministic failover rounds.

During early network growth, validator admission may use bootstrap safety controls. The long-term direction is transparent, rule-driven onboarding while preserving bounded validation and operational simplicity.

Post-Quantum-Oriented Security

Remzar’s cryptographic design centers block attestation around ML-DSA-65, a post-quantum digital signature scheme. Instead of requiring one post-quantum verification for every transaction in a block, Remzar commits transaction batches through Merkle roots and signs the block-level commitment once.

Single-Binary Node Workflow

Remzar is designed to make the full node lifecycle accessible from one guided command-line workflow. The same program exposes wallet generation, database setup, node operation, transfers, validator status, chain inspection, logs, and audit exports.

1. Setup Database — initialize local directories and RocksDB databases.
2. Generate Wallet — create keys and encrypted wallet files.
3. Start Node — bootstrap P2P, initialize chain state, and enter the runtime loop.
4. Blockchain Console — inspect blocks, headers, and chain activity.
5. Send Coins — unlock a wallet, build a transaction, sign, and propagate.
6. Receive Coins — view inbound wallet information.
7. Participant Status — inspect validator registry and leader schedule state.
8. Check Balance — read account state and compute balances.
9. List Wallets — discover local encrypted wallets.
10. Certificate / NFT — hash files or data objects and create verifiable receipts.
11. Send Chat — send signed peer messages over the P2P layer.
12. Send File — transfer files in chunks with integrity verification.
13. Wallet Utilities — perform guarded wallet maintenance and recovery actions.
14. Backup Wallet — copy encrypted wallet files for safe storage.
15. Debug Wallet Keys — validate decryptability and inspect safe metadata.
16. Export Logs — export bounded structured logs from the log database.
17. Audit Report — export chain ranges as JSON or PDF-style audit artifacts.
18. Games — optional module outside the base consensus core.
19. FAQ — access built-in operator documentation.
20. Exit — shut down the workflow safely.

Transparent Tokenomics

REMZAR is the native asset of the Remzar Layer-1 blockchain. The current monetary policy is designed to be simple to inspect and reproduce: maximum supply is capped at 200 million ZAR, genesis is rewardless, and issuance comes from validator block rewards only.

The reward ladder begins at 50 ZAR per block, steps down through fixed 500,000-block eras, and then stabilizes at 1 ZAR per block until the supply cap is reached.

Auditability by Default

Remzar treats auditability as part of the base node design. Blocks, transaction batches, rewards, logs, validator information, Merkle roots, and cryptographic fingerprints can be exported through built-in tooling. This allows operators, merchants, exchanges, and organizations to inspect local chain activity without depending entirely on third-party explorers.

Security Boundaries

Remzar is designed to fail closed against malformed inputs, oversized payloads, stale blocks, invalid signatures, replay attempts, double-spend attempts, unstable peers, and unavailable validators. The protocol uses explicit limits for block size, transaction count, transaction buffers, timestamp skew, slot drift, validator renewal, and peer eviction.

• Block size bound: 2 MiB maximum block size.
• Transaction bound: 8,192 transactions per block.
• Buffer bound: 2 MiB disk-backed transaction buffer.
• Timing bound: 30-second slots with deterministic failover windows.
• Cryptographic bound: one ML-DSA-65 block-batch signature per block commitment.