A well written post and push-back to BIP 110.

Daniel Prince

npub1hghnjjpnvkz8t6gkszuf37d7puwc2qtxc65rnklqsngzv6kkug9qhhfyz2

hex

f601d010869293053f10ef68a9e1b0768b2e13c5233d31c3f9903b53804143f9

nevent

nevent1qqs0vqwszzrf9yc98ugw769fuxc8dzewz0zjx0f3c0ueqw6nspq587gprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgst5teefqektpr4aytgpwyclxlq78v9q9nvd2pem0sgf5pxdttwyzsnycyl9

Kind-1 (TextNote)

2026-02-07T17:38:12Z

↳ Reply to Event not found

7e006f063fbe66b3e438c6d2153beb4121634e5e94a947b75b22a785cd5f9ce8...

A well written post and push-back to BIP 110.

Still learning here.

Can anyone assuage some of the concerns in this post?

Would it hinder layer 2 scaling?

This is covered in the FAQs on https://bip110.org/

"Does this affect the Lightning Network?"

No. Standard Lightning channels use P2WSH (witness v0), and BIP-110's OP_IF restriction only applies to Tapscripts — so they're completely unaffected. Newer Taproot-based channels split conditional paths into separate tapleaves instead of using OP_IF, so they're also compatible. Both P2WSH and P2TR outputs are exactly 34 bytes, within the limit."

nostr:nprofile1qqspqdj3we4h3ny6jhy58rs46the28uv45ucdthwlg70grg9l3vgprsppemhxue69uhkummn9ekx7mp0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9ufhj2n4 nostr:nprofile1qqsrzsrjc9h6jse7zd60vtjmqtypvw2xa55c48x78v25z5fu98gellcpzemhxue69uhkzarvv9ejumn0wd68ytnvv9hxgqg4waehxw309ash2arg9ehx7um5wgcjucm0d58l2jpv

nostr:nevent1qqs8uqr0qclmue4nusuvd5s48045zgtrfe0ff228kadj9fu9e40ee6qpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgq3qzthq85gksjsjthv8h6rec2qeqs2mu0emrm9xknkhgw7hfl7csrnqxpqqqqqqzp7psg8

Raw JSON

{
  "kind": 1,
  "id": "f601d010869293053f10ef68a9e1b0768b2e13c5233d31c3f9903b53804143f9",
  "pubkey": "ba2f394833658475e91680b898f9be0f1d850166c6a839dbe084d0266ad6e20a",
  "created_at": 1770485892,
  "tags": [
    [
      "e",
      "7e006f063fbe66b3e438c6d2153beb4121634e5e94a947b75b22a785cd5f9ce8",
      "wss://relay.primal.net",
      "mention",
      "12ee03d11684a125dd87be879c28190415be3f3b1eca6b4ed743bd74ffd880e6"
    ],
    [
      "p",
      "103651766b78cc9a95c9438e15d2ef951f8cad3986aeeefa3cf40d05fc58808e",
      "wss://nos.lol/",
      "mention"
    ],
    [
      "p",
      "314072c16fa9433e1374f62e5b02c8163946ed298a9cde3b1541513c29d19fff",
      "wss://atlas.nostr.land",
      "mention"
    ]
  ],
  "content": "A well written post and push-back to BIP 110.\n\nStill learning here.\n\nCan anyone assuage some of the concerns in this post?\n\nWould it hinder layer 2 scaling?\n\nThis is covered in the FAQs on \nhttps://bip110.org/\n\n\"Does this affect the Lightning Network?\"\n\nNo. Standard Lightning channels use P2WSH (witness v0), and BIP-110's OP_IF restriction only applies to Tapscripts — so they're completely unaffected. Newer Taproot-based channels split conditional paths into separate tapleaves instead of using OP_IF, so they're also compatible. Both P2WSH and P2TR outputs are exactly 34 bytes, within the limit.\"\n\nnostr:nprofile1qqspqdj3we4h3ny6jhy58rs46the28uv45ucdthwlg70grg9l3vgprsppemhxue69uhkummn9ekx7mp0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9ufhj2n4 nostr:nprofile1qqsrzsrjc9h6jse7zd60vtjmqtypvw2xa55c48x78v25z5fu98gellcpzemhxue69uhkzarvv9ejumn0wd68ytnvv9hxgqg4waehxw309ash2arg9ehx7um5wgcjucm0d58l2jpv \n \n\nnostr:nevent1qqs8uqr0qclmue4nusuvd5s48045zgtrfe0ff228kadj9fu9e40ee6qpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgq3qzthq85gksjsjthv8h6rec2qeqs2mu0emrm9xknkhgw7hfl7csrnqxpqqqqqqzp7psg8",
  "sig": "4d8ae01bbe5be6fcc88f2179f573ce3893a92f870dcb0c08a0afd512bfe3a50cfb75208ad7d695b745322c264cef579f20cc928fd109701b86801f5c413dc418"
}