Fix transaction payment runtime api (#6792)
The transaction payment runtime api used its own extrinsic generic parameter. This is wrong, because this resulted in using always the native extrinsic. If there was a runtime upgrade that changed the extrinsic in some way, it would result in the api breaking. The correct way is to use the `Extrinsic` from the `Block` parameter. This is on the node side the opaque extrinsic and on the runtime side the real extrinsic.
Showing
- substrate/bin/node/rpc/src/lib.rs 1 addition, 2 deletionssubstrate/bin/node/rpc/src/lib.rs
- substrate/bin/node/runtime/src/lib.rs 1 addition, 2 deletionssubstrate/bin/node/runtime/src/lib.rs
- substrate/frame/transaction-payment/rpc/runtime-api/src/lib.rs 2 additions, 3 deletions...rate/frame/transaction-payment/rpc/runtime-api/src/lib.rs
- substrate/frame/transaction-payment/rpc/src/lib.rs 4 additions, 5 deletionssubstrate/frame/transaction-payment/rpc/src/lib.rs
Please register or sign in to comment