diff --git a/.gitbook/assets/TAP Trees.png b/.gitbook/assets/TAP Trees.png
new file mode 100644
index 00000000..98ac9ef6
Binary files /dev/null and b/.gitbook/assets/TAP Trees.png differ
diff --git a/the-lightning-network/taproot-assets/taproot-assets-protocol.md b/the-lightning-network/taproot-assets/taproot-assets-protocol.md
index 1ced0843..79d62761 100644
--- a/the-lightning-network/taproot-assets/taproot-assets-protocol.md
+++ b/the-lightning-network/taproot-assets/taproot-assets-protocol.md
@@ -160,7 +160,9 @@ Creating assets requires a single on-chain taproot transaction, in which there i
Using this methodology, funds are allocated to account holders, represented as leafs in the sparse Merkle sum tree, but the ability to make such internal transfers is limited to the owner of the internal taproot private key(s).
-
+
+
+
Overview over the various tree structures used in Taproot Assets
