-
Notifications
You must be signed in to change notification settings - Fork 107
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
Update polkadot dependencies #417
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, few minor comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, just few questions 💪
// We don't track any teleports. | ||
() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the reasoning behind that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By design, we don't support teleportation. Only reserve-backed transfers, which doesn't require trust in the other chain.
type IsReserve = NativeAsset; | ||
type IsTeleporter = (); | ||
type IsTeleporter = NativeAsset; // <- should be enough to allow teleportation of ROC |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here we support teleportation though?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, will fix!
type Barrier = Barrier; | ||
type Weigher = FixedWeightBounds<UnitWeightCost, Call>; | ||
type Trader = UsingComponents<IdentityFee<Balance>, RococoLocation, AccountId, Balances, ()>; | ||
type ResponseHandler = (); // Don't handle responses for now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the reason for this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No idea. 😅
XCM documentation is sparse and a lot of the new XCM code I copy-pasted from the Cumulus parachains at https://github.com/paritytech/cumulus/tree/master/polkadot-parachains (statemint, rococo examples, etc)
Updated Polkadot/Cumulus dependencies to polkadot v0.9.4. This also required us to update GSRPC to get metadata V13 changes.
Note that XCM verification & testing is pushed out to a follow-up PR given the scope-creep that has arisen so far.
E2E tests mostly pass. For the tests that fail, there is an unrelated & pre-existing issue in the commitment relayer which results in some commitments getting ignored and are not being passed on to Ethereum.
Changes:
transfer
pallet. We no longer need a custom pallet to allow users to initiate XCM transfers.