summaryrefslogtreecommitdiff
path: root/f4/20c5506cf2eae376a6d600047afba34c8f6a7f
blob: cb01baea89f1a5451bf64f1df1732d97f7a5fceb (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
88
89
90
91
92
93
94
95
96
97
Return-Path: <AdamISZ@protonmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 58CCBC002F
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 24 Jan 2022 14:44:02 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp1.osuosl.org (Postfix) with ESMTP id 3A71683F71
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 24 Jan 2022 14:44:02 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -0.203
X-Spam-Level: 
X-Spam-Status: No, score=-0.203 tagged_above=-999 required=5
 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
 autolearn=ham autolearn_force=no
Authentication-Results: smtp1.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=protonmail.com
Received: from smtp1.osuosl.org ([127.0.0.1])
 by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id wYLcbiILgDCV
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 24 Jan 2022 14:44:01 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from mail-40134.protonmail.ch (mail-40134.protonmail.ch
 [185.70.40.134])
 by smtp1.osuosl.org (Postfix) with ESMTPS id E8F0C828C5
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 24 Jan 2022 14:44:00 +0000 (UTC)
Date: Mon, 24 Jan 2022 14:43:53 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
 s=protonmail2; t=1643035438;
 bh=ZSAKID99suDp32WMLRZ95BPHsh+3GJYY89F88Ba0f8M=;
 h=Date:To:From:Reply-To:Subject:Message-ID:From:To:Cc;
 b=jsy72Ba0rOCEF1GR0F/O6Ts24j8gfYu+WUdiUscFsoJLEg5EK4Anuuxao8EK1U8Ym
 7+FpxjBLMnpgaMfPWnVVwFnkj/bcwDtn/onGR9W38v/H9zPWHbTi9evj9RLmqgasfy
 2YLOoz+n3fWJRSjZLUx3c3Pa9DvncMkd04gt9jjEeLZKk6NmEn/w/QFTAhKIBFw8br
 dv3mUXVAkT4HggY3BPpFygcizr9P87pf/iddu8f4H5cZRHNv7pKpnHV4BRaVstUXwy
 FavNaXO6Uz863mEz8SG6ZrhqOXaSpqMdf71WqjtEdh2rCsHsWpLQ2dVWpZ8vetQ+up
 AwwB3I4cUUTzQ==
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: AdamISZ <AdamISZ@protonmail.com>
Reply-To: AdamISZ <AdamISZ@protonmail.com>
Message-ID: <jMANAdspMdPb1ZCFttQ3tGmkZ0oYojLY5Oz1d8ZSNl3JhZeDuT1xK0vxTu8uyHcgPXWsM_6XNb3R9tVD3_Yez88pviFrCaNt7LPqdWVBWus=@protonmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 24 Jan 2022 14:51:13 +0000
Subject: [bitcoin-dev] PathCoin
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: Mon, 24 Jan 2022 14:44:02 -0000

Hello list,

I took the time to write up this rather out-there idea:

Imagine you wanted to send a coin just like email, i.e. just transfer data =
to the counterparty.

Clearly this is in general entirely impossible; but with what restrictions =
and assumptions could you create a toy version of it?

See this gist for a detailed build up of the idea:

https://gist.github.com/AdamISZ/b462838cbc8cc06aae0c15610502e4da

Basically: using signature adaptors and CTV or a similar covenant, you coul=
d create a fully trustless transfer of control of a utxo from one party to =
another with no interaction with the rest of the group, at the time of tran=
sfer (modulo of course lots and lots of one-time setup).

The limitations are extreme and as you'd imagine. In the gist I feel like I=
 got round one of them, but not the others.

(I very briefly mention comparison to e.g. statechains or payment pools; th=
ey are making other tradeoffs against the 'digital cash' type of goal. Ther=
e is no claim that this 'pathcoin' idea is even viable yet, let alone bette=
r than those ideas).

Publishing this because I feel like it's the kind of thing imaginative mind=
s like the ones here, may be able to develop further. Possibly!


waxwing / AdamISZ