From: Jonathan Brown <jbrown@bluedroplet.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Ensuring security of funds and preserving anonymity when using Bitcoin for e-commerce
Date: Thu, 22 Jan 2015 17:20:51 +0700 [thread overview]
Message-ID: <CABaYTy_e-zj=voyLJ89af6ByCW9+=qkh+4xWukMv598JD3JTAA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 225 bytes --]
I wrote a blog post entitled "Ensuring security of funds and preserving
anonymity when using Bitcoin for e-commerce".
I thought the readers of this list might be interested.
http://jonathanpatrick.me/blog/bitcoin-ecommerce
[-- Attachment #2: Type: text/html, Size: 347 bytes --]
reply other threads:[~2015-01-22 10:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CABaYTy_e-zj=voyLJ89af6ByCW9+=qkh+4xWukMv598JD3JTAA@mail.gmail.com' \
--to=jbrown@bluedroplet.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