From: "Clément Elbaz" <clem.ds@gmail•com>
To: Andreas Schildbach <andreas@schildbach•de>,
bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] QR code alternatives (was: Proposal: extend bip70 with OpenAlias)
Date: Tue, 21 Jul 2015 08:42:02 +0000 [thread overview]
Message-ID: <CAP63atZdnDjdvtwDVq36uBO3TRch9e1=6ueRgicKxm_dRs2b7w@mail.gmail.com> (raw)
In-Reply-To: <mokvc1$p4m$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]
As a side note, you may be interested about the 2D-Doc, which is a new
French standard used to protect documents such as address proofs or
invoice. I've been involved with it closely at work.
Every 2d-Doc include an ECDSA signature inside a 2D barcode, the key being
that the barcode is a Datamatrix and not a QR code.
If any of you can read French, the technical specification of the standard
can be found here ::
https://ants.gouv.fr/content/download/516/5665/version/4/file/ANTS_2D-Doc_CABSpec_v2.0.1_erratum.pdf
Basically, a short summary of the protected document is encoded inside the
barcode, followed by an ECDSA signature of the summary (still in the
barcode). The signature is done by an official, government-approved 2D-Doc
emitter. The 2D-Code contains a short reference (a few bytes) to designate
which emitter signed it, and then you can lookup the 2D-Doc TSL supplied by
the French government to get all the X509 Certificates from every emitters
you are interested in, in order to check the signature.
While 2D-Doc solve a very different problem than Bitcoin + BIP70, you may
be interested in knowing about it as hundred of thousands of them have been
emitted successfully while solving one of the problem you face : embedding
an ECDSA signature inside a 2D barcode.
Thank you for your time,
Clément Elbaz
Le mar. 21 juil. 2015 à 10:20, Andreas Schildbach via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> a écrit :
> Hmm, the advanced QR code standards are perhaps even useful if we don't
> change anything about BIP7x. Because if we can cram more data without
> loosing scanning performance this maybe means also we can stay with the
> data we have but improve scanning?
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 2666 bytes --]
next prev parent reply other threads:[~2015-07-21 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 14:40 Mike Hearn
2015-07-21 8:20 ` Andreas Schildbach
2015-07-21 8:42 ` Clément Elbaz [this message]
2015-07-21 10:25 ` Mike Hearn
2015-07-21 14:58 ` Thomas Voegtlin
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='CAP63atZdnDjdvtwDVq36uBO3TRch9e1=6ueRgicKxm_dRs2b7w@mail.gmail.com' \
--to=clem.ds@gmail$(echo .)com \
--cc=andreas@schildbach$(echo .)de \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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