Date: Sun, 10 Apr 2022 15:32:52 -0400
From: Peter Todd <pete@petertodd.org>
To: Jeremy Rubin <jeremy.l.rubin@gmail.com>
Message-ID: <YlMw5NxXnGV9WrVg@petertodd.org>
References: <CAD5xwhik6jVQpP2_ss7d5o+pPLsqDCHuaXG41AMKHVYhZMXF1w@mail.gmail.com>
 <YgS3sJvg6kG3WnVJ@petertodd.org>
 <CAD5xwhi3Ja8gdU2h_6-1ck4kdU0TiC2Kx5O-61=f9=6JQSMs=A@mail.gmail.com>
 <YhAwr7+9mGJAe2/p@petertodd.org>
 <CAD5xwhi=sKckFZew75tZTogoeFABraWtJ6qMC+RgZjcirxYyZw@mail.gmail.com>
 <YhC6yjoe3bAfBS+W@petertodd.org>
 <CAD5xwhjR06Lp3ka-MqZQE64tfE5uDQB6TrMh06khjYrDzuT95g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="GXfBbLfz3Ln4S9kK"
Content-Disposition: inline
In-Reply-To: <CAD5xwhjR06Lp3ka-MqZQE64tfE5uDQB6TrMh06khjYrDzuT95g@mail.gmail.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
 lightning-dev <lightning-dev@lists.linuxfoundation.org>,
 Jeremy <jlrubin@mit.edu>
Subject: Re: [bitcoin-dev] [Pre-BIP] Fee Accounts
Precedence: list


--GXfBbLfz3Ln4S9kK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Feb 20, 2022 at 08:29:00AM -0800, Jeremy Rubin wrote:
> > On Fri, Feb 18, 2022 at 04:38:27PM -0800, Jeremy Rubin wrote:
> > > > As I said, it's a new kind of pinning attack, distinct from other t=
ypes
> > > of pinning attack.
> > >
> > > I think pinning is "formally defined" as sequences of transactions wh=
ich
> > > prevent or make it less likely for you to make any progress (in terms=
 of
> > > units of computation proceeding).
> >
> > Mentioning "computation" when talking about transactions is misleading:
> > blockchain transactions have nothing to do with computation.
> >
>=20
> It is in fact computation. Branding it as "misleading" is misleading... T=
he
> relevant literature is https://en.wikipedia.org/wiki/Non-blocking_algorit=
hm,
> sponsors helps get rid of deadlocking so that any thread can be guaranteed
> to make progress. E.g., this is critical in Eltoo, which is effectively a
> coordinated multi-party computation on-chain to compute the highest
> sequence number known by any worker.
>=20
> That transactions are blobs of "verification" (which is also itself a
> computation) less so than dynamic computations is irrelevant to the fact
> that series of transactions do represent computations.

It's misleading in the blockchain environment where lots of people have been
trying to portray blockchain schemes as "world computers" and other nonsense
marketing. You would have been better off just saying "make any progress"
without mentioning "computation" at all.

> > > Something that only increases possibility to make progress cannot be
> > > pinning.
> >
> > It is incorrect to say that all use-cases have the property that any
> > version of
> > a transaction being mined is progress.
> >
>=20
> It is progress, tautologically. Progress is formally definable as a
> transaction of any kind getting mined. Pinning prevents progress by an
> adversarial worker. Sponsoring enables progress, but it may not be your
> preferred interleaving. That's OK, but it's inaccurate to say it is not
> progress.

Let's try to use terminology with straight-forward meanings. I've yet to see
any other protocol where "progess" can also mean useless work being done.

