# Doomsday Explorer

Anti‑Scanner TRNG Audit Tool – Bitcoin, open‑source, white‑hat.

View on GitHub
Check out presentation
⇒Official Page
BitcoinTalk (project)
BitcoinTalk ("replay noise" attack)
Doomsday Ecosystem 🌿:
Mg-Peers Yaqui Search

## ⚡️ Quick Overview

##### What

A PoC audit framework that shows how low‑entropy / predictable TRNGs can compromise Bitcoin wallets. Ready to use as a minimalistic preliminary audit tool.

##### Why

“Noise is NOT secure random”. The project demonstrates a real‑world attack surface that many RNG specs hide. And introduces an efficient mitigation approach.

It also aims at independent, public and practical verification, if not de-mystification, of NIST claims about security of their standards...with a powerful incentivized computational peer-to-peer network.

##### How

`npm install` → download address dump → `node ingest.js` → `node enumerate.js replica_name`.

Ledger Nano Deterministic Replica reproduces the source of entropy and the rest of the TRNG pipeline:

∀ 🌈spectra🌈 (exhaustive). `avalanche noise (first power-on)` → `SHA-256` → `entropy seed` → `thermal noise` → `phase-diff + XOR-fold + SHA256` → `wallet seed`.

→ Entropy Explorer Protocol mitigates the risk of attacker running this algorithm in attempt to steal funds.

## 📽️ Demo & Screenshots

###### ^ what AI admits...in response to childish inqury ^

###### ^ Dashboard ^

###### ^ Clock is ticking... ^

## 🚀 Getting Started

    # 1️⃣ Clone the repo
    git clone https://github.com/dk14/crypto.git
    cd crypto/chats/btc-audit

    # 2️⃣ Install dependencies
    npm ci                # reproducible install

    # 3️⃣ Pull the latest address dump (≈ 600 k addresses)
    curl -L https://addresses.loyce.club/addresses.zip -o addresses.zip
    unzip addresses.zip -d .

    # 4️⃣ Populate the local DB
    node ingest.js

    # 5️⃣ Run a test enumeration (choose one source)
    node enumerate.js ledger   # Ledger‑seed brute‑force
    node enumerate.js urandom  # /dev/urandom scan
    node enumerate.js clock    # Clock‑drift demo

Tip: add `--verbose` for detailed logs or `--dry-run` for a quick sanity check.

## 🔎 Running the Audits

Command | Description | Search space
--- | --- | ---
`node enumerate.js ledger` | Enumerates actually possible seeds derived from a Ledger hardware wallet TRNG. | small (millions to billions)
`node enumerate.js urandom` | Scans for wallets that used `/dev/urandom` directly as a private key. | small (millions to billions)
`node enumerate.js clock` | Reconstructs keys generated from system‑clock entropy (e.g., `time()%2^32`). | tiny (millions)

Outputs: `found.json` (compromised addresses + private keys) and `report.md` (ready‑to‑publish disclosure).

Note: the audit tool deliberately expands the search space to simulate attacks, thereby avoiding any real‑world exploitation while the Explorer Network is still under development

## 🔎 Explorer Protocol

Decentralized. Peer-to-Peer.

       Early warning defense system

Early-warning mechanism. Entropy miners outrun hackers with efficient TRNG replicas, publicly provide wallet users with examples of keys that can be dangerously close to their private secrets (seeds, mnemonics). User compares examples against their own secret privately: offline manually or in a firmware. When risk exceeds threshold - user migrates funds to a new wallet safely.
(any TRNG supported: Ledger, Trezor, quantum, enclaves, military)

Network architecture:

