📅 Original date posted:2014-08-01
📝 Original message:On 7/31/2014 5:58 PM, Kaz Wesley wrote:
> 1. start setting nLockTime to the current height by default in newly
> created transactions (or slightly below the current height, for
> reorg-friendliness)
Reorg-frendliness is the opposite of the rationale behind #2340, which
proposes setting nLockTime at current-height + 1 to prevent
"fee-sniping" reorgs...
> 2. once users have had some time to upgrade to clients that set
> nLockTime, start discouraging transactions without nLockTime --
> possibly with a slightly higher fee required for relay
> 3. start rate-limiting relay of transactions without an nLockTime
> (maybe this alone could be used to achieve [2])
> 4. add a new IsStandard rule rejecting transactions with an nLockTime
> more than N blocks behind the current tip (for some fixed value N, to
> be determined)
>
One way to proceed is implement #3753 (mempool janitor) in such a way
that transactions with nLockTime are allowed to live a bit longer in the
mempool (say 500 blocks) than those without (72 hours). In other words,
as a first step, just actually start expiring things from the mempool in
bitcoin core, and leave any relay fee adjustments or rate limiting for
later. The isStandard change would be a good complement to #3753, to
avoid relaying a tx that will soon expire by the nLockTime rule anyway.
Tom Harding [ARCHIVE] /
npub1ms…pmwjy
2023-06-07 15:24:40
in reply to nevent1q…fxxh
Author Public Key
npub1msef5qkfwz4t7qacwxz775wgdtlytph78g2g2z903x90874u263sypmwjyPublished at
2023-06-07 15:24:40Event JSON
{
"id": "c6e3ed847e785b428ea77e84ff865549b1894925d83cff57f46937776b902f83",
"pubkey": "dc329a02c970aabf03b87185ef51c86afe4586fe3a148508af898af3fabc56a3",
"created_at": 1686151480,
"kind": 1,
"tags": [
[
"e",
"862ea3dc96b72bff70fc377e79d0d6efd56d14bf0babb9aa995ab55fc1b92d18",
"",
"root"
],
[
"e",
"61c7de1bd1c14dd0d05c097c51892dd7ae5d398416523053b9d6b2487df66623",
"",
"reply"
],
[
"p",
"83939e4391e74ab1f02f783131a30a24db681188b72b90da8bce3dcaa763c8b4"
]
],
"content": "📅 Original date posted:2014-08-01\n📝 Original message:On 7/31/2014 5:58 PM, Kaz Wesley wrote:\n\u003e 1. start setting nLockTime to the current height by default in newly\n\u003e created transactions (or slightly below the current height, for\n\u003e reorg-friendliness)\n\nReorg-frendliness is the opposite of the rationale behind #2340, which \nproposes setting nLockTime at current-height + 1 to prevent \n\"fee-sniping\" reorgs...\n\n\n\u003e 2. once users have had some time to upgrade to clients that set\n\u003e nLockTime, start discouraging transactions without nLockTime --\n\u003e possibly with a slightly higher fee required for relay\n\u003e 3. start rate-limiting relay of transactions without an nLockTime\n\u003e (maybe this alone could be used to achieve [2])\n\u003e 4. add a new IsStandard rule rejecting transactions with an nLockTime\n\u003e more than N blocks behind the current tip (for some fixed value N, to\n\u003e be determined)\n\u003e\n\nOne way to proceed is implement #3753 (mempool janitor) in such a way \nthat transactions with nLockTime are allowed to live a bit longer in the \nmempool (say 500 blocks) than those without (72 hours). In other words, \nas a first step, just actually start expiring things from the mempool in \nbitcoin core, and leave any relay fee adjustments or rate limiting for \nlater. The isStandard change would be a good complement to #3753, to \navoid relaying a tx that will soon expire by the nLockTime rule anyway.",
"sig": "b9295bfc150b7538b0b84b8eac9d70ef7be6af4cb333d9a7cbcfa1f6c3cba28812a923efb9060f56c8d745d0c0b9ba9ec84692dfce7a2e7dead6f45969dcf3df"
}