PyWaves – Community Edition
PyWaves-CE is a community-maintained fork of the original PyWaves library for the Waves blockchain.
It is a drop-in replacement that keeps the import path pywaves intact, so existing code keeps working without edits.
pip install pywaves-ce
Basic Example
import pywaves as pw
# Create addresses from seeds
firstAddress = pw.Address(seed = 'this is just a simple test seed 1')
secondAddress = pw.Address(seed = 'this is just a simple test seed 2')
# Send Waves from one address to another
tx = firstAddress.sendWaves(secondAddress, 100000)
assert 'id' in tx
# Wait for transaction to complete and verify status
tx = pw.waitFor(tx['id'])
assert tx['applicationStatus'] == 'succeeded'
Purpose & Rationale of Community Edition
- Unmaintained upstream – the original PyWaves no longer receives updates.
- Drop-in replacement – legacy code keeps using
import pywaves as pwunchanged. - Active maintenance – security fixes and new Waves features are delivered regularly.
- Repository layout – PyWaves-CE hosts the pristine 1.0.5 upstream snapshot.
- PyPI distribution – published as pywaves-ce while the internal package name remains
pywaves. - Versioning roadmap
- 1.x – strict legacy API compatibility with upstream 1.0.5.
- 2.x – modernization and intentional breaking changes.
Documentation
License
Code released under the MIT License.
Development and Packaging
PyWaves uses Poetry for dependency management and packaging.
Installation for Development
- Install Poetry (if not already installed)
pip install poetry
- Install dependencies
poetry install
- Activate the virtual environment
poetry shell
Building the Package
poetry build
This will create both wheel and source distributions in the dist/ directory.
Testing Across Python Versions
PyWaves includes a workflow testing system that can test across multiple Python versions:
python workflow_venvs.py
python workflow_tests.py
This will test the library with all Python versions specified in PYTHON_VERSIONS.py.
Metadata
Release files for PyWaves-CE 2.0.5
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 |
|---|---|---|---|---|
| pywaves_ce-2.0.5.tar.gz | 27.7 kB | With provenance | Details for pywaves_ce-2.0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pywaves_ce-2.0.5-py3-none-any.whl | Python 3 | none | any | Details for pywaves_ce-2.0.5-py3-none-any.whl |
Total release size: 57.6 kB
Release files / pywaves_ce-2.0.5.tar.gz
| Download URL | pywaves_ce-2.0.5.tar.gz |
|---|---|
| Size | 27.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fdfa5fd00198191552514cc9fc2fd6bef21e678a9bc868ed26071218e6185d4b
|
|
BLAKE2b-256 checksum How to use checksums |
13913de04cd678cbc324590cae18e476568b364cd6f141ef5aef8f4016f2de57
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Apr 16, 2026.
Transparency logRelease files / pywaves_ce-2.0.5-py3-none-any.whl
| Download URL | pywaves_ce-2.0.5-py3-none-any.whl |
|---|---|
| Size | 30.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5b9317acde9c808c85c09f99ae8b5f4f595756f24cca3c318514541b5770fcd5
|
|
BLAKE2b-256 checksum How to use checksums |
24456c7fa9a715a711a68a08f154dfa368d9668532f4e742338cf634f6522927
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Apr 16, 2026.
Transparency logSecurity for PyWaves-CE 2.0.5
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pywaves_ce-2.0.5.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 Apr 16, 2026.
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.