📅 Original date posted:2015-07-22
📝 Original message:>
> Until we’re able to merge blockchain forks like we’re able to merge git
> repo forks, the safest option is no fork.
>
Block chain forks merge in the same way as git forks all the time, that's
how the reorg algorithm works. Transactions that didn't make it into the
post-reorg chain go back into the mempool and miners attempt to reinclude
them: this is the "merge" process. If they now conflict with other
transactions they are dropped and this is "resolving merge conflicts".
However you have to want to merge with the new chain. If your software is
programmed not to do that out of some bizarre belief that throttling your
own user base is a good idea, then of course, no merge happens. Once you
stop telling your computer to do that, you can then merge (reorg) back onto
the main chain again.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150723/88e446a6/attachment.html>;
Mike Hearn [ARCHIVE] /
npub17t…4qgyd
2023-06-07 15:43:04
in reply to nevent1q…uu5u
Author Public Key
npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydPublished at
2023-06-07 15:43:04Event JSON
{
"id": "caf2712d853c589d27b7a1a4d08dd042b6b9c96633bfe1db771e34080883ad6a",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686152584,
"kind": 1,
"tags": [
[
"e",
"95a36d78d6bf18f4b8ede735f044f5cc9630ae9f0b1198d008835777ff84eede",
"",
"root"
],
[
"e",
"7ee2f7ce4aa17759aa644024bd2e3700f76214fa865a66dc901a3076e8309d7a",
"",
"reply"
],
[
"p",
"e899768d254f3537af7e26455968583632d0ab0bd4c780445eacfa087ac80d8f"
]
],
"content": "📅 Original date posted:2015-07-22\n📝 Original message:\u003e\n\u003e Until we’re able to merge blockchain forks like we’re able to merge git\n\u003e repo forks, the safest option is no fork.\n\u003e\n\nBlock chain forks merge in the same way as git forks all the time, that's\nhow the reorg algorithm works. Transactions that didn't make it into the\npost-reorg chain go back into the mempool and miners attempt to reinclude\nthem: this is the \"merge\" process. If they now conflict with other\ntransactions they are dropped and this is \"resolving merge conflicts\".\n\nHowever you have to want to merge with the new chain. If your software is\nprogrammed not to do that out of some bizarre belief that throttling your\nown user base is a good idea, then of course, no merge happens. Once you\nstop telling your computer to do that, you can then merge (reorg) back onto\nthe main chain again.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150723/88e446a6/attachment.html\u003e",
"sig": "ab71c79e6bd05969573887cc7b27b051e6c266a830887dceb31bc950c69dc62cd72952e075855e4e369bb067a544359977e55ef27d54fef10e10b4b8f64583af"
}