Questions tagged [upgrade]
The upgrade tag has no usage guidance.
26
questions
0
votes
0
answers
58
views
Runtime Upgrade: Scheduled runtime upgrade transaction halts network
We are trying to upgrade our runtime on Rococo with a scheduled parachainSystem::authorizeUpgrade transaction, that you can find in the image below.
When testing the runtime upgrade on zombienet, ...
1
vote
1
answer
24
views
How to get the call `authorize_upgrade` from `cumulus_pallet_parachain_system` inside another pallet?
I would like to schedule the dispatch call authorize_upgrade inside a custom pallet. For this I need the call enum variant of the cumulus_pallet_parachain_system pallet. How can I get this? Via the ...
- 239
0
votes
1
answer
30
views
What root dispatches are absolutely necessary to run a parachain?
I am currently developing an alternative to Sudo and Democracy. I wish to have a sudo key account, which is allowed to upgrade the chain, but only after a three month review period, the upgrade can ...
- 239
0
votes
1
answer
13
views
How to force runtime upgrades only after an enactment period of three months with the sudo pallet?
I would like to use the sudo pallet instead of the democracy pallet.
Now I would like to force the sudo user to wait three months until a runtime upgrade can be applied. So, that there is no way to ...
- 239
1
vote
1
answer
35
views
Upgrade from substrate node tag v3.0.0 to last version
We are maintaining a blockchain based on substrate node tag v3.0.0. Now we upgraded to substrate branch polkadot-v0.9.27. (We need to upgrade to support native smart contracts with Ink! with the last ...
1
vote
1
answer
27
views
tokenDecimals = 10 Causes Astronomical Fees - How To Change tokenDecimals On A Running Chain?
We have started a test chain with tokenDecimals = 10 in the chain spec JSON. The chain is running beautifully BUT fees are astronomical. For example, it takes 2.6 Billion to run for council. We are ...
- 153
3
votes
1
answer
75
views
Polkadot 29 update - try-runtime feature (trait bounds error)
We are doing upgrade to polkadot version 29. Everything works fine until we run the command
cargo build -r --features try-runtime
we got error trait bounds. In this version there was change from ...
- 229
0
votes
1
answer
24
views
parachainSystem.ValidationFunctionStored
The validation function has been scheduled to apply.
What does this event mean?
When my upgrade will be executed?
- 183
5
votes
3
answers
403
views
How can I start a function automatically after a certain period of time?
I want to start a function automatically after a certain period of time in our chain. How can I do it?
- 932
2
votes
0
answers
51
views
Forkless upgrade from v0.9.16 to v0.9.17 fails
I am working on a Substrate node update.
I have a node from Substrate repository that runs on v0.9.16. When I am executing forkless upgrade to v0.9.17 via polkadot apps (v0.121.2-89-x) it fails and I ...
3
votes
1
answer
108
views
sp_trie::recorder::Recorder does not live long enough when upgrading para-chain project from polkadot-v0.9.28 to polkadot-v0.9.29
I was upgrading a para chain from polkadot version 0.9.28 to v0.9.29 when I encountered a few suspicious looking build errors originating from deep inside substrate.
To eliminate the risk of some ...
- 447
1
vote
1
answer
21
views
Node client updates require where they should not be according to Polkadot's release notes
I am working on a Substrate node update.
I am following Polkadot's releases not to skip migrations.
Some node runtime updates require node client updates. This information can be found in Polkadot's ...
2
votes
1
answer
56
views
ink Smart Contract "dies" after the node runtime update
I am working on Substrate node update.
During the testing, I found out that the deployed smart contract (incrementer, tag: v3.0.0-rc4) "dies" during the node updates from:
v0.8.27 to v0.8....
1
vote
0
answers
32
views
Skipping node client's intermediate versions
The substrate node consists of 2 parts: runtime and outer node (or node client).
The Substrate has forkless upgrade functionality for the runtime updates. Sometimes node client should be updated first ...
0
votes
0
answers
19
views
upgrade custom chain to 0.9.24, rpc-client/src/main.rs report "no `AuthorClient` in `author`"
report "no AuthorClient in author" in rpc-client/src/main.rs when i upgrade chain to 0.9.24
report "add dyn keyword before this trait" if i change to AuthorApiClient.
does ...
- 71
0
votes
1
answer
62
views
How to upgrade substrate polkadot-v0.9.20 version to polkadot-v0.9.24?
How to upgrade substrate polkadot-v0.9.20 to v0.9.24?
Thank you
- 13
1
vote
1
answer
151
views
FIX: failed to select a version for the requirement `<crate = "version>"`
documenting an error and a fix for others. While updating a substrate repository I was getting an error:
error: failed to select a version for the requirement `wasmtime = "^0.38.0"` ...
- 33
0
votes
1
answer
33
views
Hash for an authorize-enact runtime upgrade?
Attempting a parachain runtime upgrade using .runtimes.compact.subwasm.parachain_authorize_upgrade_hash and .runtimes.compact.wasm from the srtool-cli@v0.8.0 output. Enacting the runtime upgrade ends ...
- 83
1
vote
1
answer
58
views
Exported method `TryRuntime_on_runtime_upgrade` is not found
cargo run --features try-runtime try-runtime \
--execution Native \
--chain dev \
on-runtime-upgrade \
live \
--uri ws://xxxxxxxx
I implemented try-runtime according to the ...
- 11
2
votes
1
answer
77
views
RPC node encounter `Cannot create a runtime error=Other(\"runtime requires function imports which are not present on the host:` after upgrade
I got a problem with upgrading my chain
I've upgraded my chain from version A (Client+runtime) to version B (Client+runtime). I remove some host functions in client version B because runtime version B ...
- 271
7
votes
3
answers
163
views
Node startup message missing after upgrade to Polkadot v0.9.23
After upgrading to Polkadot v0.9.23 from v0.9.16, I am missing the default "start up" message (WS/RPC connections, hardware, para-id etc, see below) when initiating the node client, both for ...
- 87
1
vote
1
answer
90
views
Calculating code hash for an authorize-enact style runtime upgrade?
How to calculate the code hash for fn authorize_upgrade of cumulus_pallet_parachain_system?
As per crate substrate-runtime-proposal-hash been trying BLAKE2B32(0x0103 | BLAKE2B32(wasm_bytes)) with no ...
- 83
0
votes
1
answer
72
views
Extrinsic Failed - Contract code rejected while implementing upgradable contract
I was following this example of ink! upgradable smart contract. After I uploaded the upgradable_contract.contract (Step 4 in the link), I got the following error:
How can I fix it?
- 779
10
votes
2
answers
205
views
How to upgrade a smart contract logic?
I deployed a smart contract to a substrate chain. How can I upgrade the smart contract's logic to a newer version?
Edit: I'm using ink! and deployed on Shibuya (Astar testnet)
- 779
0
votes
1
answer
48
views
Node discovery (Kademlia) not working after upgrading chain from v2.0 -> v3.0
I am experiencing some issues with node discovery after upgrading from substrate 2.0 to substrate 3.0
After upgrading our chain from using substrate 2.0 to substrate 3.0 (Upgrading the client & ...
- 11
3
votes
1
answer
74
views
What test should I run before performing a runtime upgrade?
If I'm running a chain in production and I've upgraded some pallets in my runtime, what steps do I need to take to make sure my runtime will run without fail when it is included in my live chain?
- 2,202