Robert Gabriel Jakabosky

What `substrate.get_events` are you calling? Is it a TypeScript/JS package or Rust package?

That library says that it supports most `MetadataV14` chains, which we support now (since our v5.0 release last month). With the v14 metadata, the `polymesh_schema.json` file shouldn't be needed, at...

Maybe it needs some extra info for the `type_registry_preset` to support Polymesh.

I am going to try that python library locally here.

Found the problem. Most substrate chains have their `runtime` package just one level deep (Polkadot `polkadot_runtime::Event`), but Polymesh has an extra package level `polymesh_runtime_mainnet::runtime::Event`. The python package `scalecodec` uses a...

Here is another way to patch in those types: ```python from substrateinterface import SubstrateInterface, Keypair from substrateinterface.exceptions import SubstrateRequestException # import logging # logging.basicConfig(level=logging.DEBUG) custom_types = { "types": { "polymesh_runtime_develop::runtime::Event":...

@arjanz Confirmed that works. Thanks for the quick fix.

@JMoore96 We will need to merge this PR to fix those compile errors: https://github.com/PolymeshAssociation/Polymesh/pull/1322 I added a change to the `storage_migrate_on` macro to allow using a different name then `StorageVersion`...

TODOS: - [x] Add benchmarks for new chain extension interfaces (ReadStorage, GetSpecVersion, GetTransactionVersion, etc...) - [x] Add call filter and storage + extrinsics for managing the list of allowed runtime...

- [ ] Add unit tests for the new extrinsic.