Cryprum client, for Python 3
Installation
pip install cryprum
Usage
Create a token at https://cryprum.com/tokens and copy "Access key"
from cryprum import Client
client = Client(token="<ACCESS_KEY>")
# Get balances
balances = client.balances("ethereum", "0xYourAddress")
print(balances) # {"ETH": 1000000000000000000, "USDT": 500000}
# Create transaction (returns immediately with operation ID)
result = client.transaction(
"ethereum",
amount=1.0,
currency="ETH",
private_key="0x...",
to_address="0xRecipient"
)
print(result) # {"id": "...", "status": "pending"}
# Poll for operation status
status = client.operation_status(result["id"])
print(status) # {"id": "...", "status": "C", "external_id": "0xtxhash..."}
# Get transaction info
tx = client.transaction_info("tron", "5de813c815a3b9feb393318b7985ff57217ea53bd7944373447406c6b918e51f")
print(tx)
# {
# "block_number": 69056553,
# "from_address": "TYDzsYUEpvnYmQk4zGP9sWWcTEd2MiAtW6",
# "to_address": "TMG9ZrB4kvCyJwdyw9wiUV8mnw5qhEdjjU",
# "txid": "5de813c815a3b9feb393318b7985ff57217ea53bd7944373447406c6b918e51f",
# "currency_code": "USDT",
# "value": 169310000,
# "value_human": 169.31,
# "confirmations": 100
# }
Async client
from cryprum import AsyncClient
async with AsyncClient(token="<ACCESS_KEY>") as client:
balances = await client.balances("ethereum", "0xYourAddress")
API Methods
| Method | Description |
|---|---|
balances(vendor, address) |
Get wallet balances |
transaction(vendor, amount, currency, private_key, to_address) |
Create withdrawal |
transaction_info(vendor, txid) |
Get transaction details |
operation_status(operation_id) |
Poll operation status |
subscribe(vendor, addresses) |
Subscribe to address notifications |
Supported vendors: tron, ethereum, bsc, polygon
Development
Run tests
pytest -v
Build and publish to PyPI
# Install uv if not already
pip install uv
# Build package
uv build
# Publish to PyPI
uv publish --token $PYPI_TOKEN
License
MIT
Metadata
Release files for cryprum 1.2.2
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 |
|---|---|---|---|---|
| cryprum-1.2.2.tar.gz | 9.2 kB | Without provenance | Details for cryprum-1.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cryprum-1.2.2-py3-none-any.whl | Python 3 | none | any | Details for cryprum-1.2.2-py3-none-any.whl |
Total release size: 19.0 kB
Release files / cryprum-1.2.2.tar.gz
| Download URL | cryprum-1.2.2.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fdb8aabac9212eead37271bfd00caf8a534c8beefe0243a09bed6c3fc197ab36
|
|
BLAKE2b-256 checksum How to use checksums |
a316b246c0c28eed0ad3389b2c8062b0f82a82d1e1f982d1fcf1ac4cb75de563
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.13
|
Release files / cryprum-1.2.2-py3-none-any.whl
| Download URL | cryprum-1.2.2-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
badfffef02adabfd61444282da76a043e277b977e0fe5033cf43b3f8b2bce579
|
|
BLAKE2b-256 checksum How to use checksums |
80fa84691cb9366550a1645aaf4bf91e45f834277f40cc54ddc7f81b10752285
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.13
|
Security for cryprum 1.2.2
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.