Skip to content

Instantly share code, notes, and snippets.

View jnewbery's full-sized avatar
🥟

John Newbery jnewbery

🥟
882 followers · 10 following
View GitHub Profile
@jnewbery
jnewbery / print_coinbase_height.py
Created January 19, 2018 22:42
#!/usr/bin/env python3
"""Search for blocks where the BIP34 indicated coinbase height is > block height.
Uses Bitcoin Core's test framework."""
import time
from authproxy import AuthServiceProxy
from script import CScript
a = AuthServiceProxy("http://<user>:<password>@<ip>:<port>")
@jnewbery
jnewbery / wallet_design_notes.md
Last active January 9, 2019 22:44

Bitcoin Core wallet design notes

The Bitcoin Core wallet consists of:

  • An in memory keystore (in /src/keystore.cpp), which contains:
    • private keys stored as mapKeys - a map from the CKeyID to the private key.
    • watchonly public keys, stored as mapWatchKeys - a map from the CKeyID to the public key.
    • scripts, stored as mapScripts - a map from the CScriptID to the secrialized script.
    • watchonly scripts, stored as setWatch - a set of serialized scripts.
  • Additional key metadata such as key birthday, hd derivation path. See CKeyMetadata in /src/wallet/walletdb.h
@jnewbery
jnewbery / file_descriptors_bitcoin_core.md
Last active February 23, 2021 06:00
File Descriptors in Bitcoin Core

Overview

  • We use leveldb for multiple databases: block index, chainstate and (optionally) txindex. block index is very small, but chainstate and txindex can grow to many hundreds of files.
  • Each database has a limit on number of 'open files'. This limit includes both mmapped files (which ldb takes the fd for, opens and then closes, returning the fd) and files which ldb opens and holds the fd for. There's a default in the leveldb code here. This is the per-database max_open_files limit.
@jnewbery
jnewbery / sighash.md
Created January 16, 2019 22:38
SIGHASH notes
@jnewbery
jnewbery / BitcoinCoreReviewClub.md
Last active October 20, 2020 09:12
Bitcoin Core PR Review Club
@jnewbery
jnewbery / git-br.py
Created May 29, 2019 18:57
git tools
#!/usr/bin/env python3
import subprocess
import os
if os.name == 'posix':
RED = "\033[1;31m"
BLUE = "\033[0;34m"
CYAN = "\033[0;36m"
GREEN = "\033[0;32m"
RESET = "\033[0;0m"
@jnewbery
jnewbery / tx_relay_peer_prioritization.md
Last active July 17, 2019 19:58
P2P peer prioritization logic for tx relay

Scenario

Bitcoin nodes relay txs to each other over the P2P network. If a node receives a valid tx from a peer, it adds it to the mempool and relays it to its other peers. If it receives an invalid tx from a peer, it must decide what action to take. We distinguish three cases:

  1. a transaction which is valid according to consensus rules, but invalid according to the node's policy rules.
  2. a transaction which is valid according to long-established consensus rules,
@jnewbery
jnewbery / 2019_09_10_socratic_tel_aviv.md
Last active September 10, 2019 08:06
2019-09-10 Tel Aviv Socratic Seminar
@jnewbery
jnewbery / labitcoin_schnorr_notes.md
Last active July 8, 2020 19:02
Labitconf schnorr/taproot presentation links and notes
@jnewbery
jnewbery / 2019_12_14_socratic_buenos_aires.md
Last active December 17, 2019 20:52