jaonoctus

# If that is inacceptable, pick as internal key a "Nothing Up My Sleeve" (NUMS) point, 
# i.e., a point with unknown discrete logarithm. 
# One example of such a point is H = lift_x(0x50929b74c1a04954b78b4b6035e97a5e078a5a0f28ec96d547bfee9ace803ac0) 
# which is constructed by taking the hash of the standard uncompressed encoding of the secp256k1 base point G as X coordinate. 
# In order to avoid leaking the information that key path spending is not possible 
# it is recommended to pick a fresh integer r in the range 0...n-1 uniformly at random and use H + rG as internal key. 
# It is possible to prove that this internal key does not have a known discrete logarithm with respect to G 
# by revealing r to a verifier who can then reconstruct how the internal key was created.

import hashlib

storopoli

---

title: How to Nixify your codebase sub_title: Docker is a shitcoin author: Jose Storopoli, Alpen Labs, storopoli.io, stratabtc.org options: incremental_lists: true theme: override: code: alignment: left

josibake

Silent Payments (BIP352) Testing Guide

This guide assumes you have a basic knowledge of the command line and are familiar with the bitcoin-cli RPC client.

Setup (optional)

While not required, this guide was written using a bendir directory for easier testing. If you want to follow the guide without using bendir, it's recommended you alias bitcoin-cli to bitcoin-cli -named -signet -datadir=<your testing datadir> so you can copy-paste the commands directly from the guide. To use bendir for your testing environment:

git clone https://github.com/josibake/bendir.git

notmandatory

This gist demonstrates how to create a bitcoind wallet that is based on pay to taproot (P2TR) descriptors.

Tools used:

• docker with image bitcoindevkit/bitcoind:v22.0rc2
• bitcoin dev kit cli, bdk-cli

About bech32 vs bech32m addresses

Steps:

1. Create aliases to work with bitcoind docker image

fxfactorial

Lightning transactions: from Zero to Hero

This gist contains everything you need to understand Bitcoin/Lightning transactions. We ignore segwit subtleties and fields that aren't necessary for our global understanding.

Table of Contents

• Bitcoin transactions
  • Transaction format
• Sighash flags

davecgh

Table of Contents

1. Overview
2. Getting Started

### 1. Overview

When developing bitcoin applications or testing potential changes, it is often extremely useful to have a test network where transactions are actually mined into blocks and difficulty levels are low enough to generate blocks as needed.

In order to facilitate these scenarios, btcd provides a simulation network (--simnet). The following is an overview of the most important properties that distinguish it from the main network: