public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed

From: Eric Voskuil <eric@voskuil•org>
To: bitcoin-dev@lists•linuxfoundation.org,
	 Neill Miller <neillm@thecodefactory•org>
Subject: [bitcoin-dev] BIP-38 issue and altchain support
Date: Mon, 14 Sep 2015 12:54:39 -0700	[thread overview]
Message-ID: <55F725FF.8030507@voskuil.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]

In the integration of BIP-38 into libbitcoin we ran into two issues.

First, the scenario that justifies the "confirmation code" is flawed. We
have implemented full support for this, but have also marked it as
deprecated.

I am seeking counter arguments, in case there is some scenario that we
haven't imagined where it might be useful. Details here:

[TLDR: the confirmation code cannot prove anything about the owner's
ability to spend from the public-key/address that it confirms.]

https://github.com/libbitcoin/libbitcoin/wiki/BIP38-Security-Considerations

Second, BIP-38 envisions altchain integration but doesn't specify it. We
have implemented the capability, documented here:

[TLDR: incorporate the payment address version into the last byte of the
encoded encrypted key prefixes, with backward compatibility]

https://github.com/libbitcoin/libbitcoin/wiki/Altchain-Encrypted-Private-Keys

If there is sufficient support I'll write up a Proposal that modifies
BIP-38.

Thanks to Neill Miller for the libbitcoin and bx BIP-38 pull requests.

e


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

                 reply	other threads:[~2015-09-14 19:54 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=55F725FF.8030507@voskuil.org \
    --to=eric@voskuil$(echo .)org \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=neillm@thecodefactory$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox