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

Changelog

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

  * Team upload.
  * No change upload for reproduce.debian.net

 -- Jochen Sprickerhof <email address hidden>  Thu, 27 Nov 2025 11:20:24 +0100

Upload details

Uploaded by:
Josue Ortega
Uploaded to:
Sid
Original maintainer:
Josue Ortega
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Resolute release universe misc

Builds

Resolute: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
python-bip32utils_0.0~git20170118.dd9c541-3.dsc 2.2 KiB 99318960b662a088e6750ee791558e0be6c2aaeb4d9c1cb5f107fb7e22742415
python-bip32utils_0.0~git20170118.dd9c541.orig.tar.gz 17.5 KiB 28e4f2ecbf350d6519a0ce576a9ba326900b6420d067ed1e6f9dd701cb1c00c3
python-bip32utils_0.0~git20170118.dd9c541-3.debian.tar.xz 3.8 KiB 50a0f6b102c9ae5cde2d4afb9a286c3fd665ff1f290334c315abd060777cfd40

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
    parties.
    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.