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
88
89
90
91
92
93
|
Return-Path: <vjudeu@gazeta.pl>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 66983C0001
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 23 May 2021 16:09:58 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 4E0CC4027A
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 23 May 2021 16:09:58 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.601
X-Spam-Level:
X-Spam-Status: No, score=0.601 tagged_above=-999 required=5
tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: smtp2.osuosl.org (amavisd-new);
dkim=pass (1024-bit key) header.d=gazeta.pl
Received: from smtp2.osuosl.org ([127.0.0.1])
by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id zWtRnKxzFp9Y
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 23 May 2021 16:09:56 +0000 (UTC)
X-Greylist: delayed 00:07:03 by SQLgrey-1.8.0
Received: from smtpo74.poczta.onet.pl (smtpo74.poczta.onet.pl [141.105.16.24])
by smtp2.osuosl.org (Postfix) with ESMTPS id 542E040265
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 23 May 2021 16:09:56 +0000 (UTC)
Received: from pmq7v.m5r2.onet (pmq7v.m5r2.onet [10.174.35.192])
by smtp.poczta.onet.pl (Onet) with ESMTP id 4Fp4qn5dJZz1tLL
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 23 May 2021 18:02:45 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gazeta.pl; s=2013;
t=1621785765; bh=uTl3z3B2BOk7y4SEB6dv+oknjanVSt7cAhyQu19DYaY=;
h=From:To:Date:Subject:From;
b=i7hnNf6QwNC65gGu7/+WN39AINs/q/k2POxgJs4BBdEwY9HOVOVNTP3ihTM3N2o8o
sW3SjQmoVKT3NW0lJ7JeWwLBrDNVlWXlL7CDKfnKpfB1bgZoA9srJqtyMuL/zenuGp
xLVJ0X56bbQ6WMa8P31m6T0JYJe6LFNUGV4H45ac=
Content-Type: multipart/alternative;
boundary="===============4215924749557260832=="
MIME-Version: 1.0
Received: from [5.173.226.233] by pmq7v.m5r2.onet via HTTP id
202105231801203373010001; Sun, 23 May 2021 18:02:45 +0200
From: vjudeu <vjudeu@gazeta.pl>
X-Priority: 3
To: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Date: Sun, 23 May 2021 18:02:45 +0200
Message-Id: <132101705-ebaab3ce4df3e652b9f8ce0ce856f62e@pmq7v.m5r2.onet>
X-Mailer: onet.poczta
X-Onet-PMQ: <vjudeu@gazeta.pl>;5.173.226.233;PL;1
X-Mailman-Approved-At: Sun, 23 May 2021 17:10:26 +0000
Subject: [bitcoin-dev] Tweaking tapscript instead of public key
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
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: Sun, 23 May 2021 16:09:58 -0000
This is a multi-part message in MIME format.
--===============4215924749557260832==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
As far as I know, P2TR address contains 32-byte public key. It can be used =
directly by creating Schnorr signature or indirectly, by revealing tapscrip=
t. Does it mean that any taproot output could be modified on-the-fly after =
being confirmed without changing an address? I mean, if we have base point =
as the private key with P2TR address tb1p0xlxvlhemja6c4dqv22uapctqupfhlxm9h=
8z3k2e72q4k9hcz7vqqzj3dz, then the owner of that key can modify spending co=
nditions without moving on-chain coins?
--===============4215924749557260832==
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
<div>As far as I know, P2TR address contains 32-byte public key. It can be =
used directly by creating Schnorr signature or indirectly, by revealing tap=
script. Does it mean that any taproot output could be modified on-the-fly a=
fter being confirmed without changing an address? I mean, if we have base p=
oint as the private key with P2TR address tb1p0xlxvlhemja6c4dqv22uapctqupfh=
lxm9h8z3k2e72q4k9hcz7vqqzj3dz, then the owner of that key can modify spendi=
ng conditions without moving on-chain coins?</div>
--===============4215924749557260832==--
|
