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
|
Return-Path: <ZmnSCPxj@protonmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 7CC628DC
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 29 Jul 2019 03:39:24 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-40130.protonmail.ch (mail-40130.protonmail.ch
[185.70.40.130])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C12762C6
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 29 Jul 2019 03:39:23 +0000 (UTC)
Date: Mon, 29 Jul 2019 03:39:15 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=default; t=1564371561;
bh=iBHHQhXGawNeLrL6MCZrEZJ14ye3xwcVI9LOYR5S2hk=;
h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:
Feedback-ID:From;
b=AcTq/F6POb3Pd/ODa4b89alDiNf+PIH1zFG9EgHo9xHLQNUaTftaaQ1618ptS8t63
xxI9tHjuogjPtVLxMdg8/kn3578qJMoKtnMSRdmdk7KGJUISZfMzur+4oGznLUuscf
Cr/pkqmLd8ic93tV2Fo9KOJ4f9mVVvUFTYx/WiZE=
To: Mike Brooks <m@ib.tc>
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Reply-To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <E5wDa72WwYR4yBace7fEiptoIXt0wqitKoL-OP5NMh519Zp6nXGJEV2IxSgGTyeqcHyoQmFJC1O65_P63n_LRoBSEjQb9QhhnCdQNoB3L0I=@protonmail.com>
In-Reply-To: <CALFqKjT=6aYGqTkzqcf2c5dwApPDTTVGuyGt=Vxi6Ms43m-4nQ@mail.gmail.com>
References: <CALFqKjQkQwuxjeYkGWO_Y_HhNQmJgrjqF3m04hbORV7FSbsi3Q@mail.gmail.com>
<nk8ihWbf71QT6w-wVbnunppF_DjS8ywDoDAugBj5mYM_LCpSzec0j6lkaTKBK4t3CsXwRSXWmzbWiW7nmqT4y0W2fn8X-3oXv-TAYXwP1R4=@protonmail.com>
<CALFqKjQoA+4XKGePHEK9OAZv2+qg=Q669v=f=MpDtg4F3Fx4kQ@mail.gmail.com>
<dW426iyRLdy0-CbpWL9pG7dG8qvmyQizPrwuBVHpblJBCBDSMjeIuFMiTjNHOaMfUzjaW2btTiFD9PiozOt9Cv5DQUZG0o22hYndr2wk3SI=@protonmail.com>
<CALFqKjTfFJATAELn4F0vBGsjorH3a8nzwwtKfXNz_vgWC5XPTg@mail.gmail.com>
<dNlv6xp0FTd29mczIiw3uOIoDYcTMV44Az0UZ53XQs_8PGzmnMIBhses0kU_SpOZGUcNzWRlerJEZm-p3YQ8USNIxPBouVZdWYCa7HcxDG0=@protonmail.com>
<CALFqKjT=6aYGqTkzqcf2c5dwApPDTTVGuyGt=Vxi6Ms43m-4nQ@mail.gmail.com>
Feedback-ID: el4j0RWPRERue64lIQeq9Y2FP-mdB86tFqjmrJyEPR9VAtMovPEo9tvgA0CrTsSHJeeyPXqnoAu6DN-R04uJUg==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, FROM_LOCAL_NOVOWEL,
RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Mon, 29 Jul 2019 07:24:25 +0000
Cc: bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] PubRef - Script OP Code For Public Data References
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: Mon, 29 Jul 2019 03:39:24 -0000
Good morning Mike,
> =C2=A0 > The problem with transaction being pruned is that the data in th=
em might now be used in a *future* `OP_PUBREF`.
>
> I can see how pruning is needed for scalability, and pruning=C2=A0can be =
made compatible with a reference to a transaction. If a transaction is prun=
ed, then the key material used in a prune'ed block's PUSHDATA operations ar=
e of no value.=C2=A0 A user of the network shouldn't need to make this kind=
of PUBREF, and if a user did want to bring a wallet back from the dead - t=
hen the utility of PUBREF wouldn't be available to them.
I believe you misunderstand the point completely.
Currently Bitcoin Core has a mode, called pruning, where:
1. It validates ***all*** transactions.
2. It throws away the transaction data of a block ***after*** validation.
3. It keeps only the UTXO set of ***all*** addresses, not just a specific =
wallet.
Given the above, if a transaction block 1000 `OP_PUBREF`s to a `OP_PUSHDATA=
` in block 100, how does the pruned validator get access to this data (Whic=
h was pruned after the pruned validator handled block 100)?
Note that pruned nodes ***are*** fullnodes and validate all transactions, n=
ot just those that involve their wallet.
Regards,
ZmnSCPxj
|
