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
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
|
Return-Path: <dscotese@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 283B7162C
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 4 Oct 2019 01:37:47 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io1-f53.google.com (mail-io1-f53.google.com
[209.85.166.53])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5FE155D3
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 4 Oct 2019 01:37:46 +0000 (UTC)
Received: by mail-io1-f53.google.com with SMTP id c6so9934998ioo.13
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 03 Oct 2019 18:37:46 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=eh2wWGt0UphBGlEMmfQ+u1t4JJ2owWMTsQF/LD23j6Y=;
b=amj2Ueot0yiCDiKETlUD7b+9GAdSt/mol2huZ8ueNwNsarWBgGt4sXk8GFGOFyihmr
ljtbAkbFOPiTdsZdmu6N5zS2/Wb0UKqcYRjhwEARcsbknE8scaWF7x9w5ecwVLpYvcrk
KbiQPwdKeDiVrffMFa5e971BMddHxrjW3IWiEmkYzgICLHZj/Dg0S2eWcttWy3Pwy3zm
KUcr2xVWG/iQ6I7R28Hdlix1cOWt7mKDczisK4sztOwA6S/qpmzXM3V9wOizIsifBuSZ
AwVpeimXxO4zSWMFBlNXHwC3DCmlnPZ6Regpu2eT90ysiCa89oypyydRzGzkbZkX73V1
umGQ==
X-Gm-Message-State: APjAAAV7Wrs/B+rdDRXJhIr5EuLTOT/7no1rDkCxrPQp+QexEIPhfK3c
qpfr/jtXPCJpC+YVmUE/yDDN65yzsyn+GQ5K1wLSZ1fT
X-Google-Smtp-Source: APXvYqy0JwSuGOQGkc+Sr81T1x2TyaRFRTS0Bguy4jzWd7uaCBsoKg49FnvkzAXJZ2tJZ9whoCMMKjZZGMKUbTwJIDg=
X-Received: by 2002:a05:6e02:4d0:: with SMTP id
f16mr12890347ils.17.1570153065464;
Thu, 03 Oct 2019 18:37:45 -0700 (PDT)
MIME-Version: 1.0
From: Dave Scotese <dscotese@litmocracy.com>
Date: Thu, 3 Oct 2019 18:37:33 -0700
Message-ID: <CAGLBAheDMFkFtJG1gLf61ZZ9U3rasZ_T6f_sAHWWRiAcNWiO8A@mail.gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000b5c88105940bbf9d"
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, DOS_RCVD_IP_TWICE_B,
FREEMAIL_FROM, HTML_MESSAGE,
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
Subject: [bitcoin-dev] Smaller "Bitcoin address" accounts in the blockchain.
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: Fri, 04 Oct 2019 01:37:47 -0000
--000000000000b5c88105940bbf9d
Content-Type: text/plain; charset="UTF-8"
Currently, bitcoin must be redeemed by providing input to a script which
results in the required output. This causes the attached amount of bitcoin
to become available for use in the outputs of a transaction. Is there any
work on creating a shorter "transaction" which, instead of creating a new
output, points to (creates a virtual copy of) an existing (unspent) output
with a larger amount attached to it? This would invalidate the smaller,
earlier UTXO and replace it with the new one without requiring the earlier
one to be redeemed, and also without requiring the original script to be
duplicated. It is a method for aggregating bitcoin to a UTXO which may
otherwise not be economically viable.
The idea is that there already exists a script that must be satisfied to
spend X1, and if the owner of X1 would like to have the same requirements
for spending X2, this would be a transaction that does that using fewer
data bytes. Since the script already exists, the transaction can simply
point to it instead of duplicating it.
This would also enable the capacity of lightning channels to be increased
on the fly without closing the existing channel and re-opening a new one.
The LN layer would have to cope with the possibility that the "short
channel ID" could change.
Dave.
--000000000000b5c88105940bbf9d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Currently, bitcoin must be redeemed by providing inpu=
t to a script which results in the required output.=C2=A0 This causes the a=
ttached amount of bitcoin to become available for use in the outputs of a t=
ransaction.=C2=A0 Is there any work on creating a shorter "transaction=
" which, instead of creating a new output, points to (creates a virtua=
l copy of) an existing (unspent) output with a larger amount attached to it=
?=C2=A0 This would invalidate the smaller, earlier UTXO and replace it with=
the new one without requiring the earlier one to be redeemed, and also wit=
hout requiring the original script to be duplicated.=C2=A0 It is a method f=
or aggregating bitcoin to a UTXO which may otherwise not be economically vi=
able.</div><div><br></div><div>The idea is that there already exists a scri=
pt that must be satisfied to spend X1, and if the owner of X1 would like to=
have the same requirements for spending X2, this would be a transaction th=
at does that using fewer data bytes.=C2=A0 Since the script already exists,=
the transaction can simply point to it instead of duplicating it.<br></div=
><div><br></div><div>This would also enable the capacity of lightning chann=
els to be increased on the fly without closing the existing channel and re-=
opening a new one.=C2=A0 The LN layer would have to cope with the possibili=
ty that the "short channel ID" could change.</div><div><br></div>=
<div>Dave.<br></div></div>
--000000000000b5c88105940bbf9d--
|
