electrum-ecc
Licence: MIT Licence
Author: The Electrum developers
Language: Python (>= 3.10)
This package provides a pure python interface to libsecp256k1.
Unlike Coincurve, it uses ctypes, and has no dependency.
Tests
$ python3 -m unittest discover -s tests -t .
Or
$ pytest tests -v
Maintainer notes
Release checklist:
- bump
__version__in__init__.py - write changelog?
$ git tag -s "$VERSION" -m "$VERSION"$ git push "$REMOTE_ORIGIN" tag "$VERSION"- build sdist (see
contrib/sdist/):$ ELECBUILD_COMMIT=HEAD ELECBUILD_NOCACHE=1 ./contrib/sdist/build.sh
$ python3 -m twine upload dist/$DISTNAME
Metadata
Release files for electrum-ecc 0.0.8
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 |
|---|---|---|---|---|
| electrum_ecc-0.0.8.tar.gz | 2.5 MB | Without provenance | Details for electrum_ecc-0.0.8.tar.gz |
Release files / electrum_ecc-0.0.8.tar.gz
| Download URL | electrum_ecc-0.0.8.tar.gz |
|---|---|
| Size | 2.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
94869a77de28ee79b7f7e974af5c20b392b949905880a8b26504e28202644106
|
|
BLAKE2b-256 checksum How to use checksums |
f0aa3aab38ecdf6276141264c91c50758df6e59545c87f18247d99b22e62b76f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.5
|
Security for electrum-ecc 0.0.8
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.