-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Executing the Utility::batch_all()
method via XCM
#112
Comments
CC @ggwpez |
Good catch! |
fellowship-merge-bot bot
added a commit
that referenced
this issue
Feb 2, 2024
We imported the runtimes into this repo at tag [`v1.1.0-rc2`](https://github.com/paritytech/polkadot-sdk/commits/v1.1.0-rc2/) but still merged stuff until they got removed in [#1731](paritytech/polkadot-sdk#1731). This re-applies all changes in that commit range [`v1.1.0-rc2..bf90cb0b`](paritytech/polkadot-sdk@v1.1.0-rc2...bf90cb0) checked in the SDK with `git log v1.1.0-rc2..bf90cb0b -- polkadot/runtime/`. Closes #112 Most changes got applied as part of #56, but two were missing: - paritytech/polkadot-sdk#1303 - <s>https://github.com/paritytech/polkadot-sdk/pull/1476</s> (reverted) <s>One [open Q](#67 (comment)) since there was a difference between [#1291](paritytech/polkadot-sdk#1291) and #67.</s> --------- Signed-off-by: Oliver Tale-Yazdi <[email protected]> Co-authored-by: fellowship-merge-bot[bot] <151052383+fellowship-merge-bot[bot]@users.noreply.github.com> Co-authored-by: Bastian Köcher <[email protected]> Co-authored-by: joe petrowski <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This RP paritytech/polkadot-sdk#1303 has removed restrictions related to
SafeCallFilter
, allowing actions such as sending XCM messages from Parachain and executing theUtility::batch_all()
method in the Relaychain. However, we've noticed thatSafeCallFilter
is still retained after the separation of polkadot-runtime and kusama-runtime from the polkadot-sdk into this new projectWas this an oversight in updating? I believe cross-chain invocations of
Utility::batch_all()
are a common practice and should not be restricted.The text was updated successfully, but these errors were encountered: