Add timeline to non-cooperative exit (#92)

* show vtxo tree with radix 4

* leaving.md:
- fix links to nomenclature
- add timeline to non-cooperative exit

Author: bordalix

website/docs/learn/leaving.md

@@ -11,22 +11,56 @@ Alice wants to leave the Ark and get her funds back on-chain. It requires an on-
 
 #### Timeline of events
 
-1. Alice tells ASP she wants to trade [VTXO](#vtxo) for UTXO
-2. ASP (with Alice) prepares next [Pool transaction](#pool-transaction-aka-ark-transaction):
+1. Alice tells ASP she wants to trade [VTXO](./nomenclature#vtxo) for UTXO
+2. ASP (with Alice) prepares next [Pool transaction](./nomenclature#pool-transaction-aka-ark-transaction):
    - an additional output is added, locked by `Alice`
-3. Alice creates a [Forfeit transaction](#forfeit-transaction-):
+3. Alice creates a [Forfeit transaction](./nomenclature#forfeit-transaction):
    - spends from VTXO (1) with `Alice + ASP`
    - adds connector output from Pool transaction (2) as input
    - signs it and send it to the ASP
-4. ASP broadcasts [Pool transaction](#pool-transaction-aka-ark-transaction)
+4. ASP broadcasts [Pool transaction](./nomenclature#pool-transaction-aka-ark-transaction)
 5. Alice has now a new UTXO
-6. For at most 4 weeks, Alice will be able to double spend her [VTXO](#vtxo), but if she does it, the ASP will have time (24 hours) to grab the funds from the [VTXO](#vtxo) to itself using the [Forfeit transaction](#forfeit-transaction-)
-
+6. For at most 4 weeks, Alice will be able to double spend her [VTXO](./nomenclature#vtxo), but if she does it, the ASP will have time (24 hours) to grab the funds from the [VTXO](./nomenclature#vtxo) to itself using the [Forfeit transaction](./nomenclature#forfeit-transaction)
 
 ### Non-cooperative exit
 
 If ASP is unresponsive, Alice can unilaterally exit revealing the branch of the Pool transaction that locks her funds.
 
 #### Timeline of events
 
-TBD
+1. Assuming a [VTXO](./nomenclature#vtxo) tree with radix of 2 and 8 [VTXOs](./nomenclature#vtxo):
+
+```mermaid
+flowchart TB
+   tx1(TX 1) --> tx2(TX 2)
+   tx1 --> tx3(TX 3)
+   tx2 --> tx4(TX 4)
+   tx2 --> tx5(TX 5)
+   tx3 --> tx6(TX 6)
+   tx3 --> tx7(TX 7)
+   tx4 --> v1(VTXO 1)
+   tx4 --> v2(VTXO 2)
+   tx5 --> v3(VTXO 3)
+   tx5 --> v4(VTXO 4)
+   tx6 --> v5(VTXO 5)
+   tx6 --> v6(VTXO 6)
+   tx7 --> v7(VTXO 7)
+   tx7 --> v8(VTXO 8)
+```
+
+2. Assuming VTXO 1 and 2 belong to Alice and Bob
+3. Alice reveals the [VTXO](./nomenclature#vtxo) tree to spend the [Shared Output](./nomenclature#shared-output-aka-shared-utxo).
+4. Alice doesn't need to reveal the entire tree, just enough to validate it:
+
+```mermaid
+flowchart TB
+   tx1(TX 1) --> tx2(TX 2)
+   tx1 --> tx3(TX 3)
+   tx2 --> tx4(TX 4)
+   tx2 --> tx5(TX 5)
+   tx4 --> v1(VTXO 1)
+   tx4 --> v2(VTXO 2)
+```
+
+5. Alice will need to wait 24 hours to be able to spend her [VTXO](./nomenclature#vtxo). This gives enough time to the ASP to prevent any double spend attempts by Alice.
+6. Bob can also spend his [VTXO](./nomenclature#vtxo) in 24 hours, or do nothing and maintain his [VTXO](./nomenclature#vtxo) on the Ark.

website/docs/learn/nomenclature.md

@@ -118,7 +118,7 @@ Different ASPs can use different ways for users to board their Ark.
 
 ### Shared output (aka Shared UTXO)
 
-- Represents a binary tree of transactions
+- Represents a tree of transactions
 - In an optimistic scenario, this tree is never revealed
 - Each leaf on this tree represents a VTXO
 
@@ -137,3 +137,19 @@ flowchart LR
     end
     shared --> tx1
 ```
+
+- Tree can have a radix higher than 2 (ex: radix 4)
+
+```mermaid
+flowchart LR
+    subgraph Onchain
+        shared(Shared output)
+    end
+    subgraph Virtual
+        tx1(TX 1) --> v1(VTXO 1)
+        tx1 --> v2(VTXO 2)
+        tx1 --> v3(VTXO 3)
+        tx1 --> v4(VTXO 4)
+    end
+    shared --> tx1
+```