From: Peter Todd <pete@petertodd•org>
To: "David A. Harding" <dave@dtrt•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: Wed, 27 Mar 2024 12:20:54 +0000 [thread overview]
Message-ID: <ZgQPJgXXFOuxVTkV@petertodd.org> (raw)
In-Reply-To: <dd99ffec956a6fe6b75e363108099e68@dtrt.org>
[-- Attachment #1: Type: text/plain, Size: 1868 bytes --]
On Sun, Mar 24, 2024 at 03:36:30PM -1000, David A. Harding wrote:
> 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?
That at least is mitigated a bit by the fact that the earlier versions existed
and were valid; it's still a potentially useful reduction in trust as the
service needs to be able to do something economically useful with the high-fee
transaction for it to be a profitable attack.
As I said, I'm suggesting a way to reduce trust. Not eliminate it.
> 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?
That might actually be a weaker attack than the first: you can watch a mempool,
unknown to the service, to see if you recieve the transaction you paid for. If
you don't, there's a reasonable chance they're trying to rip you off.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
--
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/ZgQPJgXXFOuxVTkV%40petertodd.org.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-03-27 12:23 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
2024-03-27 12:20 ` Peter Todd [this message]
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=ZgQPJgXXFOuxVTkV@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoindev@googlegroups.com \
--cc=dave@dtrt$(echo .)org \
--cc=martin.habovstiak@gmail$(echo .)com \
/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