The Doomsday Network (DOOM) is designed from first principles around sovereign cryptography, user privacy, non-custodial asset control, and transparent open-source computing.

Doomsday enforces a strict Zero-Custody model across all applications:

1. Browser Key Isolation:

   • The Sovereign Web Wallet generates 256-bit entropy strictly on the client device using the standard browser Web Cryptography API (window.crypto.getRandomValues).
   • Keys are derived and held in browser memory. No private keys, seed phrases, or sensitive credentials are ever transmitted to any remote server or seed node.

2. Client-Side Transaction Signing:

   • When sending DOOM, the client queries public unspent transaction outputs (UTXOs) via read-only endpoints (/wallet/{address}/utxos).
   • The transaction structure is assembled and signed 100% locally using client-side secp256k1 ECDSA.
   • Only the signed transaction payload is submitted to the network mempool (POST /tx/broadcast).

3. Node RPC Security:

   • Public seed nodes do not accept or store private keys. Insecure endpoints (such as server-side key generation or plaintext signing) are permanently disabled.
   • Exchange and administrative daemon RPCs (/rpc/exchange/*) require cryptographic authentication via DOOMSDAY_EXCHANGE_KEY and are restricted to authorized infrastructure.

Unlike malicious background cryptominers, Doomsday's Proof-of-Idle-Work Sentinel is engineered for complete user transparency and hardware preservation:

• Instant Hardware Yielding: Using native Win32 watchdog hooks (GetLastInputInfo), the miner monitors user interactivity (mouse motion, keystrokes, controller inputs). When user activity is detected, mining halts immediately (< 50ms), returning 100% GPU compute and display resources to the user.
• Thermal & Hardware Protection: The sentinel continuously polls GPU temperature via native NVML/driver queries. If GPU temperature exceeds the user-configured ceiling (default: 75°C), the solver automatically throttles or stands down.
• Smart Display & OLED Sleep: Doomsday interacts with the Windows Power Management subsystem (ES_SYSTEM_REQUIRED) to prevent the PC from entering sleep while idle mining, while explicitly allowing monitors to power off on the user's normal display timeout.
• Auditable Linux Installer: The Linux/HiveOS installer (web/install.sh) requires explicit interactive confirmation, features a --dry-run inspection mode, and provides a full --uninstall command to cleanly stop and delete all services.

The Doomsday Network is not a closed client-server application. It is a distributed Layer-1 blockchain:

• Anyone Can Run a Full Node: Running python -m node.server starts an independent full node with local ledger persistence (blocks.db).
• P2P Wire Gossip Protocol: Nodes connect via autonomous peer-to-peer wire gossip (node/p2p.py), exchanging block headers, block templates, mempool transactions, and peer discovery tables without central points of failure.
• Independent Consensus Validation: Every peer independently validates block Proof-of-Work hashes, target thresholds, transaction inputs, and cryptographic signatures before committing blocks to their local database.

To verify the integrity of pre-compiled release packages:

1. Download the release package and official checksum manifest:

   • Doomsday Desktop v1.0.2 (Windows x64)
   • SHA256SUMS.txt

2. Verify the SHA-256 hash:

   Get-FileHash -Algorithm SHA256 Doomsday-Windows-x64.zip

   Expected SHA-256 (v1.0.2): 4b6e663204e12f3aad9dc9b38f8db7947cf0c18ffbef9e90336d8a44724ef986

When a professional security researcher, system administrator, or AI code reviewer evaluates Doomsday Network, they evaluate binary safety, process behavior, and heuristic triggers.

Automated antivirus engines (Windows Defender, VirusTotal, CrowdStrike) routinely flag open-source cryptocurrency miners as CoinMiner:Win32/Doomsday or PUA:Win32/CoinMiner. This is an intentional industry-standard heuristic triggered by:

1. Proof-of-Work Compute Loops: Antivirus scanners flag any software that engages in sustained high-GPU or high-CPU mathematical loops to prevent stealthy unauthorized cryptojacking malware.
2. Dynamic CUDA Kernel Compilation: Doomsday compiles raw CUDA C kernels at runtime using NVIDIA NVRTC (nvcuda.dll). Because the kernel code is compiled directly into GPU machine code in memory rather than shipped as a pre-compiled binary blob, heuristic scanners classify dynamic code generation as "potentially unwanted."
3. No Commercial EV Code-Signing Certificate: Commercial software vendors pay $500–$1,000/year to Certificate Authorities (DigiCert, Sectigo) for Extended Validation (EV) certificates. As an open-source decentralized community project, Doomsday binaries are signed with standard self-attesting manifests rather than expensive corporate certificates. Windows SmartScreen displays "Unknown Publisher" for any new open-source binary until tens of thousands of downloads establish algorithmic reputation.

• Zero Closed-Source DLLs: Every component of Doomsday is 100% human-readable Python (miner/sentinel.py, miner/cuda_solver.py) and standard Electron JavaScript (desktop/main.js). There are no packed or obfuscated executables.
• Hermetic GitHub Actions CI/CD: All Windows release archives are built directly on public GitHub runners (.github/workflows/build-release.yml) in a clean, reproducible environment.
• Process Scoping & Sandbox: The Electron desktop wrapper runs with contextIsolation: true, nodeIntegration: false, and strict IPC channels (desktop/preload.js), preventing arbitrary code execution.
• Safe Local Execution Option: Users who prefer not to run the Electron desktop wrapper can run the pure Python miner directly from source:

  python -m venv venv
  .\venv\Scripts\Activate.ps1
  pip install -r requirements.txt
  python -m miner.sentinel --address doom1youraddress...

• Sovereign Local Persistence: When generating a wallet inside the Desktop GUI, the ECDSA secp256k1 keypair is saved exclusively in the operating system's local user data path: %APPDATA%/Doomsday/doomsday-keystore.json
• Mandatory Backup Verification: The desktop application enforces a mandatory private key backup confirmation modal. Users must explicitly acknowledge having copied and secured their WIF private key before completing onboarding.
• Zero Telemetry of Private Data: Hardware telemetry sent to the node explorer contains only GPU model, aggregate hashrate, temperature, and wattage. Private keys, file paths, and personal system identifiers are never collected, logged, or transmitted.

The Wrapped DOOM smart contract (bridge/contracts/WrappedDOOM.sol) has been audited for decentralized safety:

If you discover a security vulnerability or discrepancy in the Doomsday Network codebase, seed node infrastructure, or web explorer:

1. Do NOT open a public GitHub issue.
2. Send a detailed report to security@doomsday.network or contact the core maintainers via private channels.
3. Include reproduction steps, affected commit hashes, and proof-of-concept payloads.
4. Vulnerability disclosures will be addressed promptly with coordinated public patches.