From: Nagaev Boris <bnagaev@gmail•com>
To: "David A. Harding" <dave@dtrt•org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Scaling Lightning Safely With Feerate-Dependent Timelocks
Date: Fri, 29 Dec 2023 22:17:01 -0300 [thread overview]
Message-ID: <CAFC_Vt6yk2MwkUhiBKyGmOArVrU9VCdf27qR8wDMMOz_ONjt=A@mail.gmail.com> (raw)
In-Reply-To: <786297315b27fdecc1a21cc40ef4b993@dtrt.org>
Hey David!
On Fri, Dec 29, 2023 at 9:37 PM David A. Harding via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> We can't prevent people from paying out of band, but we can ensure that
> the easiest and most effective way to pay for a transaction is through
> in-band fees and transactions that are relayed to every miner who is
> interested in them. If we fail at that, I think Bitcoin losing its
> censorship resistance will be inevitable. LN, coinpools, and channel
> factories all strongly depend on Bitcoin transactions not being
> censored, so I don't think any security is lost by redesigning them to
> additionally depend on reasonably accurate in-band fee statistics.
Feerate-Dependent Timelocks do create incentives to accept out-of-band
fees to decrease in-band fees and speed up mining of transactions
using FDT! Miners can make a 5% discount on fees paid out-of-band and
many people will use it. Observed fees decrease and FDT transactions
mature faster. It is beneficial for both parties involved: senders of
transactions save 5% on fees, miners get FDT transactions mined faster
and get more profits (for the sake of example more than 5%).
--
Best regards,
Boris Nagaev
next prev parent reply other threads:[~2023-12-30 1:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 17:07 jlspc
2023-12-17 23:01 ` Antoine Riard
2023-12-22 1:25 ` jlspc
2023-12-23 4:09 ` Eric Voskuil
2023-12-28 18:19 ` jlspc
2023-12-28 18:42 ` Eric Voskuil
2023-12-30 0:37 ` David A. Harding
2023-12-30 1:17 ` Nagaev Boris [this message]
2023-12-30 3:11 ` David A. Harding
2023-12-30 3:20 ` Nagaev Boris
2023-12-22 16:36 ` Nagaev Boris
2023-12-28 18:06 ` jlspc
2023-12-29 18:11 ` David A. Harding
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='CAFC_Vt6yk2MwkUhiBKyGmOArVrU9VCdf27qR8wDMMOz_ONjt=A@mail.gmail.com' \
--to=bnagaev@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dave@dtrt$(echo .)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