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
Subxt can already decode events, constants and storage entries, but it can't decode recent blocks. This feels like a key missing part of the API, so let's add support for this.
The Plan
Create a "block-centric" API for subscribing to blocks and accessing the transactions, events and storage in the block.
Allow extrinsic bytes to be dynamically decoded into some Values representing call data.
Allow attempts to statically decode extrinsics into some tuple or struct representing call data?
Open Questions
Can we do anything about block signatures?
How far can we statically vs dynamically decode transactions? I think we'll look to the Events API for inspiration here and probably offer a similar interface. Like Events, we may not have the information we need to be able to decode all transactions (we might know only about a subset of pallets).
The Vision
Subxt can already decode events, constants and storage entries, but it can't decode recent blocks. This feels like a key missing part of the API, so let's add support for this.
The Plan
Value
s representing call data.Open Questions
Here is the corresponding GitHub milestone:
https://github.com/paritytech/subxt/milestone/15
The text was updated successfully, but these errors were encountered: