* [bitcoin-dev] BIP-38 issue and altchain support
@ 2015-09-14 19:54 Eric Voskuil
0 siblings, 0 replies; only message in thread
From: Eric Voskuil @ 2015-09-14 19:54 UTC (permalink / raw)
To: bitcoin-dev, Neill Miller
[-- 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 --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-09-14 19:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-09-14 19:54 [bitcoin-dev] BIP-38 issue and altchain support Eric Voskuil
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox