Developer‐Onboarding‐Guide - kalashnikovski/cvn_node GitHub Wiki
🛰️ Covenant Standard (CVN) Protocol v3 — Developer Onboarding Guide
Welcome to the core documentation space for the Covenant Standard (CVN) Protocol v3 network tier. This guide serves as a technical blueprint for open-source systems engineers and independent node operators attempting to clone, compile, and establish a permanent peer-to-peer (P2P) mesh bridge with our live consensus core.
🏗️ Architectural Core Overview
The CVN protocol is an open-source, multi-threaded Layer-1 consensus engine engineered completely from scratch in Go.
- State Ledger Model: Handles transaction graph tracking via a hardened, Bitcoin-style Unspent Transaction Output (UTXO) cash graph to preserve thread-safe, concurrent validation capabilities under high workloads.
- Macroeconomic Rules: Hardcodes an algorithmic total supply structure featuring an adaptive difficulty-adjustment heartbeat calibration loop, a 49-year chronological Canonical Jubilee state-decay matrix, and a Model B volition-driven priority pool (Mempool Queue).
- Storage Plane: Memory state vaults execute local database file updates (
ledger_vault_backup.json) completely asynchronously via detached background threads protected by thread-safesync.Mutexlocks to keep hardware hashing loops un-throttled.
🏁 Automated Node Onboarding Workspace Diagram
When a new operator clones the repository and executes the primary gateway script, the local environment processes their setup through an automated initialization matrix:
[ Operator executes .\AutoOnboard_And_Mine.bat ]
|
v
[ Step 1: Toolchain Audit & Workspace Scan ]
Verifies native Go Runtime (v1.20+) & GCC Compiler
|
v
[ Step 2: CGO Multithreaded Standalone Compile ]
Compiles code natively into cvn_node.exe
|
v
[ Step 3: Identity & Cryptographic Security Check ]
Looks for local file: 'my_crypto_address.txt'
/ \
(File Exists) (File Missing)
/ \
[Read Active Private Key] [Run Autonomous Keygen Module]
\ |
\ Generates unique ECDSA pair
\ |
\ Writes public address to disk
\ |
v v
[ Step 4: Network Seed Synchronization Handshake ]
Dials static seed IP over Port 8080 to sync ledger
🛠️ Step-by-Step Initial Setup Requirements
📋 Prerequisites
Before launching compilation scripts, ensure your host development environment satisfies these absolute baselines:
- The Go Toolchain: Native Go Runtime installation (v1.20 or newer recommended). Verify via terminal:
go version. - CGO Compiler Flags: GCC C-Compiler utility toolchain installed (e.g., MinGW-w64) with native environment parameters mapped properly.
- Network Firewalls: Inbound TCP network communication traffic channels for Ports 8080 and 8081 opened on your host router gateway interface.
🚀 Launching the Node Interface
Open PowerShell as an Administrator, navigate to your desired local tracking directory path, and execute this chronological command string:
# 1. Clone the master repository source files
git clone https://github.com/kalashnikovski/cvn_node
cd cvn_node
# 2. Fire up the automated compilation script loop
.\AutoOnboard_And_Mine.bat
🔐 Identity Ownership: Keys & Private Parameters
The protocol enforces sovereign identity logic rules. A new operator will not mine directly to the creator's wallet.
The moment the node executable spins up for the first time, the cryptographic keygen module generates authentic, unique private/public key signatures right inside their local folder workspace. The node stamps their fresh public address (e.g., CVN_b10bf...) directly to my_crypto_address.txt to serve as their permanent block reward destination.
Opening Your Local Wallet Profile App:
To monitor block balances, inspect transaction receipts, or authorize outbound transactions across the open web channels, operators simply execute the graphic interface shell layout inside a separate terminal window:
.\LaunchWallet.bat
The application will automatically ingest their private key file, synchronize with their locally updated ledger database, and flash their personal balance statistics cleanly!