[XCM]: Improved fee mechanism #105
Conversation
franciscoaguirre
changed the title
Co-authored-by: Adrian Catangiu <adrian@parity.io>
Co-authored-by: Adrian Catangiu <adrian@parity.io>
Co-authored-by: Adrian Catangiu <adrian@parity.io>
Co-authored-by: Adrian Catangiu <adrian@parity.io>
|
/rfc propose |
|
Hey @franciscoaguirre, here is a link you can use to create the referendum aiming to approve this RFC number 0105. Instructions
It is based on commit hash dbda71ff556635b523656c8e8af42686d5515372. The proposed remark text is: |
|
Voting for this referenda is ongoing. Vote for it here |
|
PR can be merged. Write the following command to trigger the bot
|
|
/rfc process 0x39efd93063aeaef13afdb2135a775fec4d87fe3ed51e9bf122bc73a336acd509 |
|
The on-chain referendum has approved the RFC. |
Implements [RFC#105](polkadot-fellows/RFCs#105) which, at the time of this PR, has not been approved yet. Some aspects might be changed as a result of discussion. ## TODO - [x] Add new instruction and use it in conversion functions - [x] Implement in xcm-executor - [x] Setup for xcm-executor unit tests - [x] Actual xcm-executor unit tests - [x] Happy path - [x] Unhappy path - [x] Emulated tests - [x] Asset hub westend - [x] Asset hub rococo - [x] Benchmarks - [x] Dummy values - [x] Actual benchmarks - [x] PRDoc --------- Co-authored-by: command-bot <> Co-authored-by: Adrian Catangiu <adrian@parity.io>
Moved from polkadot-fellows/xcm-format#53.
The idea is to extend the current XCM fee mechanism to support in principle delivery fees, but potentially other types of fees as well.
This is accomplished by having two additions:
PayFeesinstructionfeesregister, where fees go and stay there until the end of execution. Crucially, separate from theholdingregister