Data-submission format for entropy miners:

    `seeds, blockchain_id, replica_id, worker_id, worker_id_pow, reward_address, version, signature`.

     - seeds is list of seeds you uncovered with your algorithm
     - worker_id is YOUR pubkey
     - some reasonable worker_id_pow (SHA-256, CPU is enough) is recommended for Sybil-resistance,
       - it is over your pubkey simply: `<pubkey>+<magicNo>` - where magicNo is PoW (SHA256),
     - replica_id is 0 for ledger, 1 for trezor, up to 42 - reserved, others - arbitrary
     - blockchain_id is 0 for BTC, version is 0.
     - JSON format. Signature is over minified JSON with signature field absent
     - reward_address is where u get ur incentives

     (`worker_id` serves as a basis for work replication an distribution)

     (work replication ensures no one is hiding seeds)

     IPFS --metadata "project:ExplorerBTCAudit"

    Got your own private tool joining protocol?

    Guidelines for white-hat converts:

     - don't overload IPFS pinning services
      - you have to filter seeds based on metrics developed here (bitmatch as a starter).
     - CHECK that seeds don't belong to funded addresses.
      - If they do - submit address (NO seed, no secret) in an issue here, on GitHub.

    Notes:

     - IPFS will become replaced in favor of gossip.
     - More fields (eg sampled entropy) will be added.

Compute-reward mechanism. A wallet user rewards an entropy miner, who provides closest examples to user's private seedphrase. This incentivizes worker to not turn black-hat against the user, no special contract required. The reward mechanism naturally selects workers with more accurate TRNG replicas.

Explorer Node UI:

Science: Secure‑random values are obtained by “running away” from a high‑entropy cluster – the cluster itself provides public, verifiable examples of maximum util entropy, while your private entropy must stay as far away from those examples as computationally feasible. In practice this is analogous to how a hash‑cash PoW works: PoW uses a costly, random‑looking computation for consensus and Sybil‑resistance; our “entropy‑escape” mechanism uses the same principle for protecting private randomness. Preserving both approaches yields scientific value that outlives any single human application.

## 💰 Revenue‑Sharing & Funding

##### Fund any arbitrary BTC

Funding is needed to build and maintain high-quality software for The Explorer Network.

`bc1qekvmkczge3hxrvwdf2lj3yyvgjnparn3fdf9lg`

Continue

Instant inclusion in the Explorer Network "profit‑share" pool.

(revenue comes from network fees on compute rewards and other computationally intensive services)

BitcoinTalk

##### Bid on a Feature

Send a signed TXID + description – your feature is prioritized and you get a larger revenue slice. Bids are listed in `CONTRIBUTORS.md`.

##### Sponsor a Compute Node

Earn a “Node‑Sponsor” badge and a share of fees for all audits run on your hardware.

Inquire (Node-Sponsor status requires over 0.1 BTC investment)

##### Early bird

Earn bonuses and extra profit‑share for investing early

+ Get BRC-20 and Lightning assets proportionally to donations (~Q4 2026), with extra benefits for early investors!!11

Profit‑sharing logic lives in `profit-sharing.js`. Assets in `issue-assets.js`. Feel free to audit, fork or improve it.

## 🛣️ Roadmap & How To Contribute

Milestone | ETA | Description
--- | --- | ---
v1.1 | Q3 2026 | Explorer UI. Tool integration into Explorer protocol
v1.2 | Q4 2026 | Ledger replica. Ledger firmware integration for risk reporting
v1.3 | Q1 2027 | Full “Explorer Network” – decentralized marketplace of auditors.
v2.0 | Q2 2027 | Other replicas (Trezor, Apple Secure Enclave, military TRNGs). Audits for public SSL certificates

##### Want to help?

1. Open an issue – bug or feature request.
2. Submit a PR – follow the existing code style (`eslint-config-airbnb-base`).
3. Donate – any amount pushes the roadmap forward.

All contributors and spendings (transparent fund tracking) are listed in `CONTRIBUTORS.md`. Fund contributors automatically receive a share of future revenues.

## 📜 Authentication

Message: `"Doomsday Explorer Project for Bitcoin: https://github.com/dk14/crypto/tree/main/chats/btc-audit"`

Address: `bc1qekvmkczge3hxrvwdf2lj3yyvgjnparn3fdf9lg`

Signature: `IHdq/tIQtQeimfF92NOyOOdz2/iq2YR6qjD8vLgHWK3GGGETKX76L0e4Tvgtb1fOHrbLiW87QYIuOdCKYbSvmpA=`

## 📜 License & Disclaimer

License – MIT (see `LICENSE` file).

Disclaimer – This tool is for **educational, research and white‑hat security auditing only**. Misuse to steal funds is illegal and will be prosecuted. The author disclaims any liability for damages caused by misuse.