From: Jeremy <jlrubin@mit•edu>
To: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] [Bitcoin Advent Calendar]: Congestion Control
Date: Thu, 9 Dec 2021 10:24:44 -0800 [thread overview]
Message-ID: <CAD5xwhh7azm8jydaTwwyXT1w_VwgLyXf_KAgyBM2P8XHkUqfLg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
Today's post is a follow up to some older content about congestion control
& CTV.
It's written (as with the rest of the series) to be a bit more approachable
than technical, but there are code samples in Sapio of constructing a
payout tree.
today's post:
https://rubin.io/bitcoin/2021/12/09/advent-12/
older posts:
- https://utxos.org/analysis/bip_simulation/
- https://utxos.org/analysis/batching_sim/
Generally, I think the importance and potential of congestion control is
currently understated. The next couple posts will build on this with Coin
Pools, Mining Pools, and Lighting which also leverage congestion control
structures with multi-party opt-outs for added punch. But even in the base
case, these congestion control primitives can be really important for large
volume large value businesses to close out liabilities reliably without
being impacted too much by transient chain weather. Those types of demand
(high volume, high value) aren't served well by the lightning network
(ever) since the large values of flows would be difficult to route and
might prefer being deposited directly into cold storage given the amounts
at stake.
best,
Jeremy
--
@JeremyRubin <https://twitter.com/JeremyRubin>
<https://twitter.com/JeremyRubin>
[-- Attachment #2: Type: text/html, Size: 3422 bytes --]
reply other threads:[~2021-12-09 18:25 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=CAD5xwhh7azm8jydaTwwyXT1w_VwgLyXf_KAgyBM2P8XHkUqfLg@mail.gmail.com \
--to=jlrubin@mit$(echo .)edu \
--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