From: "David A. Harding" <dave@dtrt•org>
To: Peter Todd <pete@petertodd•org>
Cc: "Martin Habovštiak" <martin.habovstiak@gmail•com>,
bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Anyone can boost - a more efficient alternative to anchor outputs
Date: Sun, 24 Mar 2024 15:36:30 -1000 [thread overview]
Message-ID: <dd99ffec956a6fe6b75e363108099e68@dtrt.org> (raw)
In-Reply-To: <ZfmgLhETBEDql85w@petertodd.org>
On 2024-03-19 04:24, Peter Todd wrote:
> To reduce trust you could do an automated, multiple round, signing
> scheme where
> the service signs transations with higher and higher fee-rates in
> exchange for
> most funds over LN.
When the service thinks the user has paid all that they're going to pay,
what stops them from replacing their transaction one more time with a
version that does not sponsor the user's transaction? Also, what stops
the service from selling the same space in a sponsor transaction to
multiple users at once, e.g. customers Alice and Bob each iterate with
the service many times until they get a sponsor with as much fee as they
want, but when they go to broadcast, they discover that their
transactions conflict, so one of them paid for nothing?
I had thought about using a simple pay-for-signature scheme using
signature adaptors and a hoped-for LN that supports PTLCs, but I think
it suffers from the same problems. I haven't been able to think of a
way to significantly reduce trust for outsourced sponsorship without
also significantly reducing the efficiency of sponsor transactions.
-Dave
P.S. related discussion about efficient sponsors may be found in this
thread:
https://delvingbitcoin.org/t/improving-transaction-sponsor-blockspace-efficiency/696
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/dd99ffec956a6fe6b75e363108099e68%40dtrt.org.
next prev parent reply other threads:[~2024-03-25 1:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 9:47 Martin Habovštiak
2024-03-19 14:10 ` 'Fabian' via Bitcoin Development Mailing List
2024-03-19 14:24 ` Peter Todd
2024-03-25 1:36 ` David A. Harding [this message]
2024-03-27 12:20 ` Peter Todd
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=dd99ffec956a6fe6b75e363108099e68@dtrt.org \
--to=dave@dtrt$(echo .)org \
--cc=bitcoindev@googlegroups.com \
--cc=martin.habovstiak@gmail$(echo .)com \
--cc=pete@petertodd$(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