1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
|
Source: python-bip32utils
Section: python
Priority: optional
Maintainer: Josue Ortega <josue@debian.org>
Build-Depends: debhelper (>=9),
dh-python,
python3-setuptools,
python3-all,
python3-ecdsa
Standards-Version: 3.9.8
Homepage: https://github.com/prusnak/bip32utils
Vcs-Git: https://anonscm.debian.org/cgit/collab-maint/python-bip32utils.git
Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/python-bip32utils.git
Package: python3-bip32utils
Architecture: all
Depends: ${misc:Depends}, ${python3:Depends},
python3-ecdsa
Description: 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.
|
