From 2f00199a3ea4dc9493b85f9b4d8b55fcd862a85a Mon Sep 17 00:00:00 2001 From: Marcel Moura Date: Mon, 8 Jul 2024 10:53:34 -0300 Subject: [PATCH] fixup! chore: add upgrade guide for v.1.5 Co-authored-by: Guilherme Dantas --- docs/upgrade_to_1_5.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/upgrade_to_1_5.md b/docs/upgrade_to_1_5.md index 5adb0f2f0..527fdbf51 100644 --- a/docs/upgrade_to_1_5.md +++ b/docs/upgrade_to_1_5.md @@ -35,15 +35,14 @@ This is the simplest way to perform the upgrade. In order to do so, just update the application configuration considering [what has changed](#what-has-changed) and upgrade the version of the Cartesi Rollups Node as usual. -For more details about hot to deploy an application, please refer to the [deployment process](https://docs.cartesi.io/cartesi-rollups/1.3/deployment/introduction/#deployment-process) options available in the Cartesi documentation. +For more details about how to deploy an application, please refer to the [deployment process](https://docs.cartesi.io/cartesi-rollups/1.3/deployment/introduction/#deployment-process) options available in the Cartesi documentation. > [!CAUTION] > A redeployment will create a new instance of the application from scratch. > All previous inputs, outputs and claims will remain associated to the previous application address, including any funds locked in the application contract. Alternatively, the _Authority_ owner may choose to replace the _History_ being used by the application's _Authority_. -This path allows inputs, outputs and locked funds to remain unchanged. -This process is a little bit more involved and is described in the next section. +This process allows inputs, outputs and locked funds to remain unchanged, but is a little bit more involved. It is described in the next section. > [!NOTE] > A new _History_ will contain no claims. @@ -74,7 +73,7 @@ First, the address of the new _History_ instance should be calculated. > - `HISTORY_FACTORY_ADDRESS`: address of a valid _HistoryFactory_ instance > - `AUTHORITY_ADDRESS`: address of the _Authority_ instance being used by the application -> [!TIP ] +> [!TIP] > A _HistoryFactory_ is deployed at `0x1f158b5320BBf677FdA89F9a438df99BbE560A26` for all supported networks (Ethereum, Optimism, Arbitrum, Base and their respective Sepolia-based tesnets). In order to calculate the address of a new history contract, one can call the view function [`calculateHistoryAddress(address,bytes32)`](https://github.com/cartesi/rollups-contracts/blob/e8a2d82bc51167086e7928b9a6aced0d62c96cf8/onchain/rollups/contracts/history/HistoryFactory.sol#L35-L38).