From bf536d0cb7e76320fb1cafb759f5be45b9a1647a Mon Sep 17 00:00:00 2001 From: Tuan Pham Anh Date: Fri, 26 May 2023 00:03:41 +0700 Subject: [PATCH] add note `wasm cache in snapshot` in doc https://github.com/notional-labs/cosmosia/issues/263 --- docs/snapshot_usage.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/snapshot_usage.md b/docs/snapshot_usage.md index a3c4bfcb..938ae168 100644 --- a/docs/snapshot_usage.md +++ b/docs/snapshot_usage.md @@ -27,7 +27,16 @@ sed -i -e "s/^app-db-backend *=.*/app-db-backend = \"pebbledb\"/" $node_home/con ``` ### Note -Using this [workaround](pebbledb.md) when upgrading a node running PebbleDB + +- upgrading a node running PebbleDB + + Using this [workaround](pebbledb.md) when upgrading a node running PebbleDB + +- wasm cache in snapshot + + there is `MsgExecuteContract Non-determinism` bug on different CPUs. See [more](https://injective.notion.site/Injective-MsgExecuteContract-Non-determinism-ac4411a44e3e4f2aa33e7fe5d8f0db30). + Fix it by removing the wasm cache from snapshot + ### Special chains Some chains require building differently