Requiem Ledger Core

"A high-integrity Distributed Ledger Technology (DLT) core, featuring asynchronous cryptographic signatures, immutable block-chaining, and a proprietary proof-of-key consensus mechanism."

Overview

Requiem Ledger is a C++ based terminal-agnostic ledger engine. It is designed to simulate the core mechanics of decentralized finance (DeFi) in a low-level, zero-trust architecture.

Key Features

• Asynchronous Security: Transactions are processed via asynchronous cryptographic signing, ensuring that no fund movement occurs without explicit private key validation.
• Cryptographic Consensus: Every block is secured with a mathematical validation layer; the network rejects any transaction lacking a verifiable digital signature.
• Immutable Block-Chaining: Designed with a structural integrity focus, the ledger maintains a sequence of records that are computationally infeasible to reverse or alter once broadcast.
• Transparent History: Users maintain full auditability of their assets; the history command provides a real-time, granular view of all wallet-specific transaction flows.
• Proprietary Proof-of-Key: A unique, low-overhead consensus mechanism that verifies ownership and intent before any state transition in the ledger.
• Minimalist Architecture: Built for high-performance execution with zero external dependencies, providing total terminal control and optimized resource management.

Getting Started

1. Compilation

To compile the source code, use any standard C++ compiler:

g++ -o requiem RequiemLedger.cpp

2. Authorization

For security, the system requires an ADMIN_PASS environment variable.

$env:ADMIN_PASS="your_secure_password"
./requiem

Note: For rapid testing and evaluation purposes, you can use RequiemAdmin as the default ADMIN_PASS.

User Guide

Step 1: Registration

Upon launching the terminal, every user must initialize their identity within the ledger.

Step 2: Authentication

Access your wallet using your credentials. Note that admin-level operations require the ADMIN_PASS environment variable.

Step 3: Transaction Signing (TX)

Create offline-signed transactions. This ensures that no funds are moved without your private key's verification.

Step 4: Broadcasting

Once the transaction is signed and verified by the consensus mechanism, use the broadcast command to commit it to the immutable ledger.

All Commands: /help

You can run the /help command to list all commands and see their descriptions.

License

Copyright (c) 2026 requiemlaw (github.com/requiemlaw). All Rights Reserved. This source code is the intellectual property of requiemlaw and is provided for educational and portfolio evaluation purposes only.