📅 Original date posted:2016-04-24
📝 Original message:
Hello,
I am trying to understand how we should handle concurrent signatures,
and I am wondering if we couldn't use an ordering of some sort to
resolve conflicts when they occur, for example by simply comparing
signatures. If two nodes send each other a signature at the same time,
they could agree that the one that sent the "greatest" signature has
to immediately resend a new signature including all pending changes.
This new signature would encompass all the changes both parties wanted
in the first place so everybody would be happy.
For example if "SIG B0 > SIG A0":
NODE A NODE B
Committed: [] Committed: []
Staged: [X] Staged: [Y]
ADD HTLC X ---- ---- ADD HTLC Y
\ /
\ /
Committed: [X] \ / Committed: [Y]
Staged: [] \/ Staged: []
SIG A0 --- /\ --- SIG B0
\ / \ /
\/ \/
/\ /\
<--- \ / --->
Committed: [X] \/ Committed: [Y]
Staged: [Y] /\ Staged: [X]
/ \
/ \
DISCARD SIG A0 <---- -----> DISCARD SIG B0
Committed: [] Committed: []
Staged: [X Y] Staged: [X Y]
Committed: [X Y]
Staged: []
<---------------- SIG B1
Committed: [X Y]
Staged: []
REVOCATION ---------------->
SIG A1 ---------------->
<---------------- REVOCATION
Cheers,
Pierre
Pierre [ARCHIVE] /
npub1yz…y4pdt
2023-06-09 14:46:10
in reply to nevent1q…fzkr
Author Public Key
npub1yz88535e0ydqye9q9x8l5cz9d3g6ervfjgyk5xm88zvktmxvstlsuy4pdtPublished at
2023-06-09 14:46:10Event JSON
{
"id": "4a428fbd8726a0cd0e8ef836cc58003994aaf4b97cb8c249ceccc7a599215643",
"pubkey": "208e7a4699791a0264a0298ffa60456c51ac8d8992096a1b67389965eccc82ff",
"created_at": 1686314770,
"kind": 1,
"tags": [
[
"e",
"4ff2a65c3c268f45d30c60238ba4894eba060af5aaab565a2e83bb1b4c64229c",
"",
"reply"
],
[
"p",
"9456f7acb763eaab2e02bd8e60cf17df74f352c2ae579dce1f1dd25c95dd611c"
]
],
"content": "📅 Original date posted:2016-04-24\n📝 Original message:\nHello,\n\nI am trying to understand how we should handle concurrent signatures,\nand I am wondering if we couldn't use an ordering of some sort to\nresolve conflicts when they occur, for example by simply comparing\nsignatures. If two nodes send each other a signature at the same time,\nthey could agree that the one that sent the \"greatest\" signature has\nto immediately resend a new signature including all pending changes.\nThis new signature would encompass all the changes both parties wanted\nin the first place so everybody would be happy.\n\nFor example if \"SIG B0 \u003e SIG A0\":\n\n NODE A NODE B\n\n Committed: [] Committed: []\n Staged: [X] Staged: [Y]\n ADD HTLC X ---- ---- ADD HTLC Y\n \\ /\n \\ /\n Committed: [X] \\ / Committed: [Y]\n Staged: [] \\/ Staged: []\n SIG A0 --- /\\ --- SIG B0\n \\ / \\ /\n \\/ \\/\n /\\ /\\\n \u003c--- \\ / ---\u003e\n Committed: [X] \\/ Committed: [Y]\n Staged: [Y] /\\ Staged: [X]\n / \\\n / \\\n DISCARD SIG A0 \u003c---- -----\u003e DISCARD SIG B0\n Committed: [] Committed: []\n Staged: [X Y] Staged: [X Y]\n\n Committed: [X Y]\n Staged: []\n \u003c---------------- SIG B1\n Committed: [X Y]\n Staged: []\n\n REVOCATION ----------------\u003e\n\n SIG A1 ----------------\u003e\n\n \u003c---------------- REVOCATION\n\nCheers,\nPierre",
"sig": "571993779318952057466144a8105b427e25f0db9f7c0d2a1f36d6c4339c0daea1e1b5e664b5b1aab535768b93de2d76938f87731730a4322e7a5870a037829e"
}