If anyone is interested in using a bip44 Wallet to generate
deterministic GPG identities, I have implemented a demonstration in
this allows a user to manage a GPG identity for encryption
and signing with zero bytes of permanent storage. (on
Working on a proposal for extensions based on bip44 conventions.
Most interesting is: Fully Deterministic GPG keys.
Would welcome any comments or interest
Two minor observations:
DecodeBase58Check is listed as inline, but isnt actually inlined in the
This makes it both non-present in libbitcoin_common.a and unavailable
to other code that would use libbitcoin_common.a as a library. (bug?)
In general, the hierarchy of tools is poor/weak. for
I've made a proposal for a standardized ecies scheme for bitcoin
communication. To address gmaxwell's criticism, I'd like to also
follow up with a proposed change to BIP44, such that a structured
wallet would also include a series of identity keys, both addresses
which will be used for
Does anyone see a value in a standardized PGP-style message,
which would allow someone performing a bitcoin transaction to
send signed encrypted messages using only public and private
bitcoin keys ?
I'd like to propose a signed encrypted message protocol, in case
someone see's value in encoding
Mail list logo