From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 26 May 2026 18:56:18 -0700 Received: from mail-oa1-f56.google.com ([209.85.160.56]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1wS3VK-0005MU-5b for bitcoindev@gnusha.org; Tue, 26 May 2026 18:56:18 -0700 Received: by mail-oa1-f56.google.com with SMTP id 586e51a60fabf-43a886fe459sf20893200fac.0 for ; Tue, 26 May 2026 18:56:17 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1779846972; cv=pass; d=google.com; s=arc-20240605; b=dWfVy6CxHMGcOgcX6nMCrOiYFK322tSzxOldRHp3ISL7R3Ncp6mBc7JxH5x3bySUAn c2Vl7G3hE21L51aaOjKHjyxVjsj6JXs5JoftbrjHwFpqto7VvpZMldlAbTt24naZ+oSg mMKWzJBunigmm2PcWdlKJT+uFKrscADaGsKsC13sadv4fnG7J8q/MrXhCK/q7DVWY9H5 TVZu5pi6a0iU3zW30rSDPY+7GNVNK3XgPZv+md7eQY1dv9NiHhiyTVXSFvOoLvu4skeg Fjets6SIgqDOeqlFSSBFXuVhcK954mx+DjthGxpYoBXLi+f/N/IcRELno0a94e4mbdVC Qxdg== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:content-disposition:mime-version :message-id:subject:cc:to:from:date:sender:dkim-signature; bh=saQCEp6WrdeZF27gbbNQDywl5+GC19AcVTcA4Hy6cbA=; fh=f+U/loX+CQQO9yXW0SeR9sAeZMzcVjsv3zzv8rlUL98=; b=DRPk863QFxoTP2pdrWj44cNQV9eFSGzEpKv0PZUfEyVv7c3/Zlx4t5X0YbtZ/UiG0Y SZtxT/srLoSrrbB0WK69p/mkH4XMVjUY0TzDmfS6zHhBi3ipZaU6Kwk6QSgbRQWSp1Dt rpkQToFg2JzbujIQylBjrH/eUi5fZ574BKCGLuXAIY7UBJnVZeZnZxhZeEyXCzod3bkE i+zJL48Keg4gVGncvnqFngHgcpDa/7QGMiIDvgwWtNabuC54py+xuLXaNTTL7FD8t4m/ nwivKJW/lFLR9neM9OWzmz76VUUoiODU4AaOmNnrNjSuP3ec6LuIDFKvy0jIEKdF1qBv gT/g==; darn=gnusha.org ARC-Authentication-Results: i=2; gmr-mx.google.com; spf=pass (google.com: domain of aj@erisian.com.au designates 172.104.61.193 as permitted sender) smtp.mailfrom=aj@erisian.com.au DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1779846972; x=1780451772; 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-disposition:mime-version:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=saQCEp6WrdeZF27gbbNQDywl5+GC19AcVTcA4Hy6cbA=; b=uX7bQanKsqn/phqWz0oIXshHeFRxyZCvM7CYMusiHF14X9kcOadSiZWyh6t8SZ/Y5m JDdiNAR3taHvxqYtbk5He4FtYDSq7V1uDuC6U/FKuO1Y6GU3yZ6jIc9uNPR9AlUyq3KQ YgjtwoSj3uSVkReIr2L3urSUmVYPNNk7ENWAyIjXPB6C9qkekLf6qwKGahA3z3ItsZmy TM1h0Q3NbQrfOrPrQj0qbXtbckp38ut4wy4pUWiLGHaMcgOmFRRb5HSbNAqMTHFHHHk9 fdH9d9Tc3N93dwgNqYosJG31fbcIKd93WpEFZpdul+ga0vQIRBhiYecQg3GwIqJUB/7d k6ag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1779846972; x=1780451772; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:content-disposition:mime-version:message-id :subject:cc:to:from:date:x-beenthere:x-gm-message-state:sender:from :to:cc:subject:date:message-id:reply-to; bh=saQCEp6WrdeZF27gbbNQDywl5+GC19AcVTcA4Hy6cbA=; b=lLWaY0ebH4aLMMTJAl3b14blGvV9kSz525V2fLEcdDHLnhPLpevKWxSrTbayLA8jU8 ns6cqCQB51RA7tyb95tEHakBKTH+ZKkbPRDekW8ySuOtaj3wTMghY3ic+g4ocCp8ud9P M0J7V9kR9ToDHCQQjB/MkOxmyew5xAE4b5NR3aEMgD64jph5CXLnb5hc2KsQEjK7yKDt uWd5vZG5jssAWBN9IiP8KlBtio1m9BkvN35xNbmTXAGc7u8YUOqJPUSXJAOEHYdT6jk0 VYcr0/w5yb4/EX5tDOEGHtJSHhkkiWVv5BsJC3ryOq685B8AN3PQt6QzIk2ukurypkb3 vFNA== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=2; AFNElJ/r93kXpon7PAdCpH+BbXBXDx8d7V8HiGXuznErB7khgQnG3485GlkWS2umMSkomc0Gl3pQGgDdPsw+@gnusha.org X-Gm-Message-State: AOJu0YwzaJTzGKPLss4NO/w7s84isfSMr/MmcQxU26ReFM+ktI2r4JgG WaF8QMT1YhW8kqTUloR7qKxZ7PROVaZ7tQs19hzWwdwBLP4UytNL19IN X-Received: by 2002:a05:6870:a3d1:b0:42f:b963:cd49 with SMTP id 586e51a60fabf-43b5aed59b3mr12406124fac.30.1779846971694; Tue, 26 May 2026 18:56:11 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="AUV6zMPhJWFxLVLoTAgXLBzgrguxwkPwUEJkH2cLQDyemd4YJg==" Received: by 2002:a05:6870:6077:b0:43b:92b9:f770 with SMTP id 586e51a60fabf-43b92ba083dls1996838fac.0.-pod-prod-07-us; Tue, 26 May 2026 18:56:05 -0700 (PDT) X-Received: by 2002:a05:6808:1b10:b0:482:e5d4:151f with SMTP id 5614622812f47-4854a178862mr12992337b6e.29.1779846965200; Tue, 26 May 2026 18:56:05 -0700 (PDT) Received: by 2002:a05:6808:8907:20b0:479:9f23:6621 with SMTP id 5614622812f47-4854b944420msb6e; Tue, 26 May 2026 18:51:40 -0700 (PDT) X-Received: by 2002:a17:90b:57c3:b0:36a:f625:47f8 with SMTP id 98e67ed59e1d1-36af6255bf9mr7332743a91.26.1779846698266; Tue, 26 May 2026 18:51:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1779846698; cv=none; d=google.com; s=arc-20240605; b=Qz5kguxzeQrgn4IzO0/uRb3UWQYCOok8ecfI6tpbfS3er1ueoT/Q/sHa2InN+BwlGT T7HhDi7HE83zkjpIshMEAxAlObslWeaf1wraRq9hJHPxBGMQVar4nDlHkgngFnNsZ/u5 lAvSyJ6rdAw7GPuc7+ANu2NG9q+bBLFfQdfJ9QWgY9t62ZRakkSu2TpooEv2YqSpExU7 fqE5BMdzVMPE2tDeJVorR0/YQsJaOo/wNkRtmMNRRCZrFIZwLdqhDVGathIUwwhq23gX 66qhNbj7S68pArTylLHVnvhzbJJdKJKmsbyGv49I88a4D9gt2hbRdOlKhNDjfqttXl6S hmKg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=content-disposition:mime-version:message-id:subject:cc:to:from:date; bh=vnhiI9yvzasbec6yP5VnQRw1NvTwABIfxfmNhfIl1zU=; fh=4kePc997RIanDmRxTBEYxXSyOTxcLApMeD9KfyngXIg=; b=FsW4rgARuUwvwNBexsVv1DAH8lqo7SabKn2erDOfhqnUnO5GsIsfooz6B74Ks5/FzG fQuI/dcTtyudan/M2qpxn/by3MD6iYYYR+Ak990+YjBru2rwWbmpuMFe6V/rCvGBCSM+ RQmoYMAib5YIixMi4FIxIbs2dkBnjenKwlUfl0B+1AxcpG6XwBPuMTlTuIiVGwYbrKZl x9fhxsqhPbJf1kAnn6hk4l+V4qypgpcGbXuWnymms85zQ3LEtb0Z+kv6kwnZCl5h+VYd m+gUVDAdOzf+mnlFh66eA8Mhnc1K2x4rsm77ZvXQzs9sV2JVERj0FkcJoPG3/ELq43XM uBPA==; dara=google.com ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of aj@erisian.com.au designates 172.104.61.193 as permitted sender) smtp.mailfrom=aj@erisian.com.au Received: from cerulean.erisian.com.au (azure.erisian.com.au. [172.104.61.193]) by gmr-mx.google.com with ESMTPS id 98e67ed59e1d1-36b265505a1si16657a91.3.2026.05.26.18.51.37 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 26 May 2026 18:51:37 -0700 (PDT) Received-SPF: pass (google.com: domain of aj@erisian.com.au designates 172.104.61.193 as permitted sender) client-ip=172.104.61.193; Received: from aj@azure.erisian.com.au by cerulean.erisian.com.au with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wS3Qi-0004AO-1t; Wed, 27 May 2026 11:51:35 +1000 Received: by email (sSMTP sendmail emulation); Wed, 27 May 2026 11:51:30 +1000 Date: Wed, 27 May 2026 11:51:30 +1000 From: Anthony Towns To: bitcoindev@googlegroups.com Cc: Murch Subject: [bitcoindev] BIP 3 and issues on BIPs Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline X-Spam_score: -0.0 X-Spam_bar: / X-Original-Sender: aj@erisian.com.au X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of aj@erisian.com.au designates 172.104.61.193 as permitted sender) smtp.mailfrom=aj@erisian.com.au 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.8 (/) >From bips#2175: https://github.com/bitcoin/bips/pull/2175#issuecomment-4550089883 > > Lastly, the BIPs repo does not have an Issues tab. An Issues tab would > > allow for discussion of such things without opening a demonstrative PR. > (There may be other reasons, but one hypothesis amongst the BIP editors > as to why there is no Issues tab, was that the idea was to have those > discussions take place on the mailing list.) (Presumably, there was also the BIPs wiki for comments about BIPs, though that's no longer encouraged as of BIP 3) I think not having some "centralised" place for finding previous discussions/feedback about a BIP is a flaw in BIP 3 as it stands -- searching across bitcoin-dev, delving, stacker.news, twitter, nostr, random blogs, etc is certainly possible, but it would be nicer if that were a fallback, rather than the only option. I think there's basically three classes of feedback: 1) feedback that the BIP author(s) agree is a concern, but haven't figured out how to address 2) feedback that the BIP author(s) strongly disagree with, but that is considered a reasonable concern more broadly 3) feedback that is mostly dismissed as trolling and not taken seriously outside of a very small group I wonder if it would be feasible to include the first two sorts of feedback directly in the BIPs repo, making it much easier to find. For example, class 1 feedback could be added directly to the affected BIP with the agreement of the author(s), under a new top-level "Unresolved issues" section or similar. (Issues that are "resolved" can presumably be addressed more directly in the BIP, eg under the "Rationale" section) Presumably, BIPs that have an "Unresolved issues" section would not progress to "Complete". Class 2 feedback, where the BIP *editors* agree it's a reasonable concern, despite the *author(s)* NACKing it, could be placed under a dedicated BIP for class-2 feedback across the repo that's maintained by the BIP editors, perhaps as bip-xxxx/feedback-bip-yyyy.md. I guess bip-xxxx could actually just be bip-0003. Hopefully editors would be able to do a fairly quick/easy private vote to make decisions here, just a call on "is this worth surfacing to everyone or is it better left on whoever's blog?" rather than "do I agree with this criticism or not?". Both these types of feedback could then be refined over time to their best version by filing PRs on the bips repo. And just as bips themselves can have "Discussion" links, feedback items (whether class 1 or 2) could also have links to broader/more-detailed discussion of the feedback on mailing lists / blog posts / etc. I think this would be a substantial improvement on the state of the art for things like BIP 39 and its "Unanimously discourage for implementation" criticisms, or, eg, creating issues against bitcoin-inquisition/bitcoin [0], or commenting on old, closed PRs [1]. [0] https://github.com/bitcoin-inquisition/bitcoin/issues/74 [1] https://github.com/bitcoin/bips/pull/682#issuecomment-4503369974 Class 3 feedback, where both the BIP authors and the BIP editor group don't think it's valuable to surface, would still have to be raised externally and found by web searches. (For class 2 feedback where the people complaining also have a solution in mind that the BIP authors have rejected, the obvious solution is to create a new BIP aimed at replacing the existing BIP) Cheers, aj -- 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/ahZOIkGfmJBbCffy%40erisian.com.au.