From: Chris D'Costa <chris.dcosta@meek.io>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] Post to list request
Date: Fri, 21 Mar 2014 10:11:59 +0100 [thread overview]
Message-ID: <A48AEA3A-D4B2-4600-927C-3F642B366078@meek.io> (raw)
Hello
I wonder if I could be granted access to post to the dev list. My project is the Meek hardware wallet, and we are working on a solution to avoid MITM attacks when communicating a pay-to information over a non-secure transport mechanism.
Regards
Chris
next reply other threads:[~2014-03-21 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 9:11 Chris D'Costa [this message]
2014-03-21 10:58 ` [Bitcoin-development] Post to list request Andreas Schildbach
2014-03-21 11:09 ` Mike Hearn
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=A48AEA3A-D4B2-4600-927C-3F642B366078@meek.io \
--to=chris.dcosta@meek.io \
--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