Peaq SDK
Peaq Network SDK for comprehensive blockchain interactions on EVM and Substrate chains.
Installation
pip install peaq-sdk
Usage
from peaq_sdk import Sdk
from peaq_sdk.types import ChainType
from eth_account import Account
# Create an instance
sdk = await Sdk.create_instance({
"base_url": "https://your-rpc-url.com",
"chain_type": ChainType.EVM,
"auth": Account.from_key("your-private-key")
})
# Use SDK modules
result = await sdk.storage.add_item({"item_type": "test", "item": "data"})
did = await sdk.did.create({...})
transfer = sdk.transfer.native("0x...", 1.5)
Features
- DID Operations: Create, read, update, and remove decentralized identifiers
- Storage Management: On-chain data storage with add, get, update, remove operations
- RBAC System: Role-based access control with roles, groups, and permissions
- Token Transfers: Native token and ERC-20/721 transfers across chains
- Multi-chain Support: EVM and Substrate chain compatibility
- Transaction Management: Status callbacks and confirmation modes
Tests
Run tests with:
python -m pytest -s
Metadata
Release files for peaq-sdk 1.0.1
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 |
|---|---|---|---|---|
| peaq_sdk-1.0.1.tar.gz | 33.5 kB | With provenance | Details for peaq_sdk-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| peaq_sdk-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for peaq_sdk-1.0.1-py3-none-any.whl |
Total release size: 73.9 kB
Release files / peaq_sdk-1.0.1.tar.gz
| Download URL | peaq_sdk-1.0.1.tar.gz |
|---|---|
| Size | 33.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fce5019ed9fff56232313e315fcf3159b179b88902d715a5867a196c66348151
|
|
BLAKE2b-256 checksum How to use checksums |
a47ca406e9902ba583b9b0c454b816b48c611a48c8e6975411224c138cc7e790
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 24, 2025.
Transparency logRelease files / peaq_sdk-1.0.1-py3-none-any.whl
| Download URL | peaq_sdk-1.0.1-py3-none-any.whl |
|---|---|
| Size | 40.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3a06870e2763b7b84eac8f280f532b5336194e277e13815d3ee98919b01269d7
|
|
BLAKE2b-256 checksum How to use checksums |
ce44254419a6e9ea450876405ac262eb277a09db56ccc5d63a029c7e50c5a7e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 24, 2025.
Transparency logSecurity for peaq-sdk 1.0.1
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for peaq_sdk-1.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 24, 2025.
Transparency logA 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.