-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Fix weights on hard-coded XCM fragments #4144
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.
For now I think this is okay, but I do think some kind of holistic approach in solving the weight fee payment problem is needed.
An idea that I just came up with is to have something similar to version negotiation, we can have a storage item that stores the fee schedule for known parachains, and perhaps we could also have a new XCM instruction that specifically asks for this sort of data.
The main problem with that is that the fee schedule may be non-linear; for now it would work, and perhaps that's good enough. Another possibility is to have the UI discover and include the destination weight through an exported WASM of the |
* Fix weights on hard-coded XCM fragments * Formatting
* master: (73 commits) Fix XCM Teleport Benchmark (#4146) Allow Queries and Subscriptions (#4150) Fix weights on hard-coded XCM fragments (#4144) Bump spec versions (#4142) Bump libc from 0.2.104 to 0.2.105 (#4141) Enable bags-list pallet in polkadot (#4080) Move artifacts states into memory in PVF validation host (#3907) Introduce new Runtime API endpoint for fetching the validation data (#3728) export xcm_pallet config (#4116) Apply cargo fmt (#4122) remove logging from the check-dependent-* job (#4120) Remove stale migrations (#4107) Bump structopt from 0.3.23 to 0.3.25 (#4098) remove hardcoded pipeline scripts tag (#4109) Bump libc from 0.2.103 to 0.2.104 (#4099) some spelling fixes (#4088) polkadot: remove call filters on registrar pallets (#4093) Fix typos in docs (#4092) Rename Statemint where appropriate (#4087) bump substrate (#4091) ...
* Fix weights on hard-coded XCM fragments * Formatting
Fix for weights. Also adds dispatch variants for providing weight manually.
cc @shawntabrizi @KiChjang