summaryrefslogtreecommitdiff
path: root/a6/35fdbd11ea99854006026f0e33bc9706a20527
blob: f741fe8c69e4d5bcd8737b945c73f2bca49fce41 (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
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
Return-Path: <antoine.riard@gmail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 6C0DBC0001
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 12 May 2021 14:35:50 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 469FE40377
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 12 May 2021 14:35:50 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001]
 autolearn=ham autolearn_force=no
Authentication-Results: smtp2.osuosl.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=gmail.com
Received: from smtp2.osuosl.org ([127.0.0.1])
 by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id DZGI449RsO0s
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 12 May 2021 14:35:48 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com
 [IPv6:2a00:1450:4864:20::32e])
 by smtp2.osuosl.org (Postfix) with ESMTPS id 28D0140002
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 12 May 2021 14:35:48 +0000 (UTC)
Received: by mail-wm1-x32e.google.com with SMTP id
 l18-20020a1ced120000b029014c1adff1edso782060wmh.4
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 12 May 2021 07:35:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:from:date:message-id:subject:to;
 bh=np//JaW71QMwbhXd7tb0ecupnJsSMAv8dAmKKf8K5a4=;
 b=jGgw+52NGF5OoQg8nsow7PCdb/eCUEZ0FUugAup3q9DagV8Agyq9YfInXNxCk+2x6i
 q9uapttaekwW4DPFnE11AWvNlHQfMz5KpAzIZMus+lRGJj/cguErJLlrn3tHcW6CrDEl
 SMCH7/zqRd675adK1SjX6j8bRUC53Su2WQNK6GlLLCfwczUogkVQ/5HRWTWLffApDXun
 c/0Q8sfmSvyW7cu6yod4AKru1h8Xdux5yL7gXGw+gb0udVGvyELqJcTGhHOmhpWE5uuI
 3oue3EOTlJE9vyUha1ZT2m8XMq0uSWtO2tfWdhcLF6aAQKcIkbH3/rN+RiOD654aym78
 3ewg==
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=np//JaW71QMwbhXd7tb0ecupnJsSMAv8dAmKKf8K5a4=;
 b=dGPVyLJmoutG4HxGkE/MaH2IvUx8/y5qJ2SCr1irDl15Avg4Tm9TRoBTlJQNZeZlVA
 +Qp2e0ATGX7eake27KPhr57bev6cysfAx6wwXawTatwQ27ASQBNFSIARDoX3AQ6uWI8w
 5XJNczUNLEFcAez6Cscjdt4rI3oav1WltwD8fVV3NYKAJ1ZaxpDS3Pe6l9nfx9ApK7+U
 6U777vM/sr2K1SMXPisjWHMWHIdFkpOAtuzUbAuGZOKEUpUsOE7MSDVH261ZRV/MAKz5
 oYG5WC6Br67NHGJuq4sM9vQLuMGyb1TtqXuyc5r9WFM7UJHEwvXKumDoTvAQ99MQkgVJ
 yC2g==
X-Gm-Message-State: AOAM5318nvIGYdl4vPQoKQQDWxyB9031V6khkf7WZ2YZawegOsNST1pj
 rYN11wJOk8dCvD1L2MOi/GzOvs0Le9LXogMfvUNRQl7gmhzdpg==
X-Google-Smtp-Source: ABdhPJw0vrYcr/Q6qJU1/kutHp1qxpnYEsz8PWk7B/hcWPAf8qvimrPTdQ7ULBQVal7OxtdeCTNhTgF3kphrQbsKsN0=
X-Received: by 2002:a7b:c196:: with SMTP id y22mr39424467wmi.1.1620830146016; 
 Wed, 12 May 2021 07:35:46 -0700 (PDT)
MIME-Version: 1.0
From: Antoine Riard <antoine.riard@gmail.com>
Date: Wed, 12 May 2021 10:35:34 -0400
Message-ID: <CALZpt+HFDq6MtqgO5qVeWXEmruMHTf_Dk9q6OKjsnC=xjJMgwA@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000183a4f05c222ed08"
X-Mailman-Approved-At: Wed, 12 May 2021 14:54:10 +0000
Subject: [bitcoin-dev] L2s Onchain Support IRC Workshop : Agenda & Schedule
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, 12 May 2021 14:35:50 -0000

