Skip to main content
File added late

1 file was added to this release more than 14 days after its initial publication. Inspect the release files before installing.

Forked from Ofek’s awesome Bit library: https://github.com/ofek/bit

https://img.shields.io/pypi/v/bitsv.svg?style=flat-square https://img.shields.io/travis/AustEcon/bitsv.svg?branch=master&style=flat-square https://img.shields.io/codecov/c/github/AustEcon/bitsv.svg?style=flat-square https://img.shields.io/pypi/pyversions/bitsv.svg?style=flat-square https://img.shields.io/badge/license-MIT-blue.svg?style=flat-square

Noticeboard:

Latest Release - 0.9.0 (2019-08-11)

  • Also big changes in 0.8.0 so please take note.

Default Fee = 1 sat/byte:

  • The capacity of the Bitcoin SV network is such that 1 sat/byte virtually guarantees that your transaction will be included in the next block. This is therefore the default. However, it is trivial to specify a higher transaction fee by including this as an additional parameter to any of the transaction related functions.

Planned improvements

  • Improved coverage of testing modules (currently at 84%).

  • Support for use of a local bitcoin full node instead of a Web-API. (paves the way for a RegTest environment for a rapid development cycle)

  • Work on the bsvbip32 library for hierarchical deterministic keys: https://github.com/AustEcon/bsvbip32. Plan for each node to access bitsv functionality so that building apps can be a breeze! (competing implementations welcome. That’s partly why modularity is a good idea!)

  • Add Whatsonchain API for added redundancy across main / test and stn networks.

  • Minor updates to documentation for 0.9.0 release are still needed re: PrivateKey.get_transaction()


Examples

BitSV is so easy to use:

  1. Simple payment:

>>> import bitsv
>>> my_key = bitsv.Key('YourPrivateKeyGoesHere')  # Defaults to "main" network
>>> my_key.get_balance()
10000000  # satoshis
>>> # Can include a long list of tuples as outputs
>>> outputs = [
>>>     # Donate to AustEcon! (Currency conversion via api)
>>>     ('1PdvVPTzXmo4cSs68HctLUxAdW917UZtC8', 0.10, 'usd'),  # $USD 0.10 as bsv
>>>     ('1PdvVPTzXmo4cSs68HctLUxAdW917UZtC8', 0.0001, 'bsv')
>>> ]
>>> my_key.send(outputs)
'dec895d1aa0e820984c5748984ba36854163ec3d6847c94e82a921765c5b23e1'

Here’s the transaction https://whatsonchain.com/tx/dec895d1aa0e820984c5748984ba36854163ec3d6847c94e82a921765c5b23e1.

  1. OP_RETURN - 100kb size limit now supported:

>>> import bitsv
>>> my_key = bitsv.Key('YourPrivateKeyGoesHere')
>>> list_of_pushdata = ([bytes.fromhex('6d01'),  # encode hex to bytes
                         'New_Name'.encode('utf-8')])  # encode string to utf-8 encoded bytes
>>> my_key.send_op_return(list_of_pushdata)  # default fee = 1 sat/byte

This sets memo.sv name (linked to this bitcoin address) to “New_Name” (as per https://memo.sv/protocol)

Features

  • Python’s fastest available implementation (100x faster than closest library)

  • 100kb OP_RETURN transactions made very simple

  • Fully supports 21 different currencies via exchange rate API

  • First class support for storing data in the blockchain

  • Compressed public keys by default

  • Multiple representations of private keys; WIF, PEM, DER, etc.

  • Standard P2PKH transactions

Installation

BitSV is distributed on PyPI as a universal wheel and is available on Linux/macOS and Windows and supports Python 3.5+ and PyPy3.5-v5.7.1+. pip >= 8.1.2 is required.

$ pip install bitsv  # pip3 if pip is Python 2 on your system.

Documentation

Docs are hosted by Github Pages and are automatically built and published by Travis after every successful commit to BitSV’s master branch.

Credits

Donate

  • If you have found this library useful, please consider donating. It really helps.

  • HandCash: $AustEcon

  • 1PdvVPTzXmo4cSs68HctLUxAdW917UZtC8

Metadata

Release files for bitsv 0.9.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

File added late

1 file was uploaded more than 14 days after the first file in this release.

While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.

We recommend inspecting the release files before installing.

Source distribution (sdist)

Source distribution for bitsv 0.9.0
File Size Uploaded Provenance
bitsv-0.9.0.tar.gz 40.5 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for bitsv 0.9.0
File Interpreter ABI Platform
bitsv-0.9.0-py3.7.egg Legacy Egg format - - Details

Total release size: 158.3 kB

Release files / bitsv-0.9.0.tar.gz

Download URL bitsv-0.9.0.tar.gz
Size 40.5 kB
Tags Source
SHA-256 checksum
How to use checksums
b03037c4614ff76a7e0308ead9bb93d188a16f6aa05400cc17e05dbf8e33647b
BLAKE2b-256 checksum
How to use checksums
4b129f0824bb4b5279b066b27df6d0f800ecc7bc73e205c83747d21acabe9450
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/39.0.1 requests-toolbelt/0.8.0 tqdm/4.30.0 CPython/3.7.1

Release files / bitsv-0.9.0-py3.7.egg

File added late

This file was uploaded more than 14 days after the first file in this release.

While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.

We recommend inspecting the release file before installing.

Download URL bitsv-0.9.0-py3.7.egg
Size 117.8 kB
Tags Egg
SHA-256 checksum
How to use checksums
148aaa14b0e6fed77b66dc95de4d831039ac255494ea725f90eaa87b56221d64
BLAKE2b-256 checksum
How to use checksums
e14bf31e4551b56aac5f62be4c6db40267ff93d85c56c574aa0cf1e078e39722
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.1.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.6.2 requests-toolbelt/0.9.1 tqdm/4.39.0 CPython/3.7.2

Security for bitsv 0.9.0

Upload timing

File added late

1 file was uploaded more than 14 days after the first file in this release.

While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.


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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page