mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-04-23 09:38:00 +00:00
3aabd6dc09
* WIP subxt-historic * WIP subxt-historic * WIP subxt-historic; flesh out basic foundations * WIP filling in extrinsic decoding functionality * iter and decode transaction extensions * Fill in the Online/OfflineClient APIs and move more things to be part of the chain Config * WIP storage * clippy, fmt, finish extrinsics example * prep for 0.0.1 release to claim crate name * fix README link * fmt * WIP thinking about storage APIs * WIP working out storage APIs * Storage plain value fetching first pass * WIP storage: first pass iterating over values done * First apss finishing storage APIs * fmt and clippy * Create a storage example showing fetch and iteration * Bump to frame-decode 0.9.0 * Bump subxt-historic to 0.0.3 for preview release * Remove unused deps * fix import * clippy * doc fixes * tweak CI and fix some cargo hack findings * Update README: subxt-historic is prerelease
17 lines
1.1 KiB
Markdown
17 lines
1.1 KiB
Markdown
# subxt-historic
|
|
|
|
**This create is a work in progress and currently is released only as a preview.**
|
|
|
|
While `subxt` is a library for working at the head of a chain (submitting transactions and obtaining the current state), `subxt-historic` is a library for decoding blocks and state that are anywhere in a chain. To broadly summarize the differences:
|
|
|
|
| Feature | subxt | subxt-historic |
|
|
|-----------------------------------------|------------------------------|-------------------------------|
|
|
| Block access | Head of chain | Any block in chain |
|
|
| Connection to chain | Light client or RPC node | Archive RPC nodes only |
|
|
| Transaction submission | Yes | No |
|
|
| Metadata compatibility | V14 and newer | Any version |
|
|
|
|
# Examples
|
|
|
|
See the [examples](https://github.com/paritytech/subxt/tree/master/historic/examples) folder for examples of how to use `subxt-historic`.
|