summaryrefslogtreecommitdiff
path: root/83/e1eb9f062e0ef894c240b7e61a420dd07f6890
blob: e58d06bf7bc3eaeb5724d59fc10a7d92ba05c938 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
Return-Path: <gmaxwell@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id D4FE9E68
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 24 Jan 2018 10:31:37 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f44.google.com (mail-vk0-f44.google.com
	[209.85.213.44])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 70C33149
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 24 Jan 2018 10:31:37 +0000 (UTC)
Received: by mail-vk0-f44.google.com with SMTP id g186so2201877vkd.8
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 24 Jan 2018 02:31:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:sender:in-reply-to:references:from:date:message-id
	:subject:to:cc;
	bh=gHEOCcy5F8uTdODeilCZDykEiOC/hbNpHzKCjaJKFCQ=;
	b=K1wa4zPaUbivm0qBqGbvQekIlMbnzUAgq4QPKZFMT1a2BKZYMxmUGtRqK7BILMUIfw
	ZTbKsj5UgqAw4q/n2VuLzGZF0+NHDUouPhKTzwz3g72HjioPG9lBNswyfcuxy3klxPrr
	jLchSSNJu/AyjxBZmHLJ12UzdzDJlrGHnFI8uvhZoLLEwpSkRuS0Kh7ylOnsTux/VzzI
	GHyF1tLilT3Fpy2atcJsWi3R/Mlr2NyPWSRBxEWTBo9oSyHVGe9FF3DCTit8TkM7NuD0
	6wqJYDdg0JX/aO/xa7iXmJMO0e2x59IjVdeowUURxEMxUrh4LK5asYeoAhg8I413E+jW
	vmdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
	:date:message-id:subject:to:cc;
	bh=gHEOCcy5F8uTdODeilCZDykEiOC/hbNpHzKCjaJKFCQ=;
	b=Y+sA/elbdQIXwAOCoSfeWvnlskc3Xj+VBm/pjNHcNbuo0qzf/Hmefc62p2h8tQnPot
	ROqfyloIg+G+yYQuFYNn0/N1rTxKCSedMqXK7wfaEG/ZlQQ6ZH6euHa2sYIXvsUM5XJ6
	MBYSLMaksDWBsjxVU8MbZtFMYDt62rsOE6Y1AsRngy0d6EOWwrn5igod7PEZgKUwiYtS
	qbvVCl1bnRxTniD1urlT2Ikogg5DcNgur9Z8ICKoSxqr85sYzmhe5RXlVFzPTzCUeOb8
	4xmJcSrl1xdP3aAplZ1xmd9Zl0UC617HQpRwNKBjTemYqMIg/4ZCh3SRZtln3GOiSD9L
	zatA==
X-Gm-Message-State: AKwxytfexGJwgaEbOy09h+FkGyW5j+B/KvauCsBGaeD+os4MyevGS2rJ
	ZdXOpJUgn12oF/ad4zC/Pg5pk/kWe6MpJi9AMQs=
X-Google-Smtp-Source: AH8x226BA8j4AtCZCtFAvVKpOPRbsml4uWCCuDKH++Ya+yCyfpcVmoZickhEg24TaJy1F5hjR/us/DiI6IAjX236xqA=
X-Received: by 10.31.168.20 with SMTP id r20mr3989218vke.149.1516789896604;
	Wed, 24 Jan 2018 02:31:36 -0800 (PST)
MIME-Version: 1.0
Sender: gmaxwell@gmail.com
Received: by 10.103.78.155 with HTTP; Wed, 24 Jan 2018 02:31:35 -0800 (PST)
In-Reply-To: <41d8ff42-106f-45b9-cc70-507982c7336b@gmail.com>
References: <CAJRVQkBPQR3Gz3AtWFgK_Z_9vDVZvR4Ws=f+tUZ3Y0mdswuk_g@mail.gmail.com>
	<CAAS2fgQmKY5206-ko9ttV4K_4aPfoWh7Jrx=XYetXLeknU30iw@mail.gmail.com>
	<41d8ff42-106f-45b9-cc70-507982c7336b@gmail.com>
From: Gregory Maxwell <greg@xiph.org>
Date: Wed, 24 Jan 2018 10:31:35 +0000
X-Google-Sender-Auth: OozYuGJG5RTuAUJPTajc57P2sJo
Message-ID: <CAAS2fgTT+9DydafDfA3S1_KSDO+hDkA4sNiBmUn+2kHpf5cFag@mail.gmail.com>
To: Aymeric Vitte <vitteaymeric@gmail.com>
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, FREEMAIL_FROM,
	RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
	=?UTF-8?B?0JDRgNGC0ZHQvCDQm9C40YLQstC40L3QvtCy0LjRhw==?=
	<theartlav@gmail.com>
Subject: Re: [bitcoin-dev] Why is deriving public key from the signature not
 used in Segwit?
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jan 2018 10:31:37 -0000

On Wed, Jan 24, 2018 at 10:24 AM, Aymeric Vitte <vitteaymeric@gmail.com> wrote:
> out the fact that pubkey is there now even for standard p2pkh
> transactions and it was not the case some time ago
>
> But I never got any answer regarding what motivated this change
> (compared to the previous behavior) and when, so whether I am missing
> something obvious, whether nobody wants to answer

No such behaviour ever existed, you are simply mistaken.