qorechain-asset-kit (Python)
Python client for the proposed QoreChain regulated-asset modules: x/asset, x/identity, x/compliance, x/settlement and x/attest.
These modules are a proposal. They do not exist on QoreChain, on mainnet or on the testnet, and no chain upgrade that would add them is scheduled. What works on QoreChain today is the set of EVM contracts in
contracts/.
ChainClientraisesChainUpgradeRequired(with.module, for example"x/asset", and.code == "CHAIN_UPGRADE_REQUIRED") on every call. It makes no network request.MockChainimplements the proposed rules of docs/proposal.md in memory, so that applications can be built and tested now. Refusals raiseMockChainErrorwith the proposed error code name (for exampleERROR_CODE_ADDRESS_FROZEN).- Types generated from
proto/are inqorechain_asset_kit.asset,.identity,.compliance,.settlementand.attest.
Python 3.10 or later.
from qorechain_asset_kit import MockChain, MockChainError, asset
chain = MockChain()
chain.asset.create_asset(issuer="qor1issuer", asset_id="bond-2030", flags={"freezable": True})
chain.asset.mint(agent="qor1issuer", asset_id="bond-2030", to="qor1alice", amount="100")
chain.asset.freeze(agent="qor1issuer", asset_id="bond-2030", holder="qor1alice", frozen=True)
try:
chain.asset.transfer(from_="qor1alice", asset_id="bond-2030", to="qor1bob", amount="1")
except MockChainError as e:
print(e.code) # ERROR_CODE_ADDRESS_FROZEN
Methods take either the generated message, a dict, or keyword arguments. The proto field from is a Python keyword: pass it as from_ (or inside a dict as "from").
Mock helpers: set_hybrid_key, has_hybrid_key, fund_bank, bank_balance, advance(blocks, seconds), height, time, events(type=None), define_module_logic(module_id, fn).
Development
python -m venv .venv && . .venv/bin/activate
pip install -r requirements-dev.txt && pip install -e .
pytest
scripts/gen.sh # regenerate the protobuf code (protoc 36.2)
Licence: Apache-2.0. Copyright 2026 QoreChain Association.
Metadata
Release files for qorechain-asset-kit 0.1.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 |
|---|---|---|---|---|
| qorechain_asset_kit-0.1.0.tar.gz | 50.4 kB | Without provenance | Details for qorechain_asset_kit-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qorechain_asset_kit-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for qorechain_asset_kit-0.1.0-py3-none-any.whl |
Total release size: 136.3 kB
Release files / qorechain_asset_kit-0.1.0.tar.gz
| Download URL | qorechain_asset_kit-0.1.0.tar.gz |
|---|---|
| Size | 50.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fbaa3f9c0e3d17b07e894198fa97fc628cd7caf4716618a51d254b1484d64b2d
|
|
BLAKE2b-256 checksum How to use checksums |
5ad1651c6a009432c67d8abd876e9f4664b33c20e1050882dec17665a684b169
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.7
|
Release files / qorechain_asset_kit-0.1.0-py3-none-any.whl
| Download URL | qorechain_asset_kit-0.1.0-py3-none-any.whl |
|---|---|
| Size | 85.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
35a6f378c6b2ce18e1cc962daa045a2f5798d5b7c6bc27fa39d59c772a0c0f9f
|
|
BLAKE2b-256 checksum How to use checksums |
ea6a02534f2b50ef99b6c0d6d2fe591b720fbd73d1727172a5a9eddd478350fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.7
|
Security for qorechain-asset-kit 0.1.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.