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
|
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 14EB2C0051
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 5 Oct 2020 02:41:29 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by fraxinus.osuosl.org (Postfix) with ESMTP id 04517848A9
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 5 Oct 2020 02:41:29 +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 fxoH5DQqzsv1
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 5 Oct 2020 02:41:27 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-40132.protonmail.ch (mail-40132.protonmail.ch
[185.70.40.132])
by fraxinus.osuosl.org (Postfix) with ESMTPS id 2CF59848A0
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 5 Oct 2020 02:41:26 +0000 (UTC)
Date: Mon, 05 Oct 2020 02:41:14 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=protonmail; t=1601865684;
bh=PiNmr1AYUifZYJwsWQS8wfcAezpKhUVwFiHD56qqIwg=;
h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From;
b=OWSA5S9kiOoGjzLKkBbYoqwAhEE8iveqN/4MdoxALArdjP6cK4FQ270zO6SAtV7Uk
R19bzQ9nSLcHQU2ddffMZa/xD1HFk0owjRqqM8xIMiYbVsADSQ4+anbdjz12wTj7A1
+YTcAW07ZUzOPklMMxKShHCNsRqeJJEDPdbEjGyg=
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: <-9eIH0M9XOXDIGvFaSHljGrkKfd_N7q9POTV4wzobjSGljNwE3snOP2-jPE4Nh1IPovo8tTuQz_nSqgpLWI2hrD5_UGonfn-sjNo7oIbVXU=@protonmail.com>
In-Reply-To: <wptxI497skBUI-LOTu3QdUUnNW7v_NYA-BVyoqiDEAPAln6ezFlM2ZXm6ENKsiaMN9C5dZ1HtSTW0kVGnBbF_MKj7-9oY-BQg42C99cheJA=@protonmail.com>
References: <976903d1529adef2aff8839290a91f2c.squirrel@giyzk7o6dcunb2ry.onion>
<wptxI497skBUI-LOTu3QdUUnNW7v_NYA-BVyoqiDEAPAln6ezFlM2ZXm6ENKsiaMN9C5dZ1HtSTW0kVGnBbF_MKj7-9oY-BQg42C99cheJA=@protonmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [bitcoin-dev] A thought experiment on bitcoin for payroll
privacy
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, 05 Oct 2020 02:41:29 -0000
Good morning Mr. Lee,
> Permanent raises can justify permanently increasing the size of the chann=
el with the employee.
On reflection, this is a bad idea.
Suppose I am a cut-throat employee and I want to have an idea of the bi-wee=
kly salary of another employee.
I make some stupid bet, and lose, with the other employee.
I offer to pay the loss of my bet via Lightning, and the other employee, in=
all innocence, issues a Lightning invoice to me.
The Lightning invoice contains the actual node ID of the other employee.
And since I also have a channel with the cut-throat company, I know as well=
the node ID of the cut-throat company.
I can then look at the gossiped channels and see the size of the channel be=
tween the cut-throat company and the other employee, and from there, guess =
that this is the bi-weekly salary of that employee.
On the other hand --- once the employee has *any* funds at all, they can si=
milarly take an offchain-to-onchain swap, and then use the funds to create =
another channel to another part of the network.
The other employee as well can arrange incoming funds on that other channel=
by using offchain-to-onchain swaps to their cold storage.
Thus, as an employee gets promoted and pulls a larger bi-weekly salary, the=
channel with the cut-throat company becomes less and less an indicator of =
their *actual* bi-weekly salary, and there is still some deniability on the=
exact size of the salary.
At the same time, even if I know the node of the other employee, the size o=
f all its channels is also still not a very accurate indicator of their sal=
ary at the throat-cutting company.
For example, it could be a family node, and the other employee and all her =
or his spouses arrange to have their salaries paid to that node.
Or the other employee can also run a neck-reconstruction business on the si=
de, and also use the same node.
(Nodelets for the win?)
Regards,
ZmnSCPxj
|
