chore: sync ink-node with latest polkadot-sdk main branch#9
Merged
Conversation
d1d6c25 to
0113cea
Compare
cmichi
approved these changes
Jun 6, 2025
cmichi
added a commit
to use-ink/docker-images
that referenced
this pull request
Jun 25, 2025
Follow-up to `ink-node` 0.43.3, specifically use-ink/ink-node#9.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR upgrades
ink-nodeto track the latestpolkadot-sdkmain branch instead of using thestable2503release.There are two main reasons for this:
Missing runtime API:
The new
get_storage_var_keyruntime API [pallet-revive] add get_storage_var_key for variable-sized keys paritytech/polkadot-sdk#8274 is not included in the 2503 release. It is expected in2506, but in the meantime, having it available inink-nodewill help tooling teams test against it. Requested by the Dedot team.This also resolves Transaction stuck in broadcasted status when using
polkadot-api#10, where transactions sent usingpolkadot-apiwere stuck in the broadcasted state. By syncing with the latest changes inpolkadot-sdk, this issue is resolved.