From 69b301ee4086ebe7a020a7f84f714d8a1bc55466 Mon Sep 17 00:00:00 2001 From: mpoke Date: Thu, 30 Nov 2023 14:28:33 +0100 Subject: [PATCH] fix SDK link --- STATE-COMPATIBILITY.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/STATE-COMPATIBILITY.md b/STATE-COMPATIBILITY.md index 1819aaf981..b62c00c7a4 100644 --- a/STATE-COMPATIBILITY.md +++ b/STATE-COMPATIBILITY.md @@ -56,7 +56,7 @@ To avoid these problems, let's now examine how these hashes work. **Note:** The following explanation is simplified for clarity. An app hash is a hash of hashes of every store's Merkle root that is returned by ABCI's `Commit()` from Cosmos-SDK to CometBFT. -Cosmos-SDK [takes an app hash of the application state](https://github.com/osmosis-labs/cosmos-sdk/blob/5c9a51c277d067e0ec5cf48df30a85fae95bcd14/store/rootmulti/store.go#L430), and propagates it to CometBFT which, in turn, compares it to the app hash of the rest of the network. +Cosmos-SDK [takes an app hash of the application state](https://github.com/cosmos/cosmos-sdk/blob/v0.47.6/store/rootmulti/store.go#L468), and propagates it to CometBFT which, in turn, compares it to the app hash of the rest of the network. Then, CometBFT ensures that the app hash of the local node matches the app hash of the network. ### LastResultsHash