python-bip32utils 0.0~git20170118.dd9c541-2 source package in Ubuntu


python-bip32utils (0.0~git20170118.dd9c541-2) unstable; urgency=medium

  * Change scripts shebang to use Python 3
  * Update package to use debhelper-compat (= 12)
  * debian/control: Update Vcs fields to use
  * Add Debian CI tests
  * Add patch to fix bad Float argument in bip32gen script
  * Bump Standards-Version to 4.4.0:
    - Update debian/copyright Format to use securre URI

 -- Josue Ortega <email address hidden>  Fri, 06 Sep 2019 13:46:24 -0600

Upload details

Uploaded by:
Josue Ortega
Uploaded to:
Original maintainer:
Josue Ortega
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Oracular release universe misc
Noble release universe misc
Mantic release universe misc
Lunar release universe misc
Jammy release universe misc
Focal release universe misc


Focal: [FULLYBUILT] amd64


File Size SHA-256 Checksum
python-bip32utils_0.0~git20170118.dd9c541-2.dsc 2.1 KiB b992f174edc5591a5799af56e49ca2efbfe504779f66bb131953da62b97c2f63
python-bip32utils_0.0~git20170118.dd9c541.orig.tar.gz 17.5 KiB 28e4f2ecbf350d6519a0ce576a9ba326900b6420d067ed1e6f9dd701cb1c00c3
python-bip32utils_0.0~git20170118.dd9c541-2.debian.tar.xz 3.7 KiB b3c1fd8980008f3503260b83c7c1f2b4086aab4bee656b0a12a993b21cee794f

No changes file available.

Binary packages built by this source

python3-bip32utils: Python implementation of Bitcoin hierarchical deterministic wallet

 The bip32utils library is a pure Python implementation of Bitcoin hierarchical
 deterministic wallet ("HD Wallet") ECDSA key generation as specified in
 BIP0032 (Bitcoin Improvement Proposal #0032).
 Deterministic ECDSA key generation allows creating a sequence of Bitcoin
 private and public ECDSA keys from an initial seed and a hierarchical set of
 indices. A number of benefits follow:
  - An entire wallet can be backed up once by storing the wallet seed or master
    extended private key, and all future addresses in the wallet can be restored
    from it.
  - The creation of public and private ECDSA keys may be separated from each
    other. That is, it is possible to create only the public ECDSA key half
    (and receiving address) of an ECDSA key pair, without the ability to create
    the private half. Thus, one can create receiving addresses on a public
    facing system that if compromised would not give the attacker the ability to
    spend bitcoin received at those addresses. A separate, offline machine can
    generate the corresponding private ECDSA keys and sign transactions.
  - Public and private ECDSA keys may be created in a hierarchy, and control
    over or visibility of portions of the hierarchy may be delegated to third
    This has uses for auditing, for separating ECDSA key sequences into
    different logical groups or accounts, and for giving 3rd parties the ability
    to create spending transactions without first getting a receiving address
    in advance.