Jonas adamjonas

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

Reusable taproot addresses

Abstract

This document proposes a new scheme to avoid address reuse while retaining some of the convenience of address reuse, keeping recoverability purely from Bitcoin time chain and avoiding visible fingerprint. The scheme has negligible average overhead.

Motivation

The `bitcoin-core/guix.sigs` Repository Workflow

Common environment variables

export SIGNER="hebasto"
export GUIX_SIGS_REPO="/home/hebasto/dev/guix.sigs"
export DETACHED_SIGS_REPO="/home/hebasto/dev/bitcoin-detached-sigs"

Error:

>>> [do_build] Command failed: git apply /Users/jonas/bitcoin-dir/bitcoin-maintainer-tools/patches/stripbuildinfo.patch
>>> [do_build] Could not apply patch to strip build info. Probably it needs to be updated

Checkout the patchset from the last patch:

git checkout 'master@{aug 1}'

Moved to https://github.com/fjahr/debugging_bitcoin to allow for better collaboration.

This document is currently optimized for MacOS. If you would like to help me add Linux equivalent commands, please let me know.

Debugging Bitcoin Core

This guide is designed to give beginners of C++ development and/or people new to the bitcoin core code base an overview of the tools available for debugging issues as well as giving hints where issues may trip you up.

Moved to https://github.com/sipa/writeups/tree/main/minimizing-golomb-filters

Network partition resistance

For the Bitcoin network to remain in consensus, the network of nodes must not be partitioned. So for an individual node to remain in consensus with the network, it must have at least one connection to that network of peers that share its consensus rules. This document describes how we attempt to achieve this.

We can't rely on inbound peers to be honest, because they are initiated by others. It's impossible for us to know, for example, whether all our inbound peers are controlled by the same adversary.

src :

Navigating while typing

Let’s start by what you can do while typing. These keystrokes change only what happens on the input line (the line where you type stuff).

arrow left/right: move one character left or right.

	javascript: (async function() {
	async function unwrap() {
	const loadMoreBtn = document.querySelector('button.ajax-pagination-btn.no-underline.pb-1.pt-0.px-4.mt-0.mb-1.color-bg-default.border-0');
	if (loadMoreBtn) {
	loadMoreBtn.click();
	await setTimeout(unwrap, 5000);
	}
	}
	await unwrap();
	await setTimeout(() => document.querySelectorAll('span.Details-content--closed').forEach((e) => {

	#!/bin/sh

	cd ~/src/bitcoin/src

	./bitcoind -regtest -daemon=1
	printf "Waiting for regtest bitcoind to start"
	while ! ./bitcoin-cli -regtest getconnectioncount 2>/dev/null 1>&2
	do printf .; sleep 1
	done; echo