Questions tagged [upgrade]
The upgrade tag has no usage guidance.
34
questions
1
vote
0
answers
35
views
How do I monitor runtime upgrades with sidecar?
We need to monitor the spec version of the block, that is, the runtime upgrade.
Of course, we know that openGov's suggestions will determine the upgrade.
So we're going to run this guide to monitor ...
- 45
2
votes
2
answers
53
views
Steps for migration from polkadot-v0.9.30 to polkadot-v0.9.43/v1.0.0
At Ternoa we are trying to do a long jump from polkadot-v0.9.30 to polkadot-v0.9.43 or the latest. We would like to get some suggestions here if someone or some projects already experienced this much ...
- 759
2
votes
1
answer
49
views
What is the new process to follow Substrate releases for the polkadot-sdk monrepo
In the Substrate repo, it was common to update to polkadot release-branches to version the Substrate crates. Will this still be the case for chains based on the monorepo version of Substrate? Will ...
- 530
0
votes
0
answers
114
views
error[E0277]: the trait bound is not satisfied for Deserialize<'_>` and Serialize<'_>`
Hi I am currently upgrading our runtime to Polkadot 1.0 but when I try to build it get the following errors
error[E0277]: the trait bound `MintingRateInfo: Deserialize<'_>` is not satisfied
...
- 325
3
votes
0
answers
43
views
After using set_code_hash to upgrade contract, when decode on the new Storage，why there wont has error of "Not enough data to fill buffer"
I'm learning how to upgrade ink! contract，and have some question：
Eg：old contractA, storage define is
#[ink(storage)
pub struct MyContract {
a: u32,
}
new contractB，storage define is
#[ink(...
- 31
3
votes
1
answer
68
views
babe-worker failed after upgrade to 0.9.42
After upgrading to 0.9.42, we have ERROR tokio-runtime-worker sc_service::task_manager: Essential task babe-worker failed. Shutting down service. error starting the node using cargo run -- --dev. ...
0
votes
1
answer
39
views
frontier template upgrade to polkadotv0.9.38 but using Babe instead of Aura
I've upgraded the frontier-node-template to substrate polkadot-v0.9.38, I've fixed all issues in runtime, migrated my code as well.
But since last few days, I'm stuck in converting service.rs file in ...
1
vote
1
answer
29
views
Upgrade runtime parachain when relay is local
I know that to upgrade a runtime of a parachain, we need to go to parachainSystem.
But when we use a local relay chain, how could we access to the polkadot-js of the parachain ?
- 73
0
votes
0
answers
69
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, ...
2
votes
1
answer
28
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 ...
- 503
1
vote
1
answer
46
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 ...
- 503
0
votes
1
answer
16
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 ...
- 503
1
vote
1
answer
55
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
39
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 ...
- 269
3
votes
1
answer
98
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 ...
- 361
0
votes
1
answer
25
views
parachainSystem.ValidationFunctionStored
The validation function has been scheduled to apply.
What does this event mean?
When my upgrade will be executed?
- 509
5
votes
3
answers
456
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?
- 1,421
3
votes
0
answers
58
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 ...
- 105
5
votes
1
answer
135
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 ...
- 1,090
1
vote
1
answer
26
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 ...
- 105
2
votes
1
answer
76
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....
- 105
1
vote
0
answers
36
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 ...
- 105
1
vote
0
answers
24
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 ...
- 131
0
votes
1
answer
102
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
- 33
1
vote
1
answer
203
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"` ...
- 63
0
votes
1
answer
42
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 [email protected] output. Enacting the runtime upgrade ends ...
- 93
3
votes
1
answer
77
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 ...
- 31
3
votes
1
answer
194
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 ...
- 291
8
votes
3
answers
188
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 ...
- 167
1
vote
1
answer
115
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 ...
- 93
1
vote
1
answer
97
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?
- 999
11
votes
2
answers
262
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)
- 999
0
votes
1
answer
72
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 & ...
- 21
5
votes
1
answer
87
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,610