diff --git a/.github/workflows/mdbook.yml b/.github/workflows/mdbook.yml
index 7826e71..41ac32c 100644
--- a/.github/workflows/mdbook.yml
+++ b/.github/workflows/mdbook.yml
@@ -36,11 +36,13 @@ jobs:
         id: pages
         uses: actions/configure-pages@v4
       - name: Build with mdBook
-        run: mdbook build
+        run: |
+          cd book
+          mdbook build
       - name: Upload artifact
         uses: actions/upload-pages-artifact@v3
         with:
-          path: ./book
+          path: ./book/book
 
   deploy:
     environment:
diff --git a/README.md b/README.md
index b7fb583..14a67a8 100644
--- a/README.md
+++ b/README.md
@@ -1,3 +1,5 @@
 # POD2
 
-TODO
+Specification can be found at the [`book`](https://github.com/0xPARC/pod2/tree/main/book) directory, a live rendered version at: https://0xparc.github.io/pod2/
+
+Requires Rust nightly: `rustup override set nightly`.
diff --git a/book/book.toml b/book/book.toml
index e17c20c..cf50c6d 100644
--- a/book/book.toml
+++ b/book/book.toml
@@ -4,3 +4,6 @@ language = "en"
 multilingual = false
 src = "src"
 title = "POD2-docs"
+
+[output.html]
+default-theme = "light"
diff --git a/book/src/img/merkletree0.png b/book/src/img/merkletree0.png
new file mode 100644
index 0000000..87db459
Binary files /dev/null and b/book/src/img/merkletree0.png differ
diff --git a/book/src/img/merkletree1.png b/book/src/img/merkletree1.png
new file mode 100644
index 0000000..90e7a19
Binary files /dev/null and b/book/src/img/merkletree1.png differ
diff --git a/book/src/merkletree.md b/book/src/merkletree.md
index 0696c74..9c6bbaf 100644
--- a/book/src/merkletree.md
+++ b/book/src/merkletree.md
@@ -1 +1,48 @@
 # MerkleTree
+
+In the POD system, MerkleTrees are used to store the key-values of the POD.
+
+- Each leaf contains a touple of `key` and `value`
+- Leaf position is determined by the `key` content binary representation (little-endian)
+
+![](img/merkletree0.png)
+
+So for example, suppose we have the following data in a POD:
+```js
+{
+	id: "11000...",
+	kvs : {
+		idNumber: "424242",
+		dateOfBirth: 1169909384,
+		userPk: 9876543210, // target user of this POD
+		_signerPk: 1234567890, // signer of the POD
+	}
+}
+```
+
+The merkletree will contain the key values from the `kvs` field.
+
+Suppose that the binary representation of the key `userPk` is `1011...`. This uniquely defines the leaf position that contains the public key of the authenticated user.
+
+![](img/merkletree1.png)
+
+
+## Proofs of inclusion and non-inclusion
+Merkle proofs contain the siblings along the path from the leaf to the root, where the leaf position is determined by the key binary representation. 
+
+Since leaf positions are deterministic based on the key, the same approach is used for non-inclusion proofs, where it can be proven that a key is not in the tree, and furthermore, that a value is not in the tree (although the key exists):
+- Proving that the key does not exist in the tree is achieved by generating the merkle-proof for the specific key, and showing that the (virtual) leaf is empty - this is, showing that going down the path of the non-existing key, there is a leaf with a different key, meaning that the non-existing key has not been inserted in the tree.
+- Proving that a value is not in the tree (although the key exists) is achieved by generating the merkle-proof for the specific key, and showing that the leaf exists but it has a different value than the one being proved.
+
+
+
+## Encoding
+> TODO: how key-values, nodes, merkle-proofs, ... are encoded.
+
+## Temporary first version
+The first iteration of the implementation uses a hash of the key-values concatenated, with the idea of replacing it by the MerkleTree approach described above.
+
+
+## Resources
+- [https://docs.iden3.io/publications/pdfs/Merkle-Tree.pdf](https://docs.iden3.io/publications/pdfs/Merkle-Tree.pdf)
+- [https://eprint.iacr.org/2018/955](https://eprint.iacr.org/2018/955)