Jim Posen [ARCHIVE] on Nostr: 📅 Original date posted:2018-05-17 📝 Original message:> > This brings us another ...
📅 Original date posted:2018-05-17
📝 Original message:>
> This brings us another theoretical problem: someone could spend our
> OP_TRUE with a low-fee non-RBF tx, and we'd not be able to use it to
> CPFP the tx. It'd be hard to do, but possible. I think the network
> benefits from using OP_TRUE (anyone can clean, and size, vs some
> only-known-to-me pubkey) outweighs the risk, but it'd be nice if OP_TRUE
> P2WSH spends were always considered RBF.
>
I believe OP_CSV with a relative locktime of 0 could be used to enforce RBF
on the spending tx?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180517/da8223c0/attachment-0001.html>;
📝 Original message:>
> This brings us another theoretical problem: someone could spend our
> OP_TRUE with a low-fee non-RBF tx, and we'd not be able to use it to
> CPFP the tx. It'd be hard to do, but possible. I think the network
> benefits from using OP_TRUE (anyone can clean, and size, vs some
> only-known-to-me pubkey) outweighs the risk, but it'd be nice if OP_TRUE
> P2WSH spends were always considered RBF.
>
I believe OP_CSV with a relative locktime of 0 could be used to enforce RBF
on the spending tx?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180517/da8223c0/attachment-0001.html>;