public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mem Wallet <memwallet.info@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] standardize on bitcoin signed ecies ?
Date: Tue, 26 Aug 2014 20:57:51 -0400	[thread overview]
Message-ID: <CAKzHBKndU4nHHK=h4=G+hG_t_c77h0DHpeEUK+Kk9q2CsRHEcQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 322 bytes --]

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 such a thing into a BIP.

[-- Attachment #2: Type: text/html, Size: 437 bytes --]

             reply	other threads:[~2014-08-27  0:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27  0:57 Mem Wallet [this message]
2014-08-27  1:08 ` [Bitcoin-development] standardize on bitcoin signed ecies ? Gregory Maxwell

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='CAKzHBKndU4nHHK=h4=G+hG_t_c77h0DHpeEUK+Kk9q2CsRHEcQ@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