Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
195 lines (135 sloc) 6.65 KB


This repo contains the jupyter notebooks for Optech's Schnorr/Taproot workshops.


For the purposes of demonstrating the features of schnorr and taproot to the Bitcoin developer community, we have developed an extended Python library on top of Pieter Wuille's Taproot Bitcoin Core branch, which provides Python classes and methods to build more sophisticated Taproot transactions and various schnorr signature schemes for preliminary evaluation.

Our Taproot/Schnorr library is an extension of the Bitcoin python test framework, located in the dedicated Optech Bitcoin Taproot Branch.

Note: This Library is intended for demonstrative and educational purposes only.


Do not run test instances of bitcoind on the same machine that you store your Bitcoin private keys. These notebooks shouldn't interfere with your standard bitcoin data directory, but why risk it?


It will be useful to have some background on schnorr and taproot before running through the exercises in this repository.



Output Descriptors


Clone this (bitcoinops/taproot-workshop) repository

$ git clone

Build a taproot-supporting bitcoind

These workbooks require a bitcoind built from the Optech Taproot V0.1.4 branch which supports schnorr and taproot.


Clone the bitcoinops/bitcoin repository in a separate directory from this taproot-workshop repository:

$ git clone

Note the path where you cloned the bitcoinops/bitcoin repository and add it to the config.ini file in your taproot-workshop repository. For example, set:


Checkout the Optech taproot branch in the bitcoinops/bitcoin repository, which is tagged as Taproot_V0.1.4:

$ git checkout Taproot_V0.1.4

Build the Optech Taproot branch of bitcoind locally. See the build documentation ( in the Bitcoin Core repository docs directory for additional documentation on building bitcoind on Unix, macOS, or Windows.

No need to run bitcoind or download the mainchain or testnet blockchain. We will run in regtest mode and spawn node instances via scripts.

Python 3

Verify you have python3 installed:

$ python3 --version

If not, you should install Python 3.


$ sudo apt-get install python3

macOS (using homebrew):

$ brew install python3


Python Dependencies

This workshop uses some Python dependencies, particularly jupyter-notebook. To keep dependencies local to the project, you should create and activate a virtual environment. You can skip this step if you're happy to install the dependencies globally.

Make sure you are in your taproot-workshop repository folder.

$ python3 -m venv .venv && source .venv/bin/activate

(if you're using the csh or fish shells, replace .venv/bin/activate with .venv/bin/activate.csh or .venv/bin/

Install dependencies:

$ pip3 install -r requirements.txt

Ensure jupyter notebook is installed:

$ jupyter notebook --version

Jupyter notebook is a handy tool which allow us to run python code directly in an interactive document like this one. The workshop materials are built directly with jupyter .ipynb files, which you can open once you have jupyter installed.

Start jupyter notebook to see exercises:

$ jupyter notebook

Jupyter will start a notebook server in your terminal, and provide a link for your browser from which you can interact with notebook files. If your browser doesn't automatically open the notebook file explorer, click on the link provided by jupyter notebook server in the terminal.

  • Click on the 0.1-test-notebook.ipynb notebook.
  • Verify that 0.1-test-notebook.ipynb passes all checks.

After you have run the 0.1 example exercises, please also run through the 0.2-elliptic-curve-math.ipynb and 0.3-tagged-hashes.ipynb notebooks and exercises before the workshop.

Notebooks 1.x, 2.x, etc will be covered during the workshop. There is no need to run through those beforehand.

Stop the current running jupyter session using Control-C in the terminal.

After you have finished your jupyter session, you can deactivate the Python virtual environment with:

$ deactivate
You can’t perform that action at this time.