[ref-docs]: Improve ref-docs for signed extensions #3234
Conversation
jsdw
added
R0-silent
There was a problem hiding this comment.
I don't mind this, but I was thinking maybe we should also wait for #2280, and then revamp this page? cc @georgepisaltu wdyt? Do you think is it worth teaching people about signed extensions at this point?
There was a problem hiding this comment.
Signed extensions are becoming deprecated in favor of a new interface, TransactionExtension. More details on that in #2280.
I think waiting for TransactionExtension to drop and revamping this is the best course of action. A very good starting point is the PR description of #2280. I will also review the proposed docs here as I am sure there will be bits and pieces that will still be relevant.
Yup, I agree; I've looked through the new PR and related bits, and while I'm sure bits are still relevant, I'm happy to wait until that stuff merges and then have another look and update the details/examples/etc to line up with the new stuff :) |
The goals of this signed extension ref doc is to provide an overview of signed extensions, with links to various examples (eg current signed extensions and the trait itself) to learn more. This page is linked from the
extrinsic_encodingdocs so that, when from learning how to encode signed extensions as part of extrinsics there, you can come here for a bit of a deeper look into what they are and some examples showing how they are useful.I did find myself struggling to decide what was worth writing here though as opposed to on the trait etc itself. I also am not an expert on writing signed extensions (being more of a consumer/encoder of them from client code), but nevertheless I thought I'd have a stab at this :)
Feedback welcome!
Closes paritytech/polkadot-sdk-docs#42