📅 Original date posted:2018-11-22
📝 Original message:
Matt Corallo <lf-lists at mattcorallo.com> writes:
> Ah, oops, indeed, that is much cleaner :). Still need a CSV of 1, though :(.
OK, let's walk through this:
Locally offered HTLC:
- Local HTLC-Timeout tx is CLTV delayed, but remote can fulfill without delay.
Remote offered HTLC:
- Local HTLC-Success tx can be done without delay, but remote timeout is CLTV.
IOW:
- HTLC output scripts get a `1 OP_CSV OP_DROP` in the non-revoked branch:
OP_DUP OP_HASH160 <RIPEMD160(SHA256(revocationpubkey))> OP_EQUAL
OP_IF
OP_CHECKSIG
OP_ELSE
+ 1 OP_CHECKSEQUENCEVERIFY OP_DROP
...
- HTLC-Success tx needs nSequence = 1.
- Similarly any self-generated fulfullment tx needs nSequence = 1.
Yech.
I still want a new RBF rule where if you pay twice the current package
*feerate* your tx is accepted, overriding RBF rules 3, 4 & 5. Probably
need to increase the effective minrelay feerate for any txs adding to
that package, similarly (using that double-previous-package-feerate).
That would mean we're back to a single P2WSH(OP_TRUE) with less
blockchain spam, and life is simple. But I'll debate this on
bitcoin-dev :)
Cheers,
Rusty.
Rusty Russell [ARCHIVE] /
npub1zw…hkhpx
2023-06-09 12:53:02
in reply to nevent1q…g3sp
Author Public Key
npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpxPublished at
2023-06-09 12:53:02Event JSON
{
"id": "9e099d51cfc8792885d2b3c87cd418e6bf41f3b4148be778f435b5cc89331aa5",
"pubkey": "13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425",
"created_at": 1686315182,
"kind": 1,
"tags": [
[
"e",
"61bdb1113c2be407a2b6f72754d78bf88b3bb4d02794bc6282368d740c0e6130",
"",
"root"
],
[
"e",
"dfdf90ed5f6d95cf9e5e40dea69f5a9faaf9f88c4ec435953e362149a0d37e53",
"",
"reply"
],
[
"p",
"cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba"
]
],
"content": "📅 Original date posted:2018-11-22\n📝 Original message:\nMatt Corallo \u003clf-lists at mattcorallo.com\u003e writes:\n\u003e Ah, oops, indeed, that is much cleaner :). Still need a CSV of 1, though :(.\n\nOK, let's walk through this:\n\nLocally offered HTLC:\n- Local HTLC-Timeout tx is CLTV delayed, but remote can fulfill without delay.\nRemote offered HTLC:\n- Local HTLC-Success tx can be done without delay, but remote timeout is CLTV.\n\nIOW:\n- HTLC output scripts get a `1 OP_CSV OP_DROP` in the non-revoked branch:\n\n OP_DUP OP_HASH160 \u003cRIPEMD160(SHA256(revocationpubkey))\u003e OP_EQUAL\n OP_IF\n OP_CHECKSIG\n OP_ELSE\n + 1 OP_CHECKSEQUENCEVERIFY OP_DROP\n ...\n- HTLC-Success tx needs nSequence = 1.\n- Similarly any self-generated fulfullment tx needs nSequence = 1.\n\nYech.\n\nI still want a new RBF rule where if you pay twice the current package\n*feerate* your tx is accepted, overriding RBF rules 3, 4 \u0026 5. Probably\nneed to increase the effective minrelay feerate for any txs adding to\nthat package, similarly (using that double-previous-package-feerate).\n\nThat would mean we're back to a single P2WSH(OP_TRUE) with less\nblockchain spam, and life is simple. But I'll debate this on\nbitcoin-dev :)\n\nCheers,\nRusty.",
"sig": "a820f23b4037a168af5723ce968846926888d3aa73dd65948ecff80fcd5354a7b5c9bebcfe28a19c6ef60cb1b4ff1d53b2faa1c23749f51a6ad6df0e7197be5d"
}