Skip to content
This repository has been archived by the owner on Feb 21, 2022. It is now read-only.

Bump Cumulus, Polkadot, and Substrate #105

Merged
merged 10 commits into from
Nov 11, 2021

Conversation

HCastano
Copy link
Contributor

@HCastano HCastano commented Nov 8, 2021

This is ready for review, but I wouldn't merge it just yet. I haven't been able to get it
working locally with polkadot-launch due to an issue on the Polkadot side (paritytech/polkadot#4238).

Would partially close #102.

// Expected responses are OK.
AllowKnownQueryResponses<PolkadotXcm>,
// Subscriptions for version tracking are OK.
AllowSubscriptionsFrom<ParentOrSiblings>,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@KiChjang would you be able to explain what a Sibling is in the context of XCM?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No surprise here -- siblings are MultiLocations that have the same parent, as denoted by the definition MultiLocation { parent: 1, junctions: X1(_) }. It's equivalent to locating for a file under ../*, where .. is "up one level" (meaning parent) and "*" is the wildcard operator.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha, thanks!

@@ -558,7 +570,7 @@ parameter_types! {
}

/// No local origins on this chain are allowed to dispatch XCM sends/executions.
pub type LocalOriginToLocation = SignedToAccountId32<Origin, AccountId, RelayNetwork>;
pub type LocalOriginToLocation = ();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess this is something that we'll need to change for canvas.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, we'll need to definitely revisit our XCM settings after we a) learn more about what they actually do and b) determine how we actually want to use XCM in the context of Canvas

@HCastano HCastano requested a review from cmichi November 11, 2021 15:34
@HCastano
Copy link
Contributor Author

@cmichi there were some small changes with the new version bump, can you take another quick look?

@HCastano
Copy link
Contributor Author

I've tested this with polkadot-launch - I can deploy and interact with an ERC-20 contract, so I think we're good

/// The ID of this Parachain as registered on the Relay Chain.
///
/// TODO: When we register as a common good parachain this will need to change.
pub const PARA_ID: u32 = 12648430;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there is already a parachain id which @lovelaced assigned for the Rococo deployment?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Canvas on Rococo is 1002 - and as far as I understand common good chains should have a para ID 1000 <= x < 2000.

@HCastano HCastano merged commit 79f3cb6 into master Nov 11, 2021
@HCastano HCastano deleted the hc-bump-cumulus-and-friends-2021-11-08 branch November 11, 2021 17:19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Get Canvas running on Rococo again
4 participants