From f9f7769b256d12d912933296dbede587735e0d6f Mon Sep 17 00:00:00 2001
From: Alexander Demidko <dralexthk@gmail.com>
Date: Mon, 25 Jun 2018 17:08:04 +0300
Subject: [PATCH] Hierarchical tree update

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index f6f91c6..dbe8378 100644
--- a/README.md
+++ b/README.md
@@ -82,7 +82,7 @@ In this demo application the state is implemented as an hierarchical key-value t
 Such trusted location is provided by the Tendermint consensus engine. Cluster nodes reach consensus not only over the canonical order of transactions, but also over the Merkle root of the state – `app_hash` in Tendermint terminology. The client can obtain such Merkle root from any node in the cluster, verify cluster nodes signatures and check that more than 2/3 of the nodes have accepted the Merkle root change – i.e. that consensus was reached.
 
 <p align="center">
-<img src="images/hierarchical_tree.png" alt="Hierarchical tree" width="625px"/>
+<img src="images/hierarchical_tree_basic.png" alt="Hierarchical tree" width="691px"/>
 </p>
 
 ### Computations correctness