From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 6C0DBC0001 for ; 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 ; 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 ; 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 ; Wed, 12 May 2021 14:35:48 +0000 (UTC) Received: by mail-wm1-x32e.google.com with SMTP id l18-20020a1ced120000b029014c1adff1edso782060wmh.4 for ; 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 Date: Wed, 12 May 2021 10:35:34 -0400 Message-ID: To: Bitcoin Protocol Discussion 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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
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 a= merican crowd will travel around and won't be necessary on their keyboa= rds. Also, if folks from Asia/Pacific timezones want to join or participate= , I'm all good to set up additional, more-friendly sessions.

* 1= st meeting: Tuesday 15th June 19:00 - 20:30 =C2=A0UTC

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

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

To= pics will be "Package relay design and/or generic L2 fee-bumping primi= tive".

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.

D= iscussions will happen on the new chan #l2-onchain-support freenode.
Meanwhile, I'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>If any L2 protocol dev/designer have specific transaction relay requirem= ents for their projects, especially ones far different from Lightning, I= 9;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 th= e space is growing fast :)

Cheers,
Antoine

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