Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Publish the dispatch info in extrinsic events #4148

Merged
merged 11 commits into from
Nov 22, 2019
Merged

Conversation

gavofyork
Copy link
Member

@gavofyork gavofyork commented Nov 19, 2019

Place the DispatchInfo (which contains weight information about the
extrinsic that is otherwise difficult to determine) in the dispatch
result value.

CC @jacogr

Place the DispatchInfo (which contains weight information about the
extrinsic that is otherwise difficult to determine) in the dispatch
result value.
Copy link
Contributor

@kianenigma kianenigma left a comment

Choose a reason for hiding this comment

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

Sure.

Why though? doesn't the RPC already give this?

@gavofyork
Copy link
Member Author

afaik the RPC is useful only for extrinsics that have yet to happen, not that have happened.

@jacogr
Copy link
Contributor

jacogr commented Nov 19, 2019

100%, the RPC is pre-execution, the events are post-execution.

So the events are especially useful in explorers that display historical transactions with all associated info, where the RPC is especially useful in wallets where transactions are made.

@emielsebastiaan
Copy link

The request came from me (for Polkascan). There seems no other way to accurately determine fees on transaction level for historical transactions. We should be able to determine the weight component of the fees with this change.

@gavofyork gavofyork added this to the polkadot-0.6.18 milestone Nov 22, 2019
@gavofyork gavofyork merged commit 371074c into master Nov 22, 2019
@gavofyork gavofyork deleted the gav-publish-weight branch November 22, 2019 14:11
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.

4 participants