From: "Odinn Cyberguerrilla" <odinn.cyberguerrilla@riseup.net>
To: "Jeff Garzik" <jgarzik@bitpay.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Andreas Schildbach <andreas@schildbach.de>
Subject: Re: [Bitcoin-development] BIP70 proposed changes
Date: Mon, 5 May 2014 19:35:14 -0700 [thread overview]
Message-ID: <70790f686997e51d680e9bde0c9d5a3e.squirrel@fulvetta.riseup.net> (raw)
In-Reply-To: <CAJHLa0MGaxJTGPR-bduW36-4Msb348FANqFmw67jqFxq1CLwbw@mail.gmail.com>
I am curious if the Android developer who had been working on two factor
authentication and bitcoin had worked toward an open issue or pull
request? I had been looking around for some sign that this had occurred
but hadn't found it, I am interested to know what is the progress in this
area (in a fully decentralized way that resides fully on one's device or
devices).
For some reason maidsafe keeps rising up in my brain, have bitcoin core
developers touched bases with maidsafe developers on these kind of fine
points?
Just thoughts and questions.
-Odinn
> On Tue, Feb 18, 2014 at 4:40 PM, Andreas Schildbach
> <andreas@schildbach.de> wrote:
>> On 02/18/2014 08:14 PM, Ryan X. Charles wrote:
>>> BitPay is working on a new standard
>>> based on bitcoin-like addresses for authentication. It would be great
>>> if
>>> we could work with the community to establish a complete, decentralized
>>> authentication protocol.
>>
>> Sounds interesting, let us know as soon as you have anything.
>
> SINs. See https://en.bitcoin.it/wiki/Identity_protocol_v1
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
next prev parent reply other threads:[~2014-05-06 2:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 17:31 [Bitcoin-development] BIP70 proposed changes Andreas Schildbach
2014-02-18 19:14 ` Ryan X. Charles
2014-02-18 20:15 ` Gavin Andresen
2014-02-18 21:40 ` Andreas Schildbach
2014-02-19 14:10 ` Jeff Garzik
2014-02-19 16:44 ` Mike Hearn
2014-05-06 2:35 ` Odinn Cyberguerrilla [this message]
2014-05-06 8:22 ` Alon Muroch
2014-02-18 21:47 ` Peter Todd
2014-02-18 23:41 ` Bernd Jendrissek
2014-02-18 22:02 ` Derber
2014-02-21 15:34 ` Mike Hearn
2014-03-05 10:18 ` 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=70790f686997e51d680e9bde0c9d5a3e.squirrel@fulvetta.riseup.net \
--to=odinn.cyberguerrilla@riseup.net \
--cc=andreas@schildbach.de \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jgarzik@bitpay.com \
/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