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
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
This issue is for tracking backports for state-tracing into Kusama/Polkadot runtimes.
Context
Tracing allows for external sources (exchanges/archive nodes) to follow changes being done to the state by specific extrinsics. Tracing has been available in substrate and therefore Polkadot since Polkadot/Kusama version 0.8.23. However, historical runtimes do not include tracing, and so the entire history may not yet be tracked. In order to do so, tracing functionality must be backported into older runtimes, and the WASM blobs made available locally to overwrite the on-chain WASM if tracing is enabled.
This issue is for tracking backports for state-tracing into Kusama/Polkadot runtimes.
Context
Tracing allows for external sources (exchanges/archive nodes) to follow changes being done to the state by specific extrinsics. Tracing has been available in substrate and therefore Polkadot since Polkadot/Kusama version 0.8.23. However, historical runtimes do not include tracing, and so the entire history may not yet be tracked. In order to do so, tracing functionality must be backported into older runtimes, and the WASM blobs made available locally to overwrite the on-chain WASM if tracing is enabled.
Relevant PR's:
Tracing with bridging to WASM
Overwrite on-chain WASM with local wasm
Backport Older Runtimes
Disclaimer
Full state-tracing may only support Polkadot, or from a specific version as to reduce the amount of versions needed to be backported.
Backports
Version Checklist
End Polkadot Versions, the rest is only Kusama
Summary: v0.8.22 - v0.8.0 for full-tracing support in Polkadot (19 total versions)
The text was updated successfully, but these errors were encountered: