jamesob jamesob

Prelude

Soft forks tighten the rule set of what transactions are valid. Additional opcodes allow existing owners of coins to put additional constraints on how those coins are spent.

Many covenant-enabling opcodes are nothing more than "new", more specific sighashes[^sigh]. Other opcodes allow access to information about a spending transaction.

None of this is conceptually objectionable. People should be able to put constraints on their property. But first we must do no harm.

The concrete issues, when gauging additional script functionality, are:

`OP_VAULT` transaction examples

The following output was generated by the OP_VAULT functional test suite.

Normal spend, 1 input [NoRecoveryAuth]

Initialize (94 vB)

	#!/bin/bash
	IMAGE_NAME="claude-code-runner"
	CONTAINER_NAME="claude-code-$(basename $(pwd))"

	RED='\033[0;31m'
	GREEN='\033[0;32m'
	YELLOW='\033[1;33m'
	NC='\033[0m' # No Color

	# Parse arguments

	#!/bin/bash
	IMAGE_NAME="claude-code-runner"
	CONTAINER_NAME="claude-code-$(basename $(pwd))"

	RED='\033[0;31m'
	GREEN='\033[0;32m'
	YELLOW='\033[1;33m'
	NC='\033[0m' # No Color

	# Parse arguments

	Connected to Bitcoin node. Current block height: 905108
	Analyzing last 12960 blocks...
	Starting from block: 00000000000000000000e9900f08f6dc109762d09d4d0b31b8ece5ab35a5401e
	Processing block 12960/12960...
	Processed 12960 blocks

	============================================================
	Bitcoin Address Type Analysis
	============================================================
	Total Value Analyzed: 53757862.95514309 BTC

	#include <iostream>
	#include <vector>
	#include <random>
	#include <chrono>
	#include <iomanip>
	#include <cassert>

	// Include libsecp256k1
	#include <secp256k1.h>

	#include <iostream>
	#include <format>
	#include <cstring>
	#include <vector>
	#include <thread>
	#include <random>
	#include <chrono>
	#include <secp256k1.h>

	constexpr size_t NUM_KEYS = 6'500'000;

	# This (very scant) guide allows you to do Android and react-native development on Linux by
	# running the android emulator in a container.

	# install yay via AUR
	git clone https://aur.archlinux.org/yay.git && cd yay && makpkg -si

	# install all android dev packages per https://wiki.archlinux.org/title/Android
	yay -Sy android-sdk-cmdline-tools-latest android-sdk-build-tools android-sdk-platform-tools android-platform

	# add to .zshrc

	$ make clean && ./configure && make clean && make && SECP256K1_BENCH_ITERS=200000 ./bench verify sign

	Benchmark , Min(us) , Avg(us) , Max(us)

	ecdsa_verify , 71.5 , 71.5 , 71.5
	ecdsa_sign , 54.8 , 54.9 , 54.9
	schnorrsig_sign , 41.9 , 41.9 , 41.9
	schnorrsig_verify , 72.6 , 72.6 , 72.6

	// Open Inspect -> Console, copy-paste this in.

	function load_all_gh_comments() {
	let buttons = Array.from(document.querySelectorAll('button'));
	let get_with_text = (text) => buttons.filter((b) => b.textContent.includes(text));
	let load_more_buttons = get_with_text("Load more");
	let nothing_loading = get_with_text("Loading…").length === 0;

	if (load_more_buttons.length === 0 && nothing_loading) {
	console.log("done loading comments");

jamesob jamesob

Prelude

OP_VAULT transaction examples

Normal spend, 1 input [NoRecoveryAuth]

`OP_VAULT` transaction examples