š
Original date posted:2015-01-16
š Original message:Since we only need the sorting for creating the scriptPubKey,
wouldn't it make the most sense to sort it by the way it represented in
that context?
On Thu, Jan 15, 2015 at 2:03 PM, Wladimir <laanwj at gmail.com> wrote:
> On Thu, Jan 15, 2015 at 1:17 AM, Matt Whitlock <bip at mattwhitlock.name>
> wrote:
> > 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?
>
> OP_CHECKSIG (and OP_CHECKSIGVERIFY) takes a DER-encoded pubkey and a
> DER-encoded signature on the stack.
>
> Possibly you're confused with OP_HASH160 <hash160> OP_EQUALVERIFY as
> used in outputs, which compares the 160-bit hash of the pubkey against
> the given hash (usually taken from a bitcoin address).
>
> It doesn't help understanding to consider either as integers. They are
> binary blob objects with either a fixed format (DER) or a fixed size
> (hashes).
>
> Wladimir
>
--
BlockTrail B.V.
Barbara Strozzilaan 201
1083HN Amsterdam
The Netherlands
Phone: +31 (0)612227277
E-mail: ruben at blocktrail.com
Web: www.blocktrail.com
Github: www.github.com/rubensayshi
BlockTrail B.V. Is registered with the Dutch Chamber of Commerce in
Amsterdam with registration No.:60262060 and VAT No.:NL853833035B01
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150116/6dcebfd8/attachment.html>;
Ruben de Vries [ARCHIVE] /
npub1u7ā¦9tmku
2023-06-07 15:28:32
in reply to nevent1qā¦2x83
Author Public Key
npub1u77xvkrrl5w2ygqggk44xmumt75xc3jlcsez4cguuxds23gj658se9tmkuPublished at
2023-06-07 15:28:32Event JSON
{
"id": "f1b89010a511ed97ddf24d3f3d03898e5c310e30293754cac42ac7eb456e58a4",
"pubkey": "e7bc665863fd1ca2200845ab536f9b5fa86c465fc4322ae11ce19b054512d50f",
"created_at": 1686151712,
"kind": 1,
"tags": [
[
"e",
"ef9480e99ea56d0362e9d11aa3d3348112e8c8b0adbfbdfee1624a1e22a745a8",
"",
"root"
],
[
"e",
"0b928bbf339190548b9847a7f26e7998ed1258f1ad88be91e9edf822c2657c03",
"",
"reply"
],
[
"p",
"e899768d254f3537af7e26455968583632d0ab0bd4c780445eacfa087ac80d8f"
]
],
"content": "š
Original date posted:2015-01-16\nš Original message:Since we only need the sorting for creating the scriptPubKey,\nwouldn't it make the most sense to sort it by the way it represented in\nthat context?\n\n\nOn Thu, Jan 15, 2015 at 2:03 PM, Wladimir \u003claanwj at gmail.com\u003e wrote:\n\n\u003e On Thu, Jan 15, 2015 at 1:17 AM, Matt Whitlock \u003cbip at mattwhitlock.name\u003e\n\u003e wrote:\n\u003e \u003e On Wednesday, 14 January 2015, at 3:53 pm, Eric Lombrozo wrote:\n\u003e \u003e\u003e Internally, pubkeys are DER-encoded integers.\n\u003e \u003e\n\u003e \u003e I thought pubkeys were represented as raw integers (i.e., they're\n\u003e embedded in Script as a push operation whose payload is the raw bytes of\n\u003e the big-endian representation of the integer). As far as I know, DER\n\u003e encoding is only used for signatures. Am I mistaken?\n\u003e\n\u003e OP_CHECKSIG (and OP_CHECKSIGVERIFY) takes a DER-encoded pubkey and a\n\u003e DER-encoded signature on the stack.\n\u003e\n\u003e Possibly you're confused with OP_HASH160 \u003chash160\u003e OP_EQUALVERIFY as\n\u003e used in outputs, which compares the 160-bit hash of the pubkey against\n\u003e the given hash (usually taken from a bitcoin address).\n\u003e\n\u003e It doesn't help understanding to consider either as integers. They are\n\u003e binary blob objects with either a fixed format (DER) or a fixed size\n\u003e (hashes).\n\u003e\n\u003e Wladimir\n\u003e\n\n\n\n-- \nBlockTrail B.V.\nBarbara Strozzilaan 201\n1083HN Amsterdam\nThe Netherlands\n\nPhone: +31 (0)612227277\nE-mail: ruben at blocktrail.com\nWeb: www.blocktrail.com\nGithub: www.github.com/rubensayshi\n\nBlockTrail B.V. Is registered with the Dutch Chamber of Commerce in\nAmsterdam with registration No.:60262060 and VAT No.:NL853833035B01\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150116/6dcebfd8/attachment.html\u003e",
"sig": "6fdc798fd9392192c5923f7aa54cb5478d7d53de89357413d8fd40a17f6694b825d74ec8af85eaa0b4a115bfe204a1935c561450339c77893d917ffe8f1593c5"
}