Questions tagged [upgrade]
The upgrade tag has no usage guidance.
41
questions
0
votes
0
answers
2
views
Invalid transaction & Transaction has a bad signature
I'm trying to adjust my implementation to the recent runtime changes
CheckMetadataHash. I added the mode in the transaction and both the metadatahash and the mode parameter in the payload that is sign ...
- 1
0
votes
0
answers
27
views
Error E0433: Failed to Resolve metadata_ir in the Crate Root When Using decl_runtime_apis! Macro
When upgrading polkadot-sdk from v1.2.0 to v1.3.0 I am getting the following compile error.
I am encountering a compile error upgrading polkadot-sdk from v1.2.0 to v1.3.0 . The error message is as ...
- 778
1
vote
1
answer
24
views
How to manage compatibility of changing inherents between versions?
Basically, the title. What are the strategies around updating inherents over time and maintaining backwards-compatibility? How would I for example, take one inherent's InherentData, and update its ...
- 556
1
vote
1
answer
38
views
Upgrade parachain collator binary from polkadot-sdk v0.9.29 to v1.1.0, failed to launch with error 'Invalid argument: column families not opened'
We're running a parachain on Polkadot Relaychain. The parachain collator binary is built based on polkadot-sdk v0.9.29
When we try to upgrade binary to a new version which is built based on polkadot-...
- 25
0
votes
1
answer
25
views
No matching package named 'evm-gasometer found'
My node is on the substrate branch polkadot-v0.9.19. I have bumped it to polkadot-v0.9.22. After bumping the version I am trying to build the node in release mode using the following command.
cargo ...
- 45
0
votes
1
answer
37
views
How to update the client with new chain spec?
By referring to this solution, it works properly unless there are modifications in the chain spec.
How to upgrade the client?
In my case, the chain spec file has been modified as I removed some ...
- 708
1
vote
0
answers
23
views
Denpendencies update from an old polkadot version
We have been using polkadot/substrate v0.9.42 version and want to catch up with the latest release (v1.6.0+). I'll make sure to check each version's release analysis on the polkadot.forum, but still I'...
- 383
1
vote
1
answer
45
views
Why do I need to call the upgrade_account in the balance pallet?
With the introduction of version 0.9.42, the logic of how balances work in Substrate changed. This version upgrade introduced a new extrinsic called upgrade_account. The fee_frozen attribute of the ...
1
vote
0
answers
44
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
63
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 ...
- 769
2
votes
1
answer
70
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 ...
- 556
0
votes
1
answer
272
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
50
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
94
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. ...
- 115
0
votes
1
answer
71
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 ...
