📅 Original date posted:2018-05-21
📝 Original message:Jim Posen <jim.posen at gmail.com> writes:
> I believe OP_CSV with a relative locktime of 0 could be used to enforce RBF
> on the spending tx?
Marco points out that if the parent is RBF, this child inherits it, so
we're actually good here.
However, Matt Corallo points out that you can block RBF will a
large-but-lowball tx, as BIP 125 points out:
will be replaced by a new transaction...:
3. The replacement transaction pays an absolute fee of at least the sum
paid by the original transactions.
I understand implementing a single mempool requires these kind of
up-front decisions on which tx is "better", but I wonder about the
consequences of dropping this heuristic? Peter?
Thanks!
Rusty.
Rusty Russell [ARCHIVE] /
npub1zw…hkhpx
2023-06-07 18:11:58
in reply to nevent1q…88n5
Author Public Key
npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpxPublished at
2023-06-07 18:11:58Event JSON
{
"id": "33600aa57c9522ceb70bf217f07545f37fa981fa8ae177f42a7491f81fc9ecbe",
"pubkey": "13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425",
"created_at": 1686161518,
"kind": 1,
"tags": [
[
"e",
"caee4e3828cad70a0aa9bfba9569480bc6157a528d4896eeab11f571613a9d97",
"",
"root"
],
[
"e",
"da66d39a9dd8e0890c770ef152c5fa5efb53efd2e4b7a33da5a1e9204b035075",
"",
"reply"
],
[
"p",
"9e2723f47c6c16d3093735bd6acdc8b0dd1b91c78216f7001bdd2f7562b69ed1"
]
],
"content": "📅 Original date posted:2018-05-21\n📝 Original message:Jim Posen \u003cjim.posen at gmail.com\u003e writes:\n\u003e I believe OP_CSV with a relative locktime of 0 could be used to enforce RBF\n\u003e on the spending tx?\n\nMarco points out that if the parent is RBF, this child inherits it, so\nwe're actually good here.\n\nHowever, Matt Corallo points out that you can block RBF will a\nlarge-but-lowball tx, as BIP 125 points out:\n\n will be replaced by a new transaction...:\n\n 3. The replacement transaction pays an absolute fee of at least the sum\n paid by the original transactions.\n\nI understand implementing a single mempool requires these kind of\nup-front decisions on which tx is \"better\", but I wonder about the\nconsequences of dropping this heuristic? Peter?\n\nThanks!\nRusty.",
"sig": "9840a2854f2072f62fadc07573d6c5946cd5570454f231f486f6a183fd50df86f2c5a6df2a5292593f05d108de356850595b89af5f3e7051554301f0cf55d2ab"
}