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
There's an actor to decode extrinsics and it works, with some caveats:
there may be discrepencies between the formats of newer, scale-info-produced JSON and legacy-desubj produced JSON (in terms of extrinsics)
once archive reaches the point at which it begins to decode extrinsics using desub-current, i.e. scale-info the memory tends to balloon. This could/is for a few reasons and there could be optimizations made in archive, but imo mainly because of the presence of doc-strings within the metadata (which take up a most of the extrinsic in scale-info). If we are decoding 1000-10,000 extrinsics at once, this causes significant memory issues
Other than this, indexing is fast enough and it works
Bug Fixes needed:
Desub issues
frame-metadata
dependencies from git to crates desub#55version
for RuntimeMetadata when added to frame-metadata desub#51Nice to Have:
The text was updated successfully, but these errors were encountered: