Skip to main content

Questions tagged [upgrade]

The tag has no usage guidance.

Filter by
Sorted by
Tagged with
0 votes
0 answers
25 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 ...
Yatusabes's user avatar
  • 776
1 vote
1 answer
23 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 ...
Justin Frevert's user avatar
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-...
Brian Wu's user avatar
0 votes
1 answer
24 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 ...
RRR's user avatar
  • 43
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 ...
CocDap's user avatar
  • 678
1 vote
0 answers
21 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'...
Kailai's user avatar
  • 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 ...
Adel Golghalyani's user avatar
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 ...
hs1228's user avatar
  • 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 ...
Immanuel John's user avatar
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 ...
Justin Frevert's user avatar
0 votes
1 answer
261 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 ...
chexware's user avatar
  • 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(...
ruarua's user avatar
  • 31
3 votes
1 answer
91 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. ...
Benjamin Gallois's user avatar
0 votes
1 answer
63 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 ...
Zubair Buriro's user avatar
1 vote
1 answer
32 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 ?
Matthiew's user avatar
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 ...
Chralt's user avatar
  • 543
1 vote
1 answer
54 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 ...
Chralt's user avatar
  • 543
0 votes
1 answer
17 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 ...
Chralt's user avatar
  • 543
1 vote
1 answer
61 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 ...
Fernando Ruscitti's user avatar
1 vote
1 answer
41 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 ...
KathrynColleen's user avatar
3 votes
1 answer
107 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 ...
Michal Danco's user avatar
0 votes
1 answer
29 views

parachainSystem.ValidationFunctionStored

The validation function has been scheduled to apply. What does this event mean? When my upgrade will be executed?
rust.dev's user avatar
  • 519
5 votes
3 answers
474 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?
Deepak Chaudhary's user avatar
3 votes
0 answers
59 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 ...
Andrei Navoichyk's user avatar
5 votes
1 answer
137 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 ...
Simson's user avatar
  • 1,201
1 vote
1 answer
28 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 ...
Andrei Navoichyk's user avatar
2 votes
1 answer
78 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....
Andrei Navoichyk's user avatar
1 vote
0 answers
37 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 ...
Andrei Navoichyk's user avatar
1 vote
0 answers
25 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 ...
Smith's user avatar
  • 141
0 votes
1 answer
111 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
oscar's user avatar
  • 33
1 vote
1 answer
227 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"` ...
DJJ's user avatar
  • 63
0 votes
1 answer
52 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 ...
user1813's user avatar
  • 103
3 votes
1 answer
80 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 ...
junyuan wei's user avatar
3 votes
1 answer
336 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 ...
Daniel Lam's user avatar
8 votes
3 answers
199 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 ...
0x5hmoo's user avatar
  • 189
1 vote
1 answer
122 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 ...
user1813's user avatar
  • 103
2 votes
1 answer
105 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?
Minh Mốc's user avatar
  • 1,009
11 votes
2 answers
282 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)
Minh Mốc's user avatar
  • 1,009
0 votes
1 answer
80 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 & ...
thduke's user avatar
  • 21
5 votes
1 answer
95 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?
Sacha Lansky's user avatar
  • 2,640