The second one is indeed safer. But I don't think they'll ev...

SatsAndSports

npub1zthq85gksjsjthv8h6rec2qeqs2mu0emrm9xknkhgw7hfl7csrnq6wxm56

hex

b816621b5bf2748b59ac0eda097a6bed4cfb53ae28f2f749667e05ad14f41aef

nevent

nevent1qqsts9nzrddlyayttxkqaksf0f476n8m2whz3uhhf9n8upddzn6p4mcprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsp9msr6ytgfgf9mkrmapuu9qvsg9d78ua3ajntfmt580t5llvgpesgvld34

Kind-1 (TextNote)

2026-07-29T15:24:01Z

↳ Reply to Event not found

b226b737c20ff1ccb8f3a55a38c3d825cddacff834a32a579974c38308d1c3e7...

The second one is indeed safer. But I don't think they'll ever get 4032 blocks; I'm not even sure they'll get 4 mandatory signalling blocks

So I think if you want to guarantee that splitting is possible, then - like you said - you need something like this:

  1. make a splitting transaction, with a large op_return, and broadcast it at or after the start of mandatory signalling (August 8th/9th), and broadcast it on the "legacy" network
  2. If that confirms on both chains, then the "split" has failed, and a BIP110 miner broke the default policy. You haven't lost funds, you just need to start again from the new address.
  3. When it confirms on the legacy chain, then you should quickly RBF to spend the funds back to yourself
  4. Now you have successfully spilt (unless you're unlucky and reorgs happen!)

.. come to think of it, that's just too messy, I think

Raw JSON

{
  "kind": 1,
  "id": "b816621b5bf2748b59ac0eda097a6bed4cfb53ae28f2f749667e05ad14f41aef",
  "pubkey": "12ee03d11684a125dd87be879c28190415be3f3b1eca6b4ed743bd74ffd880e6",
  "created_at": 1785338641,
  "tags": [
    [
      "alt",
      "A short note: The second one is indeed safer. But I don't think ..."
    ],
    [
      "e",
      "7bbd9b4f0786785ca22ad6ce02757125e6c9d0485080245695042a26063e50a7",
      "wss://nos.lol/",
      "root",
      "e3fc673fc5f99cc554d0ff47756795647d25cb6e6658f912d114ae6429d35d35"
    ],
    [
      "e",
      "c97ef7576d58d4e61089f1109c5a8d72bcfff5bf64f70e4ffde911f97c9176d3",
      "wss://nostr.chaima.info/",
      "",
      "12ee03d11684a125dd87be879c28190415be3f3b1eca6b4ed743bd74ffd880e6"
    ],
    [
      "e",
      "b226b737c20ff1ccb8f3a55a38c3d825cddacff834a32a579974c38308d1c3e7",
      "wss://relay.snort.social/",
      "reply",
      "e3fc673fc5f99cc554d0ff47756795647d25cb6e6658f912d114ae6429d35d35"
    ],
    [
      "p",
      "e3fc673fc5f99cc554d0ff47756795647d25cb6e6658f912d114ae6429d35d35",
      "wss://relay.primal.net/"
    ],
    [
      "p",
      "12ee03d11684a125dd87be879c28190415be3f3b1eca6b4ed743bd74ffd880e6",
      "wss://nos.lol/"
    ],
    [
      "client",
      "Amethyst"
    ]
  ],
  "content": "The second one is indeed safer. But I don't think they'll ever get 4032 blocks; I'm not even sure they'll get 4 mandatory signalling blocks\n\nSo I think if you want to guarantee that splitting is possible, then - like you said - you need something like this:\n\n1. make a splitting transaction, with a large op_return, and broadcast it at or after the start of mandatory signalling (August 8th/9th), and broadcast it on the \"legacy\" network\n2. If that confirms on both chains, then the \"split\" has failed, and a BIP110 miner broke the default policy. You haven't lost funds, you just need to start again from the new address.\n3. When it confirms on the legacy chain, then you should quickly RBF to spend the funds back to yourself\n4. Now you have successfully spilt (unless you're unlucky and reorgs happen!)\n\n.. come to think of it, that's just too messy, I think\n\n",
  "sig": "0d373872690f6052f395b39cd953bbce7d4fcd788c828030bb24fc22eeeea4c37b5e93fed78e4372b4e01e3123e021a5e91b376b447cc49e47ad55785cb5c40c"
}