This project is forked from https://github.com/polkascan/py-scale-codec
Python Polymath SCALE Codec
Python Polymath SCALE Codec Library
Description
Most of the data that the Substrate RPCs output is encoded with the SCALE Codec. This codec is used by the Substrate nodes' internal runtime. In order to get to meaningful data this data will need to be decoded. The Python SCALE Codec Library will specialize in this task.
Documentation
https://polkascan.github.io/py-scale-codec/
Installation
pip install polymath-scalecodec
Examples
Decode a SCALE-encoded Compact<Balance>
RuntimeConfiguration().update_type_registry(load_type_registry_preset("default"))
RuntimeConfiguration().update_type_registry(load_type_registry_preset("kusama"))
obj = ScaleDecoder.get_decoder_class('Compact<Balance>', ScaleBytes("0x130080cd103d71bc22"))
obj.decode()
print(obj.value)
Encode to Compact<Balance>
RuntimeConfiguration().update_type_registry(load_type_registry_preset("default"))
obj = ScaleDecoder.get_decoder_class('Compact<Balance>')
scale_data = obj.encode(2503000000000000000)
print(scale_data)
Encode to Vec<Bytes>
RuntimeConfiguration().update_type_registry(load_type_registry_preset("default"))
value = ['test', 'vec']
obj = ScaleDecoder.get_decoder_class('Vec<Bytes>')
scale_data = obj.encode(value)
print(scale_data)
Add custom types to type registry
RuntimeConfiguration().update_type_registry(load_type_registry_preset("default"))
custom_types = {
"types": {
"MyCustomType": "u32",
"CustomNextAuthority": {
"type": "struct",
"type_mapping": [
["AuthorityId", "AuthorityId"],
["weight", "AuthorityWeight"]
]
}
}
}
RuntimeConfiguration().update_type_registry(custom_types)
Or from a custom JSON file
RuntimeConfiguration().update_type_registry(load_type_registry_preset("default"))
RuntimeConfiguration().update_type_registry(load_type_registry_file("/path/to/type_registry.json"))
Multiple runtime configurations
By default a singleton is used to maintain the configuration, for multiple instances:
# Kusama runtime config
runtime_config_kusama = RuntimeConfigurationObject()
runtime_config_kusama.update_type_registry(load_type_registry_preset("default"))
runtime_config_kusama.update_type_registry(load_type_registry_preset("kusama"))
# Polkadot runtime config
runtime_config_polkadot = RuntimeConfigurationObject()
runtime_config_polkadot.update_type_registry(load_type_registry_preset("default"))
runtime_config_polkadot.update_type_registry(load_type_registry_preset("polkadot"))
# Decode extrinsic using Kusama runtime configuration
extrinsic = ScaleDecoder.get_decoder_class(
type_string='Extrinsic',
data=ScaleBytes(extrinsic_data),
metadata=metadata_decoder,
runtime_config=runtime_config_kusama
)
extrinsic.decode()
Using the type registry updater in your application
To ensure the type registries are in sync with the current runtime of the blockchain, you can use the updater function in your application:
from scalecodec.updater import update_type_registries
# Update type registries with latest version from Github
try:
update_type_registries()
except Exception:
pass
This will overwrite the type registry JSON files with the downloaded lastest versions from Github. In case of write
permission restrictions it is also possible to always use the remote version on Github with the use_remote_preset kwarg:
# Polkadot runtime config
runtime_config_polkadot = RuntimeConfigurationObject()
runtime_config_polkadot.update_type_registry(load_type_registry_preset("default", use_remote_preset=True))
runtime_config_polkadot.update_type_registry(load_type_registry_preset("polkadot", use_remote_preset=True))
License
https://github.com/PolymathNetwork/py-scale-codec/blob/master/LICENSE
Metadata
Release files for polymath-scalecodec 4.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| polymath-scalecodec-4.0.0.tar.gz | 112.4 kB | Without provenance | Details for polymath-scalecodec-4.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| polymath_scalecodec-4.0.0-py3-none-any.whl | Python 3 | none | any | Details for polymath_scalecodec-4.0.0-py3-none-any.whl |
Total release size: 180.6 kB
Release files / polymath-scalecodec-4.0.0.tar.gz
| Download URL | polymath-scalecodec-4.0.0.tar.gz |
|---|---|
| Size | 112.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ffbc43d1eb677572bb00edcb32170341655b28d130b2ea524cae9a3be45a5d97
|
|
BLAKE2b-256 checksum How to use checksums |
8053b9908c261fa0a7a51955e02e2347208c98df97fe77ae234caa026eea6c97
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.1 CPython/3.9.5
|
Release files / polymath_scalecodec-4.0.0-py3-none-any.whl
| Download URL | polymath_scalecodec-4.0.0-py3-none-any.whl |
|---|---|
| Size | 68.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a85c09dd361d8b62e533aa28e523f2ff78e068892698ef6c0279cecf50378941
|
|
BLAKE2b-256 checksum How to use checksums |
734b40bfc305a925e85aad8a3945a759fb07f49ef5c37d68e77f12b3254390ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.1 CPython/3.9.5
|
Security for polymath-scalecodec 4.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.