📅 Original date posted:2017-02-07
📝 Original message:
On Tue, Feb 7, 2017 at 2:39 AM, Nicolas Dorier <nicolas.dorier at gmail.com>
wrote:
> Good point, actually, a simpler way to do it, is for TX2 to be nTimelocked
> after bounty's expiration.
>
That works too and keeps the transaction smaller.
I think a symmetrically funded channel needs 4 1BTC outputs, so it is
pretty much two single funded channels. It would be slightly smaller than
2 transactions to open the channel.
TX1
Input
2 from Alice
2 from Bob
Output
1: (Alice + Bob) OR (Bob + AliceSecret)
1: (Alice + Bob) OR (Alice + BobSecret)
1: (Bob + timeout(now + T)) OR (Alice + AliceSecret)
1: (Alice + timeout(now + T)) OR (Bob + BobSecret)
TX2
locktime: now + 2T
Input
TX1/0: signed by (Alice + Bob)
TX1/1: signed by (Alice + Bob)
Output
Initial channel paying Alice & Bob 1BTC each
---------------------------------------
Alice and Bob create TX1, sign it and share the result.
Alice and Bob create TX2, sign it and share the result.
Abort for those 2 steps:
* If one signs and the other doesn't then the signer should spend their
inputs to be safe.
* If TX1 is broadcast, then they can both spend their timeouts to recover
their funds, so it is safe.
Once they both have signed versions of TX1 and TX2, they should broadcast
TX1. This initializes the channel.
If TX1 is mutated, then they should both abort and spend their timeouts and
recover their funds.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20170207/7d562bed/attachment.html>;
Tier Nolan [ARCHIVE] /
npub1g6…sl5wd
2023-06-09 12:47:01
in reply to nevent1q…aevl
Author Public Key
npub1g6vxlp4e0nyhs2dqxxcryztyf5f5hyuaq93nw4r87zcnv0sdsa0qqsl5wdPublished at
2023-06-09 12:47:01Event JSON
{
"id": "b22127b7d7eff783a7ef63e34c269b54a5015409b877b910c37076a1f0b0bc2f",
"pubkey": "46986f86b97cc97829a031b03209644d134b939d0163375467f0b1363e0d875e",
"created_at": 1686314821,
"kind": 1,
"tags": [
[
"e",
"9ea054313bf60f8de6d3bffeb1c78d06c11e96e42cc896b7e3b1ee263032c084",
"",
"root"
],
[
"e",
"8c4047d61280d657b92b5e1e4a3db7e3743540b4a9e142b03c362aea4965a3e3",
"",
"reply"
],
[
"p",
"bf0548dc0ad239e9e1e0bba3c969632ded402a68091cde1b21a0895e90bc9a57"
]
],
"content": "📅 Original date posted:2017-02-07\n📝 Original message:\nOn Tue, Feb 7, 2017 at 2:39 AM, Nicolas Dorier \u003cnicolas.dorier at gmail.com\u003e\nwrote:\n\n\u003e Good point, actually, a simpler way to do it, is for TX2 to be nTimelocked\n\u003e after bounty's expiration.\n\u003e\n\nThat works too and keeps the transaction smaller.\n\nI think a symmetrically funded channel needs 4 1BTC outputs, so it is\npretty much two single funded channels. It would be slightly smaller than\n2 transactions to open the channel.\n\nTX1\n\nInput\n2 from Alice\n2 from Bob\n\nOutput\n1: (Alice + Bob) OR (Bob + AliceSecret)\n1: (Alice + Bob) OR (Alice + BobSecret)\n1: (Bob + timeout(now + T)) OR (Alice + AliceSecret)\n1: (Alice + timeout(now + T)) OR (Bob + BobSecret)\n\nTX2\nlocktime: now + 2T\n\nInput\nTX1/0: signed by (Alice + Bob)\nTX1/1: signed by (Alice + Bob)\nOutput\nInitial channel paying Alice \u0026 Bob 1BTC each\n\n---------------------------------------\n\nAlice and Bob create TX1, sign it and share the result.\n\nAlice and Bob create TX2, sign it and share the result.\n\nAbort for those 2 steps:\n* If one signs and the other doesn't then the signer should spend their\ninputs to be safe.\n* If TX1 is broadcast, then they can both spend their timeouts to recover\ntheir funds, so it is safe.\n\nOnce they both have signed versions of TX1 and TX2, they should broadcast\nTX1. This initializes the channel.\n\nIf TX1 is mutated, then they should both abort and spend their timeouts and\nrecover their funds.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20170207/7d562bed/attachment.html\u003e",
"sig": "f7b2b0638a9606e00d22aefa784161a1a7cd347b55bac4bd996d0eced4accd8afeffd11f2eb48ce6f7f74831bbcb4a632b1f7a390bd672049487cb38d09f508b"
}