From: Antoine Riard <antoine.riard@gmail•com>
To: Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
"lightning-dev\\\\@lists.linuxfoundation.org"
<lightning-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Reminder: Transaction relay workshop on IRC Libera - Tuesday 15th June 19:00 UTC
Date: Mon, 14 Jun 2021 10:41:21 -0400 [thread overview]
Message-ID: <CALZpt+HvoEC8Tf1uOJ6-XMAbt7dVbxfgmmNp_8wjKVACbvSpEw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
Hi,
A short reminder about the 1st transaction relay workshop happening
tomorrow on #l2-onchain-support Libera chat (!), Tuesday 15th June, from
19:00 UTC to 20:30 UTC
Scheduled topics are:
* "Guidelines about L2 protocols onchain security design"
* "Coordinated cross-layers security disclosures"
* "Full-RBF proposal"
Find notes and open questions for the two first topics here:
* https://github.com/ariard/L2-zoology/blob/master/workshops/guidelines.md
* https://github.com/ariard/L2-zoology/blob/master/workshops/coordinated.md
Going to send the "Move toward full-rbf" proposal soon, deserves its own
thread. Workshops will stick to a socratic format to foster as much
knowledge sharing among attendees and ideally we'll reach rough consensus
about expected goals.
If you're a second-layer protocol designer, a Lightning dev, a Bitcoin Core
dev contributing around mempool/p2p areas, or a Bitcoin service operator
with intense usage of the mempool, I hope you'll find those workshops of
interest and you'll learn a lot :)
Again it's happening on Libera, not Freenode, contrary to the former mail
about agenda & schedule.
Cheers,
Antoine
[-- Attachment #2: Type: text/html, Size: 1473 bytes --]
reply other threads:[~2021-06-14 14:41 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+HvoEC8Tf1uOJ6-XMAbt7dVbxfgmmNp_8wjKVACbvSpEw@mail.gmail.com \
--to=antoine.riard@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=lightning-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