From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Fri, 02 Oct 2026 06:18:29 -0700 Received: from mail-ot1-f64.google.com ([209.85.210.64]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1xCd9g-0002Y2-Nc for bitcoindev@gnusha.org; Fri, 02 Oct 2026 06:18:29 -0700 Received: by mail-ot1-f64.google.com with SMTP id 46e09a7af769-820ce3bb94bsf72111a34.0 for ; Fri, 02 Oct 2026 06:18:28 -0700 (PDT) ARC-Seal: i=3; a=rsa-sha256; t=1790947102; cv=pass; d=google.com; s=arc-20260327; b=dvq8m/TQ+w2OZ0rZuoWGxSbs87PDzAqfSYwBUu4yfSuANzCkVtueubDaUuOTEpaIXI Vop1+bKlFCYnEmaOMh7wCFGD8vANgq+FI/S5z2NckZpqqdVG/ZMlSwkbDbaYO965d8xr biMHYmMZ1plTwP++l0UVAZkiqPrkSZ5SXoHYXRfWXFWtkVNdjhCfIjBHwZ4GnkOTD++s 9LqlZX25Esl5gHOUq5NcILf9Ot0HgeSRuWmtVT7+yEo7gkpOwPOss2L9zmiulAM9QsJh YgdhTE6jCZ+KbBDo3Ay4vmQcFZWGHeoGkyzWtssnl9ToJRgZIYAxpKiKvXQUQyo5tNx/ A26w== ARC-Message-Signature: i=3; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:cc:to:subject:message-id:date:from :mime-version:sender:dkim-signature:dkim-signature; bh=wkaaViqWYi/GPNv6JCVNlQ0X9CvUhvVYtnXXfP1W3pM=; fh=UDg1Sg0yHYp0u6NOKvn/vcum/xHOnkeO/d9l8mj6upw=; b=KRHXDSZ6bLnWdOuX6n6OQYIt7C7o9OMMNA6YeADm7YD/Cb4VBVnz+Gn/gN01VH0AAn vsJbvw7i9rPon+4BTy0O060ZBEmyFwosQzQ7YhGpk/tPXLcPYaOYaauwXdhrEu5mA9dF DNnRGSpaNocSvTcWGnMC6OZ0vEjCv3U4rzH4QwcsJlVSo1PZr/5IxkK768Kz+DA60NA5 hFSTQpKzTN8qbvqpMSl/FnlehXFh1gxduQDFah4VvJhinhSaN+ZUhn4l5ekekQn5lMNW SnIT+VJOJ+3R7zcKX188jxAeZZ7Yjo30rbks5iRUzHK5Lf7fsP/6BNt2uFfwLXFdSnUF rsEw==; darn=gnusha.org ARC-Authentication-Results: i=3; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20251104 header.b=aK4WnFX9; arc=pass (i=1); spf=pass (google.com: domain of antoine.riard@gmail.com designates 2607:f8b0:4864:38::f as permitted sender) smtp.mailfrom=antoine.riard@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com; dara=pass header.i=@googlegroups.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1790947102; x=1791551902; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:content-type:cc:to:subject:message-id:date:from :mime-version:sender:from:to:cc:subject:date:message-id:reply-to :content-type; bh=wkaaViqWYi/GPNv6JCVNlQ0X9CvUhvVYtnXXfP1W3pM=; b=ki0/YKVAbQrk90JQCtRSZ1DhJhRHDRoDfpBVjYvDLtvXlvm6enwcvHH9oeQM/D2LQT kvmalQhrZfXU6/1fus8nrVl7dvfLz947taZeuEegY4K4h3xy1yMarUZ2pa+9mUcPa1wX roNnbbK2Pyc73gsq9sLsFPDvD+gxCFCnJ937SANnH2ZoH/wYT4BWobz5aPJFCHpG6E9A oIVCMez+KB1pIW3GHU+KXCCX4bVkvaO/7F2o0Dft0//xHMiyX/koZhR1Ec24hIp5PSjs IFBO/k5c1fMGq7NRDzV5dtLcj1/l8JsUxggEsQ6LVMpY/8ea6Q3bX+Aop1GwAoanU/Z8 pUWA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1790947102; x=1791551902; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:content-type:cc:to:subject:message-id:date:from :mime-version:from:to:cc:subject:date:message-id:reply-to :content-type; bh=wkaaViqWYi/GPNv6JCVNlQ0X9CvUhvVYtnXXfP1W3pM=; b=d89Y2ffZ0ndl8NCRKYrt+U9ASSCBWULBASt5xL12S63T5cCDSvqbJrj2EBZRMGxWTu DkoJtGtjiWPe7t7IyQGRY6q684w8cT+W5tdBbUJ6tkqtlE3osx5K6j1K2HQ2oVrVLwD3 LZX+inhpSoTl6TYr0Wad3cxXwjOWRfxydp8C9wfujXbYb5IgBPbzY7MgC+540+Biy6iN SdbohztgeWq7rFau60T2TxJGca80mn9ta0mKQiE4wfRqgLojqv1TY7yQeiVF5xpeEgBI ZEvOxfFHZVs3j0qw1CVGYqG0fInTqpnuhuwAMiogHtZ+u7LyPtH+OtlUqxY2eubR+oHe rmOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1790947102; x=1791551902; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:content-type:cc:to:subject:message-id:date:from :mime-version:x-gm-gg:x-beenthere:x-gm-message-state:sender:from:to :cc:subject:date:message-id:reply-to:content-type; bh=wkaaViqWYi/GPNv6JCVNlQ0X9CvUhvVYtnXXfP1W3pM=; b=B+8pQxdanRQJ5XMZHukEEzJpimwORFTqXkiugXUmqhmGOPXzwvxFKhWJJbgDymulzU p9K0ycRvKG2ai4HktwfzGc2q/aUWqwri0Q4gG6/YgLbifeewubCDD0yqtdZEXLlt6TXq VInU1b3AYaOIVpL2oYuJIuxGQBiwX7Ozqz6tF37Rt2HwW7WKl3nidd8JkctbRTmep4iZ 72sdFc6WN3QqcY9QiMnChMcOG+8DPTizMRR73DoMut/zQT0P4L1BkVsXgS1oaDlk5nJI RUwm9ElQZKb5zaoSvC5SubSibHfJiTEypO1/YDiVePLufJvOOebN1U5HdXrzkKMNSx04 Jqig== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=3; AKwUvBwdfuD0wI9oZSRRYjYHXLwf/J7piwkhJGTwHdQbhvEcsh5blBxoUT07/CXlrLaW2fLaMeDdvT9fi7x+@gnusha.org X-Gm-Message-State: AFuF++m7RgMhmNkABATQWHONnx1yiB1wQYFT2mdl+gQtNCVlAWwFmTmo Ruq8ZkcwnFn16Kn9UOuE3hJ+mqSVed+Pak+OoZY6E+gAfWIMwoACnKDH X-Received: by 2002:a05:6820:4b89:b0:6cd:3fcc:96d2 with SMTP id 006d021491bc7-6df3602e447mr2135110eaf.80.1790947102102; Fri, 02 Oct 2026 06:18:22 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="ATskLdfKldQ6KFtr5doQ+HABa31LZNPKFEnZIQnyG253OGkKtg==" Received: by 2002:a05:6820:a08b:b0:6d5:d630:801c with SMTP id 006d021491bc7-6df48b24081ls914395eaf.1.-pod-prod-03-us; Fri, 02 Oct 2026 06:18:15 -0700 (PDT) X-Received: by 2002:a05:6808:250b:b0:4eb:8d60:bd4b with SMTP id 5614622812f47-4f52b7bd716mr1838671b6e.59.1790947095461; Fri, 02 Oct 2026 06:18:15 -0700 (PDT) Received: by 2002:a05:6808:c3bd:b0:4f4:894c:18c5 with SMTP id 5614622812f47-4f52e253e99msb6e; Thu, 1 Oct 2026 21:59:47 -0700 (PDT) X-Received: by 2002:a17:90b:3d86:b0:39e:6c68:c77b with SMTP id 98e67ed59e1d1-3a6ce83b91emr1616159a91.49.1790917186256; Thu, 01 Oct 2026 21:59:46 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1790917186; cv=pass; d=google.com; s=arc-20260327; b=Wlk0800xtcog7sqQTIS9kPhRMj9jfuLlO5ru09/+Zx4Higecxvb/EooM+ak/N1J+RK cnbrUMvP/O9pWmfT44HL1QoQqVMfMVEfrHMPXHMhhmfVxZ1RCGn0XsfqLRoLg6xIBdU4 YJVki2nMSWS28qKjwQxQAJp5GoUc9vEgXYkKdD9dvFLaCnAAdA8RED39Ff6ISyMfLqEm 9YwFXW6YXJcTkwG+ng1EJASImI5/Goc65o5apNIVTi1mpUiHX5P9L2ITAytTNedfkz2l Gxnu918kedtZZdHwagtBzDCuK5I5cbiYLQ6+eOACVjugQ2b6Pk6UUaRabwh2ccsvPxbS jtLg== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=cc:to:subject:message-id:date:from:mime-version:dkim-signature; bh=lheHmdy+f+kqfXsnaZvH5tDWWm3chDVeZjnXqCXkSig=; fh=rkm3bHbFkkqaOCEhDYIrUdh+uNF0aEpt1sjHeEyiFh0=; b=iIHFwc3Ox6E/tg9fRga8u18YKHuX6DBruKGDXbJxXL9RFf0jv6SKSJwvSV+cfaBm5Q tcMrpxKuDjV5e4+Uiby1qf+xR/eY59Efrb7oPFk0svIlNEmE2cTHq2dNZzLRvlaOPrHa jkUWjO0bikEHt8QNrQgd7IvizrngPfQ7Nr327j2N+nD9tGAPX9cAuz+nIl+0H3PyXryn D3lKr2gwKLJ8/bZE4AL1Inmsw2IXZf3njs0mUhqJMN/bOiY1BmKIt7av8FuDx5c7HoSt kngMO1dmpSeE0CtWx6xyuJd6SmPcDvuFQU+sZxktST44kB5fe7r8VrdxPfN5AfSHqgu+ MeFw==; dara=google.com ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20251104 header.b=aK4WnFX9; arc=pass (i=1); spf=pass (google.com: domain of antoine.riard@gmail.com designates 2607:f8b0:4864:38::f as permitted sender) smtp.mailfrom=antoine.riard@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com; dara=pass header.i=@googlegroups.com Received: from mail-dl2-x0f.google.com (mail-dl2-x0f.google.com. [2607:f8b0:4864:38::f]) by gmr-mx.google.com with ESMTPS id 98e67ed59e1d1-3a6dcf66e94si23748a91.1.2026.10.01.21.59.46 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 01 Oct 2026 21:59:46 -0700 (PDT) Received-SPF: pass (google.com: domain of antoine.riard@gmail.com designates 2607:f8b0:4864:38::f as permitted sender) client-ip=2607:f8b0:4864:38::f; Received: by mail-dl2-x0f.google.com with SMTP id a92af1059eb24-1460bcc512eso4446507c88.1 for ; Thu, 01 Oct 2026 21:59:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1790917185; cv=none; d=google.com; s=arc-20260327; b=W76Ni9vQxsya2Y4SA7dGJxYkQnBzeHdKlQ5v0n01jMoz0t+KRoNbXwG/zIP+Kf85cA uhOVwPcTGOpAOWmBEH69e/qNGvj893Y0f+hMYgzaap3nZ88xvh5gr1X16jp6qSQQE71A 2xXZ3k5Uc5xAlWdV9E3L7CotRFDMzNI9Sz7PpAHYhFZ+2ReqHNAGyyXJjMmtNGVuQ/9t 1NevxBLqz+KoGpXFrbZaC/uBcuZG9H0CIrYKETUns2gxTNQBTxPXI214NFePUBLD1Iwv MdbY9bjS/qStSIHYBVaPPe+n9IxvSjuPBvIUMNsfrz6vyMQqeRV1Eq3AtsUQ/xJyoOyj a/fw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=cc:to:subject:message-id:date:from:mime-version:dkim-signature; bh=lheHmdy+f+kqfXsnaZvH5tDWWm3chDVeZjnXqCXkSig=; fh=rkm3bHbFkkqaOCEhDYIrUdh+uNF0aEpt1sjHeEyiFh0=; b=kLCxh+Wx+TtftpoAdLiE6L+8IZMQTrjveuWk/+foLYOUgMxmVfDKSMJl24Dlk+tAgX OGaIITTgtJsaMzyGcHtuTkrYew6PxnRyr61EPVZykqICzM44gaUjwFX2v9mxvju+hcFL sYpJJTTpZq9ovKzAng4IY1rVcYa4DkZfJleIPQOnLySIHmB2XlcGJIRzhAU3tP3eCQRJ tnQ1gmK6/E4e27/tO17dlVIuHQ0ZopT7zgi/6mQq571O5wO2YtMe3irClysD0KYiIuJO IIqQY9OMg5nMgvSO5yDhRt8TeCeQSyxWnBRBzaBly+Y0W0DCH1e4Twcp/5iXma1UaWc6 zAkQ==; dara=google.com ARC-Authentication-Results: i=1; mx.google.com; arc=none X-Gm-Gg: AYBFou1t8CJcbjZTq7g3mKWZmObhFYU6l+iI3ne9yiUNUfB1MpSjY5UBZh42+zaRtlW Lc0m9ftxG704mnAls0Te4Ltcv8Bd/C6FnJ/ncJqYdzKCVcnG4fhdnPsFV2LcAlWiL6htFu0xCuH TlX6Fv8WAG7qrph+3hPc2XxAemVdjfRXhRl9XC1hlb497oHkulXCzeNOK4pAN825MlB4gMkM4I5 CLV39ZoJ/p1Ka/0AoJ/PWt/0jwv442cZsfazBScjVvTUL9WgpfeeZIiqvRE9oEjEMST7hP5hOJr uyxfL7naRFt6LjraUxMrui5Hm1PtH2U+qxXtFnAKkU1EWfYir8ck2vg= X-Received: by 2002:a05:701b:280e:b0:144:de98:ef10 with SMTP id a92af1059eb24-14f5c5e9215mr1576065c88.21.1790917185109; Thu, 01 Oct 2026 21:59:45 -0700 (PDT) MIME-Version: 1.0 From: Antoine Riard Date: Fri, 2 Oct 2026 05:59:32 +0100 X-Gm-Features: AclHuK-jh0Q7fzjfIChoZWszkXlapbeB9st4R5F_qAwKjZBfeOIMa4NY-qOggsY Message-ID: Subject: [bitcoindev] Getting BIP54 past the finish line To: Bitcoin Development Mailing List Cc: btc@ariard.me Content-Type: multipart/alternative; boundary="000000000000a40459065cd4669e" X-Original-Sender: antoine.riard@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20251104 header.b=aK4WnFX9; arc=pass (i=1); spf=pass (google.com: domain of antoine.riard@gmail.com designates 2607:f8b0:4864:38::f as permitted sender) smtp.mailfrom=antoine.riard@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com; dara=pass header.i=@googlegroups.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) --000000000000a40459065cd4669e Content-Type: text/plain; charset="UTF-8" Hello devs, Writing this post to do a summary of where from my viewpoint BIP 54 is, in terms of technical readiness, and what are the remaining steps to be done, to move it toward its technical finalization and after that to activation. Indeed, it goes without saying it's representing my viewpoint only. Back on the chronological timeline, the great consensus cleanup was put back on the table by Poinsot at the end of '23 and beginning of '24 [0]. The aim of the consensus changes is to fix long known security issues among bitcoin protocol devs, even if there is a divergence of viewpoints among them on their severities, and necessity of a consensus patch. Those issues are (a) the timewarp attack, (b) the long block validation time arising for pre-segwit scripts, (c) the merkle tree malleability with 64-byte transactions and (d) the possibility of duplicate coinbase transactions. There were numerous design discussions on the best way to solve each issue [1]. During those discussions, it has been made the point, that it might be necessary to fix more advanced variants of some attack, notably the Murch-Zawy one [2]. In parallel, investigations were made on the private Delving Bitcoin thread on the worst-case evaluations for the long block validation time. Early '25, a BIP draft was proposed to the community [3]. It turns out that the new rule to remove 64-byte transactions was (and is still) the most argued against, by some devs. After those conversations, a reference implementation was proposed with test vectors in late '25 [4]. The work was done to address more open technical concerns from different people beginning of '26, notably on the encoding of the height in the coinbase transaction nlocktime [5]. Public demo of the severity of the long block validation time was made on signet [6]. More conversations still arised about the 64-byte transactions [7]. Those are the main elements on the design conversations about BIP 54 that I can remember from my memory, while of course there are more design conversations that did happen not listed here. A pull request on bitcoin core has been opened to implement BIP54 and it is currently under review and testing [8]. There is also ongoing work in btcd to implement the BIP and exercise inter-compatibility [9]. I think there is no ongoing implementation for libbitcoin, though as said I would be willing to contribute to the review of one there. Moving BIP54 past the finish line, in my view, would necessitate resolving the open technical conservations, especially on the disagreement about the 64 bye transactions. Apart from the high level technical conversations calling for progress, more review and testing of the reference implementation is obviously needed. More sound review and testing is always better, higher we set the technical bar, better we're while staying realistic on the process. Testing inter-compatibility with one or more other implementations is likely also valuable, to assert there is no shortcoming with the design. Beyond, though that's might be my personal view only, some parts of the BIP would be better to be more documented for any wallet or off-chain protocol, in function of what they're doing it's good for them to be aware of the proposed new 2500 pre-segwit script tx limit, and the 64 byte outlawing rule if it slips in. Overall, I think it's good to invite skilled eyes that wish to do so to go over the full conceptual BIP 54 design, what they agree with, what they disagree with, what could be improved and goes to publish their grounded analysis on their personal blog, or whatever. A standard of review that was echoed in the past [10]. Doing more real-live testing of the vulnerabilities like it has been done on signet might be very valuable again. Apart of the activation logic, of which the conversation can be deferred later on, what else would be technically valuable to advance the conversation ? Minding all of that, and with previous experience of the design, review and activation cycle of the schnorr / taproot change, it might sounds realistic to slowly start to think about an activation of BIP 54 during S2 2027. Why not if the community consensus is present by then, and of course no "force majeure" ou sh*t hit the fan too much (as it happens in the bitcoin world). I'm only speaking for myself, so everyone else in the (bitcoin) world is free to respectfully disagree with the present viewpoint. Hopefully, at least it is useful to advance the conversation and not being the BIP champion it's easier for me to do such a call. Looking on a long term perspective, there are other consensus changes that will be likely very also valuable in the future be it post quantum or other security fixes, and imo it's better as a community we don't sleep on them. Cheers, Antoine OTS hash: dbc7c36dbce85e4885b4d140bb90a1d775176b7ec60753d02a655e42418062bb [0] https://groups.google.com/g/bitcoindev/c/CAfm7D5ppjo [1] https://delvingbitcoin.org/t/great-consensus-cleanup-revival/710 [2] https://delvingbitcoin.org/t/zawy-s-alternating-timestamp-attack/1062 [3] https://groups.google.com/g/bitcoindev/c/0tSvml90Qcw [4] https://groups.google.com/g/bitcoindev/c/1XEtmIS_XRc [5] https://groups.google.com/g/bitcoindev/c/6TTlDwP2OQg [6] https://delvingbitcoin.org/t/consensus-cleanup-demo-of-slow-blocks-on-signet/2367 [7] https://groups.google.com/g/bitcoindev/c/iCuq6bFKt5Y [8] https://github.com/bitcoin/bips/pull/1800 [9] https://github.com/btcsuite/btcd/pull/2537 [10] https://gnusha.org/pi/bitcoindev/CAGpPWDbbZ7PEpr4iwYwBn+5QcjjCx8qmTZVB98i2Z=UwDfwaTQ@mail.gmail.com/ -- You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CALZpt%2BGwkE1gH2-yrJXt%3DoqkrYR_ubdrMur0PG6aZvziJCHMLg%40mail.gmail.com. --000000000000a40459065cd4669e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello devs,

Writing this post to do a summary of wh= ere from my viewpoint
BIP 54 is, in terms of technical readiness, and wh= at are the
remaining steps to be done, to move it toward its technicalfinalization and after that to activation. Indeed, it goes
without say= ing it's representing my viewpoint only.

Back on the chronologic= al timeline, the great consensus cleanup
was put back on the table by Po= insot at the end of '23 and
beginning of '24 [0]. The aim of the= consensus changes is to
fix long known security issues among bitcoin pr= otocol devs,
even if there is a divergence of viewpoints among them ontheir severities, and necessity of a consensus patch.

Those issues= are (a) the timewarp attack, (b) the long block
validation time arising= for pre-segwit scripts, (c) the merkle
tree malleability with 64-byte t= ransactions and (d) the possibility
of duplicate coinbase transactions.<= br>
There were numerous design discussions on the best way to solve
e= ach issue [1]. During those discussions, it has been made the
point, tha= t it might be necessary to fix more advanced variants
of some attack, no= tably the Murch-Zawy one [2]. In parallel,
investigations were made on t= he private Delving Bitcoin thread
on the worst-case evaluations for the = long block validation time.

Early '25, a BIP draft was proposed = to the community [3]. It
turns out that the new rule to remove 64-byte t= ransactions was
(and is still) the most argued against, by some devs. Af= ter
those conversations, a reference implementation was proposed
with= test vectors in late '25 [4].

The work was done to address more= open technical concerns from
different people beginning of '26, not= ably on the encoding of
the height in the coinbase transaction nlocktime= [5]. Public
demo of the severity of the long block validation time was = made
on signet [6]. More conversations still arised about the 64-bytetransactions [7].

Those are the main elements on the design convers= ations about
BIP 54 that I can remember from my memory, while of course = there
are more design conversations that did happen not listed here.
=
A pull request on bitcoin core has been opened to implement
BIP54 an= d it is currently under review and testing [8]. There
is also ongoing wo= rk in btcd to implement the BIP and exercise
inter-compatibility [9]. I = think there is no ongoing implementation
for libbitcoin, though as said = I would be willing to contribute
to the review of one there.

Movi= ng BIP54 past the finish line, in my view, would necessitate
resolving t= he open technical conservations, especially on the
disagreement about th= e 64 bye transactions. Apart from the high
level technical conversations= calling for progress, more review
and testing of the reference implemen= tation is obviously needed.

More sound review and testing is always = better, higher we
set the technical bar, better we're while staying = realistic on
the process. Testing inter-compatibility with one or more o= ther
implementations is likely also valuable, to assert there is no
s= hortcoming with the design.

Beyond, though that's might be my pe= rsonal view only, some parts
of the BIP would be better to be more docum= ented for any wallet
or off-chain protocol, in function of what they'= ;re doing it's
good for them to be aware of the proposed new 2500 pr= e-segwit
script tx limit, and the 64 byte outlawing rule if it slips in.=

Overall, I think it's good to invite skilled eyes that wish to<= br>do so to go over the full conceptual BIP 54 design, what they
agree w= ith, what they disagree with, what could be improved and
goes to publish= their grounded analysis on their personal blog,
or whatever. A standard= of review that was echoed in the past [10].

Doing more real-live te= sting of the vulnerabilities like it has been
done on signet might be ve= ry valuable again. Apart of the activation
logic, of which the conversat= ion can be deferred later on, what else
would be technically valuable to= advance the conversation ?

Minding all of that, and with previous = experience of the design,
review and activation cycle of the schnorr / t= aproot change, it
might sounds realistic to slowly start to think about = an activation
of BIP 54 during S2 2027. Why not if the community consens= us is
present by then, and of course no "force majeure" ou sh*= t hit the
fan too much (as it happens in the bitcoin world).

I&#= 39;m only speaking for myself, so everyone else in the (bitcoin)
world i= s free to respectfully disagree with the present viewpoint.
Hopefully, a= t least it is useful to advance the conversation and
not being the BIP c= hampion it's easier for me to do such a call.

Looking on a long = term perspective, there are other consensus
changes that will be likely = very also valuable=C2=A0in the future be
it post quantum or other securi= ty fixes, and imo it's better as
a community we don't sleep on t= hem.
=C2=A0
Cheers,
Antoine
OTS hash: dbc7c36dbce85e4885b4d140b= b90a1d775176b7ec60753d02a655e42418062bb

[0] https://groups.google.com/g/bitcoi= ndev/c/CAfm7D5ppjo
[1] https://delvingbitcoin.org/t/great-consensu= s-cleanup-revival/710
[2] https://delvingbitcoin.org/t/zawy-s= -alternating-timestamp-attack/1062
[3] https://groups.google.com/g/bitcoindev/= c/0tSvml90Qcw
[4] https://groups.google.com/g/bitcoindev/c/1XEtmIS_XRc
= [5] https:= //groups.google.com/g/bitcoindev/c/6TTlDwP2OQg
[6] https://groups.google.com/g/bitcoindev/c/iCuq6bFKt5Y
[8] <= a href=3D"https://github.com/bitcoin/bips/pull/1800">https://github.com/bit= coin/bips/pull/1800
[9] https://github.com/btcsuite/btcd/pull/2537
[10] https://gnusha.org/pi/bitcoindev/CAGpPWDbb= Z7PEpr4iwYwBn+5QcjjCx8qmTZVB98i2Z=3DUwDfwaTQ@mail.gmail.com/

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/= d/msgid/bitcoindev/CALZpt%2BGwkE1gH2-yrJXt%3DoqkrYR_ubdrMur0PG6aZvziJCHMLg%= 40mail.gmail.com.
--000000000000a40459065cd4669e--