RandyMcMillan

use num_bigint::BigInt;
use num_traits::{One, Zero};

// ============================================================================
// EXECUTABLE PROOFS & MATHEMATICAL VERIFICATION MODULE
// ============================================================================

pub mod proofs {
    use std::f64::consts::E;

RandyMcMillan

sudo du -h -a / 2>/dev/null | sort -h -r

RandyMcMillan

Installs all cross platform emulators for use with docker buildx

docker run -it --rm --privileged tonistiigi/binfmt --install all

RandyMcMillan

Connector Vaults: Delegated Execution and Stateless Revocation

Each chain of presigned vault transactions carries one tiny connector UTXO controlled by a controller wallet. Every transaction spends the current connector and creates the next, so it can execute only when the controller wallet signs at broadcast time. Spending the live connector elsewhere revokes the remaining chain without moving its funds or requiring presigned revocation transactions.

Properties:

• Offline signatures and presigned transactions are halved. An n-step policy needs n offline-signer authorizations instead of 2n (n authorizations + n revocations). This is especially impactful when performing large signing ceremonies on low-powered devices like hardware wallets.
• Revocation transactions do not need to be presigned. The controller wallet constructs th

RandyMcMillan

//! BIP: 2106
//! Layer: Consensus (Softfork)
//! Title: Extended 64-Bit Coinbase Timestamp and Header nTime Decoupling
//! Author: Randy McMillan <randy.mcmillan@gmail.com>
//! Comments-Summary: No comments yet.
//! Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-2106
//! Status: Draft
//! Type: Standards Track
//! Created: 2026-08-17
//! License: BSD-2-Clause

RandyMcMillan

use chrono::NaiveDate;
use serde::Deserialize;
use std::f64::consts::PI;
use std::io::Cursor;

const CSV_URL: &str = "https://raw.githubusercontent.com/coinmetrics/data/master/csv/btc.csv";
const GENESIS_DATE: &str = "2009-01-03";

/// Raw CSV Row matching Coin Metrics structure
#[derive(Debug, Deserialize)]

RandyMcMillan

//! # NIST SP 800-90B Health-Tested Jitter Entropy & BIP-64MOD Engine
//!
//! Implements Section 4 of NIST SP 800-90B requirements for physical entropy sources:
//! 1. **Repetition Count Test (RCT)** (§4.4.1): Continuous stuck-source detection.
//! 2. **Adaptive Proportion Test (APT)** (§4.4.2): Continuous bias monitor.
//! 3. **Startup Power-On Self-Test (POST)** (§4.3): Power-on health validation.
//! 4. **BIP-64MOD & C-ABI Engine**: Conditioned 64-bit modular word extraction and GCC interop.

use sha2::{Digest, Sha256};
use std::hint::black_box;

RandyMcMillan

ASMap in Bitcoin Core releases/ASMap data sources

Background

To get a general overview/refresher of the ASMap project please (re)read the post from Gleb on the Bitmex blog [1]. What is described there is still the status of ASMap file data sources to my knowledge.

Some further questions of mine about the process were discussed in November 2021 in an IRC meeting [2]. It was discussed that fresh ASMap files will be generated for and shipped with every release. The historic files that are part of the releases should be available in a separate repository under the bitcoin core GitHub organization. It was also discussed where the tools used during the release process should be maintained.

Since then, my focus has been on what would be the best possible data sources and quality assurance process for the input data of the ASMap file, i.e., a prefix to AS mapping that most accurately reflect the reality of the internet and that stays up to date for as long as possible.

RandyMcMillan

Theoretical ASMap deployment for v25.0 release

For reference, see the general release schedule of v25.0 here: bitcoin/bitcoin#26549

Tools/Repositories mentioned:

• asmapy
• sipasmap
• kartograf

Steps

RandyMcMillan

use rand::seq::SliceRandom;
use std::fmt;

#[derive(Debug, Clone, Copy, PartialEq, Eq)]
pub enum Suit {
    Clubs,
    Diamonds,
    Hearts,
    Spades,
}