From: Brooks Boyd <boydb@midnightdesign.ws>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Physical key / edge detection software and PIN to generate private key
Date: Fri, 14 Mar 2014 12:49:19 -0500 [thread overview]
Message-ID: <CANg-TZB3snv+ny5NdwMic_NtSbMCvt_=qSViJHXeTsdU2Qnygg@mail.gmail.com> (raw)
In-Reply-To: <CAMPt2UN=ySXRP04cB+Cx3frF0u9F2yWoHCVZsvz5VG=ZEaZJCw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]
On Thu, Mar 13, 2014 at 9:38 PM, Jack Scott <jack.scott.public@gmail.com>wrote:
> BIP: XX
> Title: Physical key / edge detection software and PIN to generate a
> Bitcoin private key
> Author: Jack Scott
> Status: Idea
> Type: Standard Track
> Created: 13-3-2014
>
> Abstract:
> A method is proposed to generate a Bitcoin private key by using a physical
> key in conjunction with image recognition software and a PIN. Use edge
> detection software applied to incoming video feed to convert the shape of a
> physical key into an equation that describes the key. The hash of the
> key's equation plus a user generated five digit pin can then be used to
> create a Bitcoin private key.
>
>
Interesting idea, though as Wladimir mentioned, a real-world "key" is much
less secure than a Bitcoin/PGP "key", though in this case, I could see your
physical/visual "key" being any complex, high-contrast image (like a Motion
Tracking Target: https://www.google.com/search?q=tracking+markers&tbm=isch),
if just using edge-detection (a high-contrast image would help make
low-light or out-of-focus shots still able to be detected), though like a
QR-code, it should probably have calibration markers in the corners to
specify orientation (would help decoding a skewed or rotated image) and the
standard should enforce some minimum level of complexity to prevent really
simple and easy-to-reproduce/steal keys .
Though if you're getting to that level of complexity, you might as well
just have a QR code of the private key.
Brooks
[-- Attachment #2: Type: text/html, Size: 2170 bytes --]
prev parent reply other threads:[~2014-03-14 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 2:38 [Bitcoin-development] Physical key / edge detection software and PIN to generate private key Jack Scott
2014-03-14 3:19 ` Wladimir
2014-03-14 17:49 ` Brooks Boyd [this message]
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='CANg-TZB3snv+ny5NdwMic_NtSbMCvt_=qSViJHXeTsdU2Qnygg@mail.gmail.com' \
--to=boydb@midnightdesign.ws \
--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