> I didn't claim there to be a chain of unconfirmed, I claimed that there
> could be single output chain that you're RBF'ing one step per block.
>=20
> E.g., it could be something like
>=20
> A_0 -> {A_1 w/ CSV 1 block, OP_RETURN {blah, foo}}
> A_1 -> {A_2 w/ CSV 1 block, OP_RETURN {bar}}
>=20
> such that A_i provably can't have an unconfirmed descendant. The notion
> would be that you're replacing one with another. E.g., if you're updating
> the calendar like:
>=20
>=20
> Version 0: A_0 -> {A_1 w/ CSV 1 block, OP_RETURN {blah, foo}}
> Version 1: A_0 -> {A_1 w/ CSV 1 block, OP_RETURN {blah, foo, bar}}
> Version 2: A_0 -> {A_1 w/ CSV 1 block, OP_RETURN {blah, foo, bar, delta}}
>=20
> and version 1 gets mined, then in A_1's spend you simply shift delta to
> that (next) calendar.
>=20
> A_1 -> {A_2 w/ CSV 1 block, OP_RETURN {delta}}
>=20
> Thus my claim that someone sponsoring a old version only can delay by 1
> block the calendar commit.

You seem to still be confused about OpenTimestamps. There is no output chai=
n at
all; OTS has no reason to use CheckSequenceVerify and does not. OTS
transactions are, from the point of view of the timestamp proofs, entirely
independent of one another.

Remember that OTS simply proves data in the past. Nothing more.

> > > Lastly, if you do get "necromanced" on an earlier RBF'd transaction b=
y a
> > > third party for OTS, you should be relatively happy because it cost y=
ou
> > > less fees overall, since the undoing of your later RBF surely returned
> > some
> > > satoshis to your wallet.
> >
> > As I said above, no it doesn't.
> >
> >
> It does save money since you had to pay to RBF, the N+1st txn will be
> paying higher fee than the Nth. So if someone else sponsors an earlier
> version, then you save whatever feerate/fee bumps you would have paid and
> the funds are again in your change output (or something). You can apply
> those change output savings to your next batch, which can include any
> entries that have been dropped .

Again, that is not true. Because OTS doesn't have a chain of transactions, =
I'd
rather do one transaction with all pending commitments at a particular time
rather than waste money on mining two transactions for a given set of
commitments that need timestamping.

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org

--GXfBbLfz3Ln4S9kK
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmJTMOEACgkQLly11TVR
LzfyWhAAgVKu/QZBwvBC0UNetiKdjEkfYFxz4cEgqYaOcS88Av3nglKRY6zXG9eb
QhBlPSCGtrvOGTI5MDSjAbQZ1jPZv8kWWck5DmZafRGFpTQ5UT4onwaGyq4bkxzK
N/DSn6v6pyo79DnL5CgF8oUywqFESIosfm3ZYgNGU5hv0W+yk9Fa5k9jo/C23H3U
/8x/hUxWtqTJv8lFYIYlB/OW1VrgPq60zD9kSTSnrrgugUXj2wZT5druScRWL9mY
nFmPuDM5ruxrVM1mc2/pNI20xe677fazJ4sn9uElxb6C0DKYLCKXV5bK1zGf07rW
ohnBx4ZRikyqUe9XIG5pzz3OlT/WYYJN2Q7KBopHT8+6NTlowWcV1FtNbvSc8TDl
KrnXo0ugLzrB+7Fk75mm4CE1pIdI16T34gJ2TVxUlZHGkZP8+Uos2LfjhBwyczjB
0N029CPpYRoSYQ8jKeZruEXyaGeeAilvwYoKIG0rV7ul3awlvsv11mSIQ0cBHyv8
ETMFET9RWCseQ9pI1I2kkGi98+G0XHYFHoib13gocnqzz9U5OVGiW0r+HGYr9sqN
vALh4g0bRA1lJqP2LcJ7uIxwp/pVJsjGIWry4O/rY3cJopHj6vvAMYaZ3Zl6kUz4
VxMNEqynRgYZxCvmsY28Vcb2T02ZpyqZA6KQKAXhRkg0xMYA6R0=
=nhF5
-----END PGP SIGNATURE-----

--GXfBbLfz3Ln4S9kK--