You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do we want Subxt to be able to accept some merkalized metadata "proof" and use it to decode an extrinsic?
This would allow Subxt to be used in signers which are only passed this merkalized metadata and some TX bytes, and then decode this payload in order to show to the user, as well as then sign the TX taking this metadata proof hash into account.
Do we want Subxt to be able to accept some merkalized metadata "proof" and use it to decode an extrinsic?
I would say it depends on the demand for this feature. For now, I would probably say that you don't need this, but maybe someone already uses subxt in a signer, then this is probably a different topic.
Do we want Subxt to be able to accept some merkalized metadata "proof" and use it to decode an extrinsic?
This would allow Subxt to be used in signers which are only passed this merkalized metadata and some TX bytes, and then decode this payload in order to show to the user, as well as then sign the TX taking this metadata proof hash into account.
Needs thought!
https://github.com/bkchr/merkleized-metadata
The text was updated successfully, but these errors were encountered: