public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Russell O'Connor" <roconnor@blockstream.io>
To: Jonas Schnelli <dev@jonasschnelli.ch>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] New serialization/encoding format for key material
Date: Wed, 13 Jun 2018 10:58:33 -0400	[thread overview]
Message-ID: <CAMZUoKkstFOrA3xR7S1j2xJVYG+9L72TrLjAhFdPrQwwVyxXgA@mail.gmail.com> (raw)
In-Reply-To: <03557E21-8CFC-4822-8494-F4A78E23860B@jonasschnelli.ch>

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

On Tue, May 29, 2018 at 5:13 AM, Jonas Schnelli via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Hi
>
> If 520 bits are present, first 256 bits are the BIP32 chain code, to
> second 264
> bits (33 bytes) define the public key (according to BIP32)
>

In a 33 byte compressed public key, only 1 bit from the first byte conveys
information.  The other 7 bits can be discarded.  This will allow you to
reduce the bech32 encoded result by one character.

[-- Attachment #2: Type: text/html, Size: 895 bytes --]

  reply	other threads:[~2018-06-13 14:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29  9:13 [bitcoin-dev] New serialization/encoding format for key material Jonas Schnelli
2018-06-13 14:58 ` Russell O'Connor [this message]
2018-05-30  6:30 shiva sitamraju
2018-05-30 14:08 ` Gregory Maxwell
2018-05-30 19:03 ` Jonas Schnelli
2018-06-03 16:51   ` Jonas Schnelli
2018-06-03 19:23     ` Pieter Wuille
2018-06-03 21:30       ` Jonas Schnelli
2018-06-13  2:44         ` Pieter Wuille
2018-06-15 15:54       ` Russell O'Connor
2018-06-23 19:49         ` Pieter Wuille

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=CAMZUoKkstFOrA3xR7S1j2xJVYG+9L72TrLjAhFdPrQwwVyxXgA@mail.gmail.com \
    --to=roconnor@blockstream.io \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=dev@jonasschnelli.ch \
    /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