From: Michael McLees <michael.nakapay@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Nakapay - Proposal for payment method using client generated paycodes and federated paycode servers
Date: Thu, 6 Nov 2014 07:29:14 -0600 [thread overview]
Message-ID: <CALZ14xkBXA8vMvW5Z+Hai+XtDisX8vnWevKuGxgLJNGQHRM99g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]
I sent this yesterday but it is not showing in the archives, so I'm not
sure if I did it correctly. I sent it prior to subscribing, so perhaps that
mucked it up.
nakapay.com
I have developed a system whereby a person requesting Bitcoin can make a
specific request (amount, address, timeframe, etc...) by only communicating
a 6 character paycode to a payer. The system does not require that users
sign up for the service; it is open to all. Users may submit information by
POST via my API for which I have documentation on the website above. It is
my intention to convince wallet developers, merchants, exchanges, and
payment processors to integrate my system into their products.
Common objections are a lack of use cases and a lack of security. I'd like
to explore possible use cases and discuss security with this mailing list.
When talking to wallet developers, I've gotten the impression that there is
a chicken and egg problem with my product. If no one uses it, they won't
develop for it, and if they don't develop for it ... on and on.
There are possible monetary incentives for development as there is a
possible revenue stream for paycode server operators.
I've not used a mailing list like the before, so I'm not sure if this
submission is getting where it needs to go.
Thank you all for your time and continued efforts to improve Bitcoin.
[-- Attachment #2: Type: text/html, Size: 2301 bytes --]
reply other threads:[~2014-11-06 13:29 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=CALZ14xkBXA8vMvW5Z+Hai+XtDisX8vnWevKuGxgLJNGQHRM99g@mail.gmail.com \
--to=michael.nakapay@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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