Skip to content

Commit

Permalink
fixup! chore: add upgrade guide for v.1.5
Browse files Browse the repository at this point in the history
Co-authored-by: Guilherme Dantas <[email protected]>
  • Loading branch information
marcelstanley and guidanoli authored Jul 8, 2024
1 parent 92b8b68 commit 2f00199
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions docs/upgrade_to_1_5.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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).
Expand Down

0 comments on commit 2f00199

Please sign in to comment.