From: Mem Wallet <memwallet.info@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] bip44 GPG identities - POC demo
Date: Sat, 7 Mar 2015 10:53:37 -0500 [thread overview]
Message-ID: <CAKzHBKnh+yzTwXkZXmezRaOkTTnUO4Z1dJnvKjYGnZBKoNQNEQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
If anyone is interested in using a bip44 Wallet to generate
deterministic GPG identities, I have implemented a demonstration in
javascript.
http://memwallet.info/bip44ext/test.html
this allows a user to manage a GPG identity for encryption
and signing with zero bytes of permanent storage. (on tails for example)
Paper is here still:
https://github.com/taelfrinn/bip44extention/blob/master/README.md
One minor correction added which specifies that the smallest S value
should be used, to prevent different ecdsa implementations from creating
non-canonical/identical outputs.
comments welcome
[-- Attachment #2: Type: text/html, Size: 973 bytes --]
next reply other threads:[~2015-03-07 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 15:53 Mem Wallet [this message]
2015-03-08 1:34 ` [Bitcoin-development] bip44 GPG identities - POC demo Pavol Rusnak
2015-03-08 8:20 ` Natanael
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKzHBKnh+yzTwXkZXmezRaOkTTnUO4Z1dJnvKjYGnZBKoNQNEQ@mail.gmail.com \
--to=memwallet.info@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox