From: Antoine Riard <antoine.riard@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] L2s Onchain Support IRC Workshop : Agenda & Schedule
Date: Wed, 12 May 2021 10:35:34 -0400 [thread overview]
Message-ID: <CALZpt+HFDq6MtqgO5qVeWXEmruMHTf_Dk9q6OKjsnC=xjJMgwA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1697 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 2039 bytes --]
reply other threads:[~2021-05-12 14:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALZpt+HFDq6MtqgO5qVeWXEmruMHTf_Dk9q6OKjsnC=xjJMgwA@mail.gmail.com' \
--to=antoine.riard@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox