public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Matt Whitlock <bip@mattwhitlock.name>
To: bitcoin-development@lists.sourceforge.net
Cc: Ruben de Vries <ruben@blocktrail.com>, Jeffrey Paul <jp@eeqj.com>
Subject: Re: [Bitcoin-development] convention/standard for sorting public keys for p2sh multisig transactions
Date: Wed, 14 Jan 2015 20:17:52 -0500	[thread overview]
Message-ID: <3382316.6TbFyFjyI6@crushinator> (raw)
In-Reply-To: <CABr1YTdqUxBs3+dMmtZ5dQvxP8MBFgttCdJ9cuvy10LdwAKaYQ@mail.gmail.com>

On Wednesday, 14 January 2015, at 3:53 pm, Eric Lombrozo wrote:
> Internally, pubkeys are DER-encoded integers.

I thought pubkeys were represented as raw integers (i.e., they're embedded in Script as a push operation whose payload is the raw bytes of the big-endian representation of the integer). As far as I know, DER encoding is only used for signatures. Am I mistaken?



  parent reply	other threads:[~2015-01-15  1:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 16:37 [Bitcoin-development] convention/standard for sorting public keys for p2sh multisig transactions Ruben de Vries
2015-01-14 17:39 ` devrandom
2015-01-14 18:00   ` Eric Lombrozo
2015-01-14 18:58   ` Jean-Pierre Rupp
2015-01-14 19:27   ` Jeffrey Paul
2015-01-14 19:58     ` Pavol Rusnak
2015-01-14 23:53     ` Eric Lombrozo
     [not found]       ` <CALKy-wreXNohc_Pe_DLBS1cXoS-3j8C_F7WsKuU=CYYKF9NB1Q@mail.gmail.com>
2015-01-15  1:09         ` Eric Lombrozo
2015-01-15  1:17       ` Matt Whitlock [this message]
2015-01-15 12:33         ` Jean-Pierre Rupp
     [not found]         ` <CA+s+GJCsta-FesGv7zW_i2pEtZM5U20ZqP2V_Oog_LBtQBbe-w@mail.gmail.com>
2015-01-16 10:16           ` Ruben de Vries
2015-01-16 16:34             ` Thomas Kerin
2015-01-16 17:09               ` Alan Reiner
2015-01-14 20:32 ` Jeff Garzik
2015-01-15 11:59   ` Jonathan Brown
2015-01-16 18:40 Jean-Pierre Rupp

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=3382316.6TbFyFjyI6@crushinator \
    --to=bip@mattwhitlock.name \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jp@eeqj.com \
    --cc=ruben@blocktrail.com \
    /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