--000000000000183a4f05c222ed08
Content-Type: text/plain; charset="UTF-8"

Hi,

Following-up on the workshop announcement [0], I'm proposing today's early
agenda and schedule.

Dates have been picked up 2 weeks after the end of the Miami's conference
as the american crowd will travel around and won't be necessary on their
keyboards. Also, if folks from Asia/Pacific timezones want to join or
participate, I'm all good to set up additional, more-friendly sessions.

* 1st meeting: Tuesday 15th June 19:00 - 20:30  UTC

Topics will be "Guidelines about L2 protocols onchain security design",
"Coordinated cross-layers security disclosures", "Full-RBF proposal".

* 2nd meeting: Tuesday 22th June 19:00 - 20:30 UTC

Topics will be "Package relay design and/or generic L2 fee-bumping
primitive".

I hope to address most of the issues in two sessions. If it doesn't fit, we
can still do a third one on the 29th June.

Discussions will happen on the new chan #l2-onchain-support freenode.

Meanwhile, I'll prepare a series of open questions and resource pointers
for each topic. Also, coming up with weaponized pinning attacks against LN
nodes and proposals on how you can improve double-spend protection
hopefully with package relay or p2p extensions if we move towards full-rbf.

If any L2 protocol dev/designer have specific transaction relay
requirements for their projects, especially ones far different from
Lightning, I'm really interested if you want to share them in the
L2-zoology repo (https://github.com/ariard/L2-zoology/tree/master/protocols)
or anywhere else. I'm doing my best to keep up with most L2 security
models, that said the space is growing fast :)

Cheers,
Antoine

[0]
https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-April/003002.html

--000000000000183a4f05c222ed08
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<br><br>Following-up on the workshop announcement [0], =
I&#39;m proposing today&#39;s early agenda and schedule.<br><br>Dates have =
been picked up 2 weeks after the end of the Miami&#39;s conference as the a=
merican crowd will travel around and won&#39;t be necessary on their keyboa=
rds. Also, if folks from Asia/Pacific timezones want to join or participate=
, I&#39;m all good to set up additional, more-friendly sessions.<br><br>* 1=
st meeting: Tuesday 15th June 19:00 - 20:30 =C2=A0UTC<br><br>Topics will be=
 &quot;Guidelines about L2 protocols onchain security design&quot;, &quot;C=
oordinated cross-layers security disclosures&quot;, &quot;Full-RBF proposal=
&quot;.<br><br>* 2nd meeting: Tuesday 22th June 19:00 - 20:30 UTC<br><br>To=
pics will be &quot;Package relay design and/or generic L2 fee-bumping primi=
tive&quot;.<br><br>I hope to address most of the issues in two sessions. If=
 it doesn&#39;t fit, we can still do a third one on the 29th June.<br><br>D=
iscussions will happen on the new chan #l2-onchain-support freenode.<br><br=
>Meanwhile, I&#39;ll prepare a series of open questions and resource pointe=
rs for each topic. Also, coming up with weaponized pinning attacks against =
LN nodes and proposals on how you can improve double-spend protection hopef=
ully with package relay or p2p extensions if we move towards full-rbf.<br><=
br>If any L2 protocol dev/designer have specific transaction relay requirem=
ents for their projects, especially ones far different from Lightning, I&#3=
9;m really interested if you want to share them in the L2-zoology repo (<a =
href=3D"https://github.com/ariard/L2-zoology/tree/master/protocols">https:/=
/github.com/ariard/L2-zoology/tree/master/protocols</a>) or anywhere else. =
I&#39;m doing my best to keep up with most L2 security models, that said th=
e space is growing fast :)<br><br>Cheers,<br>Antoine<br><br>[0] <a href=3D"=
https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-April/003002=
.html">https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-April=
/003002.html</a></div>

--000000000000183a4f05c222ed08--