Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update v1.11 proposal #1539

Merged
merged 3 commits into from
Sep 18, 2023
Merged

Update v1.11 proposal #1539

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6514c5f
change upgrade block
liorbond Sep 18, 2023
2f24aa3
update version
toml01 Sep 18, 2023
f7dceea
explanation
toml01 Sep 18, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/proposals/v1.11.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# Secret Network v1.11 Upgrade

This proposal recommends that the chain undergo a software upgrade to version v1.11 of the Secret Network codebase on secret-4 block **TODO**. The estimated time for the upgrade is **Tuesday, September 26, 2023, at ~2pm UTC**.
This proposal recommends that the chain undergo a software upgrade to version v1.11 of the Secret Network codebase on secret-4 block 10824000. The estimated time for the upgrade is **Tuesday, September 26, 2023, at ~2pm UTC**.

Since block times can vary significantly, we advise monitoring the chain for a more precise upgrade time. ETA monitor: [mintscan.io/secret/blocks/TODO](https://dev.mintscan.io/secret/blocks/TODO).
Since block times can vary significantly, we advise monitoring the chain for a more precise upgrade time. ETA monitor: [mintscan.io/secret/blocks/10824000](https://dev.mintscan.io/secret/blocks/10824000).

## Upgrade Highlights

Expand All @@ -17,7 +17,7 @@ Since block times can vary significantly, we advise monitoring the chain for a m
- On init, the creator can specify an admin address.
- The admin can migrate the contract to a new code ID.
- The admin can update or clear the admin address.
- The admins of contracts that were instantiated before v1.10 are hardcoded according to [proposal 262](https://github.com/scrtlabs/SecretNetwork/blob/ab1852727/docs/proposals/hardcode-admins-on-v1.10.md).
- The admins of contracts that were instantiated before v1.11 are hardcoded according to [proposal 262](https://github.com/scrtlabs/SecretNetwork/blob/ab1852727/docs/proposals/hardcode-admins-on-v1.10.md) (this proposal was originally called v1.10, hence prop. 262 referenced it's original version name).
- Hardcoded admins can only be updated/cleared with a future gov proposal.
- When the new `MsgMigrateContract` is invoked, the `migrate()` function is being called on the new contract code, where the new contract can optionally perform state migrations. See usage example [here](https://github.com/scrtlabs/SecretNetwork/blob/139a0eb18/cosmwasm/contracts/v1/compute-tests/migration/contract-v2/src/contract.rs#L37-L43).
- Fixed a scenario where the enclave's light client might fail a valid node registration transaction.
Expand Down