summaryrefslogtreecommitdiff
path: root/b1/b0af31358c00a03cfa99ebb2c4267015ef7f85
blob: 440198eb831831a3d38a3a1e150f082dbd517b64 (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
98
99
100
101
102
103
104
105
106
107
108
Return-Path: <ZmnSCPxj@protonmail.com>
Received: from fraxinus.osuosl.org (smtp4.osuosl.org [140.211.166.137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 08A90C016F
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 10 Jun 2020 06:47:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by fraxinus.osuosl.org (Postfix) with ESMTP id EC391869E1
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 10 Jun 2020 06:47:40 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from fraxinus.osuosl.org ([127.0.0.1])
 by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id uy-YSoPfmHb9
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 10 Jun 2020 06:47:39 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-40141.protonmail.ch (mail-40141.protonmail.ch
 [185.70.40.141])
 by fraxinus.osuosl.org (Postfix) with ESMTPS id 59A0386920
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 10 Jun 2020 06:47:39 +0000 (UTC)
Date: Wed, 10 Jun 2020 06:47:28 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
 s=protonmail; t=1591771657;
 bh=0Nwu0L3BJXGlg6zMZv5UvAdaWWiAU6E41fYw3rP+k7U=;
 h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From;
 b=UHoAJ8eLDGEoPybPqzhwrTsNQ3CQS6f88ufAr/gVjV9LPfrYpkj1Mc+HRRw4coRnl
 UmK2Di91JPUG8+Odw00BMpcCMo5IliPNnQPV9ti2vcenpzOboG2Lb3QV/KV2Mgaz9+
 jomgdZPn5fCHEIU6/qkO2LnF33ZFVnULm87NMs/g=
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Reply-To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Message-ID: <Ke7oBPiiaYh_IZr8DdhdRAEsYnZS_mA8EQIKLEaggUUHZtsT8TAaVy6cWs2NamHBOpwCv6cVfI1vr2RxsCh5W1M3DWsfxGAUtPex86-39xw=@protonmail.com>
In-Reply-To: <sjC0RVZr0Uyg5QKjgmAQfNibCUtaG-r_XEO8xDgPd7GIjLKSEybd47utANFWA53yySigMzqfiotpbCdFy-M5NcxJN1J6cCQO1r3sR1-eVks=@protonmail.com>
References: <7c0dc46538f96032596163c4a9f03dc2.squirrel@giyzk7o6dcunb2ry.onion>
 <sjC0RVZr0Uyg5QKjgmAQfNibCUtaG-r_XEO8xDgPd7GIjLKSEybd47utANFWA53yySigMzqfiotpbCdFy-M5NcxJN1J6cCQO1r3sR1-eVks=@protonmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [bitcoin-dev] Question about PayJoin effectiveness
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: Wed, 10 Jun 2020 06:47:41 -0000

Good morning again Mr. Lee,

> > I am trying to learn about payjoin. I have a couple concerns on its
> > effectiveness. Are my concerns valid or am I missing something?
> > concern 1
> > If it is known to be a payjoin transaction anyone could determine the
> > sender the recipient and amount right?
> > Lets assume that everyone has a single utxo because payjoin becomes com=
mon
> > use and payjoin consolidates utxos through "snowballing". If Alice has =
a
> > UTXO of 0.05 btc and Bob has a UTXO of 1.15 btc. Bob can be assumed to
> > have more balance because he is a merchant and his customers payjoin hi=
m
> > payments alot.


It is also helpful to remember that Bob cannot exist in isolation, and ther=
efore, Bob probably has:

* Employees.
* Suppliers.
* Shareholders.

For example, suppose Bob holds in reserve a 0.05 BTC UTXO in a holding wall=
et.

Then Bob takes the 1.16 UTXO it got from Alice and transfers 1.12 BTC to th=
e holding wallet:

    Bob merchant wallet 1.16 --___-- 1.17 Bob holding wallet
    Bob holding wallet  0.05 --   -- 0.04 Bob merchant wallet

The above looks exactly like one of the "customer pays Bob" transactions, b=
ut is in fact different.

Then Bob uses the holding wallet to pay out to employees, suppliers, and sh=
areholders, such as in a single large batched transaction, and then leaves =
behind another 0.05 BTC in the holding wallet (or some random small number =
of BTC) for the next time Bob has to pay to employees/suppliers/shareholder=
s.

So the transaction below:

    1.16 --___-- 1.17
    0.05 --   -- 0.04

*could* be interpreted as the 0.05 owner paying to the 1.16 owner, but in f=
act that is just Bob preparing the incoming funds from the merchant front-e=
nd for processing to send to its own liabilities.

Regards,
ZmnSCPxj