Lucas Ontivero lontivero

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

First and foremost the manual mentions it explicitly:

[Use] the standalone home-manager tool. For platforms other than NixOS (...), this is the only available choice. (...) See Section 1.1, “Standalone installation” for instructions (...)

https://grahamc.com/blog/erase-your-darlings
https://github.com/ryantm/home-manager-template
ico nix-store sqlite corruption NixOS/nix#1353
ico nix-store permission error NixOS/nix#4356
https://rgoswami.me/posts/local-nix-no-root/
https://dram.page/p/bootstrapping-nix/

The purpose of this document is keep track of my learning process while I learn F#.

Introduction

My first programming language was Basic, Sinclair BASIC first and GW-BASIC a few months later, then DBase III+, then Clipper Summer 87, then Clipper 5, Pascal 4.5, FoxPro, Microsoft Macro Assembler, C, C++, Delphi, Builder C++, Visual Basic, and many more until C#.

Nowadays there are thousands and thousands of programming languages but only a few concentrate the huge majority of programmers. However, something is clear: programming languages don't last forever or are not cool forever. Whoever

Architecture

Use Onion architecture
- Dependencies go inwards. That is, the Core domain doesn't know about outside layers
Use pipeline model to implement workflows/use-cases/stories
- Business logic makes decisions
- IO does storage with minimal logic
- Keep Business logic and IO separate
Keep IO at edges

Useful tips and tricks

Productivity

Developers work with many branches at the same time because during any single day they review others' pull requests, try new crazy things, work on new features/bug-fixes and also fix somebody else's PRs. All this forces a combination of git stash [pop|save], git fetch, git checkout [-f] and again git stash [pop|apply]. No matter if this is done by command line or with a tool the problem of having only one copy of the code is an ugly constrain.

Wasabi Wallet folders organization (suggestion)

Create main local bare repository

First clone your existing repository as a bare repo (a repository without files) and do it in a .git directory.

	1) COPY SSH KEYS TO USER@HOST TO ENABLE PASSWORD-LESS SSH LOGINS. (NOT ON MAC)

	ssh-copy-id user@host

	To generate the keys use the command ssh-keygen

	2) START A TUNNEL FROM SOME MACHINE’S PORT 80 TO YOUR LOCAL POST 2001

	ssh -N -L2001:localhost:80 somemachine

	// This is just an initial example / tech-demo.
	#if INTERACTIVE
	#I "./../packages/NBitcoin/lib/net45/"
	#I "./../packages/Newtonsoft.Json/lib/net45"
	#r "NBitcoin.dll"
	#r "Newtonsoft.Json.dll"
	#else
	module BlockChain
	#endif

	----------------------------------------------------------------------------------------------------
	sudo apt-get install p0f -yqq
	p0f -L #LISTENING ALL THE INTERFACES
	p0f -i eth0 -p -o /tmp/p0f.log # one interface and logging, -p promiscous mode
	p0f -r /tmp/dump.pcap -o dump-result.log # analyze pcap file
	----------------------------------------------------------------------------------------------------
	#ZIP Password Cracking Windows
	>zip2john.exe test.zip > test.hash #generate the hash with zip2john
	>type test.hash
	>john.exe --pot=test.pot --wordlist=\tmp\wordlists\Passwords\Common-Credentials\10-million-password-list-top-1000000.txt