From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Mon, 10 Aug 2026 04:56:30 -0700 Received: from mail-ot1-f56.google.com ([209.85.210.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 1wtOcH-0001XP-KH for bitcoindev@gnusha.org; Mon, 10 Aug 2026 04:56:30 -0700 Received: by mail-ot1-f56.google.com with SMTP id 46e09a7af769-7ead32f5c6asf988646a34.1 for ; Mon, 10 Aug 2026 04:56:29 -0700 (PDT) ARC-Seal: i=3; a=rsa-sha256; t=1786362983; cv=pass; d=google.com; s=arc-20260327; b=Xa/iF8uCtqgAAfSVjjNkxK9QSokhIEPaJi17MSBpKfGgQ1KfGYmyFDN1cXd605x01B tL7GED2HTP+naR2IgQG0LZFFM9D5ZfFYyb6v+Z+v29qTl07DyUytWQdvaQTl+QWMgI8n 53T/S8Mw5hrMfvcQBGt/UVcjbw4ZysjPNr8aUw9Qk8Y3yHPNsJ2ieyL9TX+saoqxpIuV o2vVtysnzWv9McZTgbhE1HAIwrP7gCSsU+wUzsw6R5Vp+SelJagJ558simZRKVIRkWoo SiIIE0E6gqzGVYC0L9EdbGvWBTt3YOdRuD7EjDu1LtSV3DMnPyQS8M12eaMm2C4G69th A3Rg== 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 :in-reply-to:references:mime-version:sender:dkim-signature :dkim-signature; bh=qB+wmrWPWhNr1m510ZcWMXZggt+6aAkg/Z3xegIARpo=; fh=o7HriOtkCFDe58YRciYki9rmMjxp8ZDWjWqTPPYKnSU=; b=UyEpfzrXcwR/qyfaygi6chCC/BqhsAYhuPLcIVA0sWtDMF+mf4iv9uRfALpczro8Me N6EBDzGEKKBkWIM6FQiyEAvzARlyO8OKAF51cUTth5qogX4Z4BONlk7pR8s2o/kXykvK WM/ccKZChee0KFHK5aGHqgkvf8BJ+uXckBbZY2AYv1lsn1OVV8ojxZqgcZYChD09WXMg Htxj43TuJvKw4/RZUySS4x+RSDpVGRSnRLqlUJ2E/y/iQgYB2l8FvRyr6GRnDIC9XgwK L17EL6UfQHF3KP3X4s1XjXZ/8o4WxqHYmX4kfECdB4GabKfpfqk4ejoAdOyKMYTt9KEm kxHg==; darn=gnusha.org ARC-Authentication-Results: i=3; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20251104 header.b=Celpx4AE; arc=pass (i=1); spf=pass (google.com: domain of saintwenhao@gmail.com designates 2a00:1450:4864:20::22b as permitted sender) smtp.mailfrom=saintwenhao@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=1786362983; x=1786967783; 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 :in-reply-to:references:mime-version:sender:from:to:cc:subject:date :message-id:reply-to:content-type; bh=qB+wmrWPWhNr1m510ZcWMXZggt+6aAkg/Z3xegIARpo=; b=VBlz/7FCpIN8kXlzrd+0G8FafnrI1LPfnFW6gkXi1Aeo9eZ4cb1xkOOh+tEsqw1nFS 9BU+dmiguj0Eog8dKiLVk6qpH/YGqcbJn4QK0/CKfNZUkDf7eNE/AgXIlj8D0/ccyWyB OtxZN2vmi+kyOBB4C4vpPdxoeN7ug5bjAbnZqLsnc1mkzZvhpKHFRWhT/56n6jcCkPDr qBo7As1F1PrAJmakUrXjBLnG1Yfqhqypm8il2lFnH8NHxVNHcykU1qzSk3/HKANO+Bgs yx/IllhVv2ksAmhoY+1/7zQE66UL/mvTDjXJEnlT0ZFRuBFCXrSXsUWw29viYCWQXcSv BULw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1786362983; x=1786967783; 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 :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to:content-type; bh=qB+wmrWPWhNr1m510ZcWMXZggt+6aAkg/Z3xegIARpo=; b=Au/aRMhE+uP2t6cm3mc/x2FB5zX3wKPyUs+XtPj8bMPH+4Xla9sIRQ8Pkk+iX3tDdl lnWDHIkdlIlrT12xTg7dYNunO3SwAmPY/bJc5QTFrN6jO/28XTKaGNE1OLuwY9ZIA+gJ JRneTSehy4S0k8StoUDqZSjFgGTFthxqQ6hLqh1Df11Oxu3Rm5JRGe4BS66/T2ElQYl9 5Gd/AqT5PuZmLJwF5POqs+16CtEYJEy00Lh+GWgtXLKw6qZYvXvIpVvJfrSmPatkpQqJ 51poxGDqtlSOLaJabYvioJkmDsLgcTJYlHANf3EE7zF38ddeRIyg9nzZ9cbF8vo+zDDO sNQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1786362983; x=1786967783; 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 :in-reply-to:references:mime-version:x-gm-gg:x-beenthere :x-gm-message-state:sender:from:to:cc:subject:date:message-id :reply-to:content-type; bh=qB+wmrWPWhNr1m510ZcWMXZggt+6aAkg/Z3xegIARpo=; b=JvaxV4PSLIIShqYhKqwU3FlrW9rrTiYvmzdZ8YUYWd94eK1DedxyF45SvqLmWgvBHR nUHQTO07CWzfc2tP4jcvsS9XRe6ajw0zWWc1Gi1s/TK7WBDIkXxrmA3bA2XsFJ+OvKDT tARaVjjW0OpFBhGa5EP7hdmWp3cbvZxbPGkXVO+QDIFVgOf/98Kj8I6YKDgZHzYZoAuN YZ/51Z1XRi9pUKVGUzfD4GHMzPTWhpdGDphGwmo6XamPsybDtC9pRSjtt/LfRZKByfjB YejtBJmGm3p9IDuvz0UsCPr1We88jpdIm3lPl1efeCEvI8W6v1/xaiXsZCymumxWr5O+ OxWw== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=3; AHgh+RqsnAo4dwee4g/xyeAvi5bAVsKovEsQ73R9WDnRwMI4TDkr08kLDUDnjnnlj1aAZygKrovQdMW9vlPj@gnusha.org X-Gm-Message-State: AOJu0YxcP2roZJnb3jglrXZnZLT37koNnshNKdCY9GKosw+Szlc/b2ne kLqfyqIAsO2nyX5565ohn2gYDxFTF/Ueq5z0GV7Sulu2x+7GChBCOlFO X-Received: by 2002:a05:6820:8c9:b0:6a3:2368:4cc5 with SMTP id 006d021491bc7-6b09095f2d9mr506826eaf.35.1786362983217; Mon, 10 Aug 2026 04:56:23 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="Aa7YSPRCKbbx0YspOUPJ0lfk7C3Aw7BaIE3YgAQJEQ4wjnBoSA==" Received: by 2002:a05:6870:51f:b0:459:1566:9e14 with SMTP id 586e51a60fabf-459cda63dd8ls1891845fac.2.-pod-prod-04-us; Mon, 10 Aug 2026 04:56:18 -0700 (PDT) X-Forwarded-Encrypted: i=3; AHgh+RpW9R0UZsYyh3LcLIeJOydH6ors87qB85OzlRwyh3ncS9/DfQNVVTGTSyrfBWMkzoLhXnd++fN5SJpZ@googlegroups.com X-Received: by 2002:a05:6808:6902:b0:492:973e:1c23 with SMTP id 5614622812f47-4b1e7936ee1mr403738b6e.15.1786362978476; Mon, 10 Aug 2026 04:56:18 -0700 (PDT) Received: by 2002:a05:600c:2944:b0:495:6266:d77a with SMTP id 5b1f17b1804b1-4995b133611ms5e9; Mon, 10 Aug 2026 04:54:40 -0700 (PDT) X-Forwarded-Encrypted: i=3; AHgh+RoQxc1PL3vw1JZ+l2n1VM41nyEm3IIXqhxTrEawVdaCXcIdQQqe367zWCoLOuWoWzvnT4v56k/ai26h@googlegroups.com X-Received: by 2002:a05:600c:3586:b0:494:6baa:ccef with SMTP id 5b1f17b1804b1-499619833admr260475815e9.11.1786362878629; Mon, 10 Aug 2026 04:54:38 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1786362878; cv=pass; d=google.com; s=arc-20260327; b=V5ITiPetteJ6KEhKK9HBByx0ih1SJ7Dbi34VbdX8jbpncqZGuFXhofg0Ha9XykBWm8 mRJfju2pFr05lnQ8dgubmmVNZYrJqes4NN4ZNkr9kCSF+cmjXbPosewAbAILfwAXafcw rRmib9H8ETBpGnOzRdO3itfwsBncwuTisPnxKCQeHR+dYsiKQ0tHfP08NVTO2wNpardC LFugZY7Oe89nNF3BmSZJiWQcO3AblMIHwqxcVeCSaDHPkW8ysT0KokLtSIsNmfIaIkMK 8OFhvhL6qEJ+sFeRbsmfyYLzAOLEZX/5x4zaxipHT/asAaSCQUWBFqFsnYvk4q1wOpNM sNag== 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:in-reply-to:references :mime-version:dkim-signature; bh=XHdEVxX/A9p7rE6aPcwYC9QVrI+bep0YbDqAl9nXOGs=; fh=axUwQSidyEQ0+KCVEk0F+mivUCTXxxTPmxXYBPrU/Uw=; b=XJJsDt3bnJ863oddAFaHXB9oJltiHBpxGnxjQaxILvp8eV4Mz5O2p5046N5vPj7ZCO 5ukpWTHiVLMeZTDLuqdJAgCGLaa7kovkS7hp7tyOvJrQlUahnt1nZmzsnW8ZuiqGitwM fcIJ7cEa/27M6IdP6yG2q+UVpwj6+Z7ASTIfACoRTVBnKObca9L/vYZPHPJPW4YgaUHT t+HVsGvwPdb9gnG2993XHljJ6PTq5QtTFQ1FgV7iyhtJswZ+CXoEzia5S1sLT44Aw4Oy K0FyRfcJJlZXIt+c/pwQngoDt74rSPa769iKtXv4GTF6cHIXQDUpKy8oRsIxvoQwD6k0 2OLA==; dara=google.com ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20251104 header.b=Celpx4AE; arc=pass (i=1); spf=pass (google.com: domain of saintwenhao@gmail.com designates 2a00:1450:4864:20::22b as permitted sender) smtp.mailfrom=saintwenhao@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com; dara=pass header.i=@googlegroups.com Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com. [2a00:1450:4864:20::22b]) by gmr-mx.google.com with ESMTPS id 5b1f17b1804b1-4995bb852f2si1265065e9.0.2026.08.10.04.54.38 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 10 Aug 2026 04:54:38 -0700 (PDT) Received-SPF: pass (google.com: domain of saintwenhao@gmail.com designates 2a00:1450:4864:20::22b as permitted sender) client-ip=2a00:1450:4864:20::22b; Received: by mail-lj1-x22b.google.com with SMTP id 38308e7fff4ca-39c74c469e8so10793741fa.0 for ; Mon, 10 Aug 2026 04:54:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1786362878; cv=none; d=google.com; s=arc-20260327; b=Sp2mRUw04ZEVqbUlNSU6s2pBUXw0Qx+3uAyRwNZku6/jiod6BgXoicfDfYCj5r5NaZ KQeRC06q48iUV32OGnp/Xsk0sjLERQap/kXg/gPdNmn1DJ+2KgU5bnVD6GNI3NNS6Eaq c5K2AR8ltmAjuKcd+0RCtdnD+TCu36qB0tGci/ZdimsdyL+rroON9yvXfqDRua1Ss0zS Y6T2kMno99HzrI6p1Zua1tZrKSwT8VHZUgHITb0nx++qA2/UWPNzrGVBk6iKQj4jJfTT 2vJwPk1w1pz1LyjOg70wjiWU/KksVHYDbQxfs1P+v+RZTfE7bXG4l6YdsdGBym/5q7DP bDLg== 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:in-reply-to:references :mime-version:dkim-signature; bh=XHdEVxX/A9p7rE6aPcwYC9QVrI+bep0YbDqAl9nXOGs=; fh=axUwQSidyEQ0+KCVEk0F+mivUCTXxxTPmxXYBPrU/Uw=; b=Bnqkm6uIsLOd35GpZW4k6loiza04IHV246HCfSu88LRFI2EW3+0Ime2aKW2KB88fAm YQ5k8iZyKSLpIqdHtrjtXjEhBA/GLoktJtWnwIlyn6TfrTXeazy/4BIXdb7PqGH9Wnu1 5aK6hh/j5jqLeNV3P8B5R7EJcD3gX5aoJDSIIRIj+9PS6Ji95ykA8AJRqb1JIvb/5pKp B2+vI7mUckQfO1AacQB8GR5MTx5GROVTKfyxIUOnlai1zje4odV/DeJnYU1T0jt5jFKl kVi8lzXnCTTXM1ySDCgy1mflgvz98zq/1DygHpj3CyGueH8CY5RjwqRgr0Qb+qxZCins Bbpg==; dara=google.com ARC-Authentication-Results: i=1; mx.google.com; arc=none X-Forwarded-Encrypted: i=1; AHgh+RqMdwH4YgtvibsSPRtNZOJhcmqNBj7uZtUwLzjPmGt5egELU2XpqqJfZu5X40sDc0Nsh/oMzWa3AX1g@googlegroups.com X-Gm-Gg: AR+sD13LiIkaR5IGPljOGLZ/JIlKqZnlchi2gGknwOLBOIX4Xgpk/5X1IWM9ZtE4FDL 4IMmGGRNbWsmtaLjaCOAhRI05/k9GYqfmnErmwjvZ+Ap0JuVn67UfaBq4ys7hrPOiuwgLtMa1Z6 FNMvvy+sd0wAdaHtZsSW1H8y97rdrUSncSV7oDmir3lCm0qVa8asiWll+spBZtsCn3CgwInQFYh WH99pXgnwqT6AoAJn+IIzgo+7642rQfrBGZ1RGU7ho+FGc2rrBhsUDbUir9Rq0pfIhebZuCcfc1 1D4q7cCgvyyUi5O4pOMyuujRQNT2Dl/O7pIHKF8HdwHBsgvl6C9XQLUS5IppSoJFz6SBJogDuUz OfoUBrbagmGA= X-Received: by 2002:a05:651c:a38c:10b0:39f:bc94:eba3 with SMTP id 38308e7fff4ca-39fe5772ff8mr14615551fa.16.1786362876423; Mon, 10 Aug 2026 04:54:36 -0700 (PDT) MIME-Version: 1.0 References: <474c04c7-fa32-4f97-84ae-722f12f08f40@murch.one> <5911e0ad-b8f1-4cdb-bd6e-47f032c72924@app.fastmail.com> In-Reply-To: <5911e0ad-b8f1-4cdb-bd6e-47f032c72924@app.fastmail.com> From: Saint Wenhao Date: Mon, 10 Aug 2026 13:54:25 +0200 X-Gm-Features: AUfX_mxbqvkFM6oHPJqEtI4jBcQA9qV29OCz6YReEI5nU_gK8_2UYvAdHogAcwM Message-ID: Subject: Re: [bitcoindev] BIP 110: update status to closed To: Sjors Provoost Cc: Greg Tonoski , Murch , Bitcoin Development Mailing List Content-Type: multipart/alternative; boundary="000000000000b072b10658b00492" X-Original-Sender: saintwenhao@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20251104 header.b=Celpx4AE; arc=pass (i=1); spf=pass (google.com: domain of saintwenhao@gmail.com designates 2a00:1450:4864:20::22b as permitted sender) smtp.mailfrom=saintwenhao@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 (/) --000000000000b072b10658b00492 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > I could spin up a BIP 12 (OP_EVAL) node tomorrow, reject P2SH by forking off at its activation height, and probably mine a whole bunch of blocks trivially. Well, in the past, there was an altcoin, which supported OP_EVAL: it was called CoiledCoin. Back then, Luke had its own mining pool, and used that power, to basically make their chain unusable, by mining empty blocks, only with the coinbase transactions, which raised their difficulty to insane levels, where the community could no longer mine it, when he stopped. And then, he wrote: https://bitcointalk.org/index.php?topic=3D56675.msg676981#msg676981 > CoiledCoin now closed. Have a nice day. Now, people can simply say, that after all of these years, he simply got, what he deserved: "LukeCoin now closed. Have a nice day." Of course, any user can use any coin: CoiledCoin, BIP-110 coin, non-BIP-110 coin, or whatever. But if some chain is dead, and nobody pushes it forward, then I guess BIP can be closed: if someone wants to use a closed BIP, then it is just a choice of a given user. > Closing a BIP does not confiscate coins. I guess some people think, that if a BIP is there, then it is somehow supported, or accepted by the community. Which is simply not the case, because we have BIPs for block size increases, which are used only by some altcoins. Probably it is a similar case, as it is with testnets being traded: some people believe, that if a given testnet is included into Bitcoin Core, then it is more valuable, just because it is included. Which is also why people are patiently waiting for testnet5 to be included, to trade it instantly, even though anyone could simply launch a similar test network, and use it. Basically, including or excluding things into BIPs, or Bitcoin Core became more political, than it should be. Users can use whatever they want, but now, some people simply consider Bitcoin Core as a "brand", and a mere inclusion of something to be worthy. pon., 10 sie 2026 o 13:27 Sjors Provoost napisa=C5=82(= a): > Hi Greg, > > Closing a BIP does not confiscate coins. The only way to achieve that > would a new BIP enforcing a confiscatory soft fork on top of the BIP 110 > forked chain. Or a checkpoint on the winning chain. Nobody is advocating > for either. > > Closing a BIP also doesn't ban anyone from running a node or continuing t= o > mine. But the odds of catching up are slim. > > I'm not in a rush to close it, but what would be your own criteria for > when it's reasonable to do so? > > I could spin up a BIP 12 (OP_EVAL) node tomorrow, reject P2SH by forking > off at its activation height, and probably mine a whole bunch of blocks > trivially. Modern Bitcoin Core wouldn't reject those blocks, because > checkpoints have been removed. But I would never catch up with the tip. > Nobody would seriously considering reopening BIP12 in such a scenario, ev= en > if I ran a million nodes. > > For BIP110, it was obvious to me years ago [1] that this was never going > to work, not as a policy rule, and not as a consensus rule. For others it > look longer realize this, and some people never will. Hard to put an exac= t > number on when to close it, though now would be fine. > > - Sjors > > > [0] https://github.com/bitcoin/bips/blob/master/bip-0012.mediawiki > > > [1] see e.g. > https://bitcoinexplainedpodcast.com/@nado/episodes/episode-98-return-of-t= he-op-return and > my comments on > > On Sun, Aug 9, 2026, at 22:12, Greg Tonoski wrote: > > The BIP-110 was activated at the block height as you (Mark Erhardt) > approved in the specification. There wasn't any other "adoption" criteria > (especially "2.5%"). > > As the Bitcoin Whitepaper says: "As long as honest nodes control the most > CPU power on the network, they can generate the longest chain and outpace > any attackers. (...) Each node works on finding a difficult proof-of-work > for its block". The chain is mined by many more nodes than the single one > "Roughnecks" that you mentioned below. Roughnecks' decision does not > represent the other nodes. Roughnecks node is free to leave at will as > specified in the Bitcoin Whitepaper: "Nodes can leave and rejoin the > network at will (...)". Again, there are estimated 18 000 fully validatin= g > nodes in the Bitcoin network and they don't reject the BIP-110 soft-fork > (a.k.a. RDTS). I am running of the nodes and has just broadcast a > transaction. It's not an altcoin transaction. The bitcoins should not be > confiscated. Therefore, I think that my objection is justified. > > I look forward to a reply. > > On Sun, 9 Aug 2026 at 21:42, Murch wrote: > > Hello Greg, > > BIP=E2=80=AF110 failed to achieve adoption in both phases of its deployme= nt > attempt. It got just shy of 2.5% of blocks signaling readiness in the > latest signaling period, and since RDTS nodes mandated signaling, RDTS > nodes relegated themselves to a chain that only found two blocks, while > the Bitcoin blockchain grew by 134 blocks. The sole block author on the > RDTS chaintip has since announced that they have ceased mining on the > stalled chaintip. > > While it=E2=80=99s your choice to remain on the stalled chaintip or to th= row-in > with the hard fork that is now being discussed, it=E2=80=99s clear that t= he > Bitcoin network rejected the soft fork. The minority hashrate chaintip > therefore constitutes a forkcoin. Altcoins are not on-topic for the BIPs > repository, and therefore, BIP110 should be advanced from Deployed to > Closed as it is obsolete. > > Murch > > On 2026-08-09 11:36, Greg Tonoski wrote: > > Objection. The Bitcoin Improvement Proposal 110 (BIP-110 Reduced Data > > Temporary Softfork) has been activated. There are two blocks with the > > bit 4 signal (block height 961633) and the estimated 18 000 fully > > validating nodes in the network. I keep running such a node and > > accepting payments even if time interval between blocks is temporarily > > longer until the next difficulty adjustment. > > > > On Sun, 9 Aug 2026 at 20:07, Jon Atack > > wrote: > > > > Hello list, > > > > I'd like to propose marking BIP 110 Reduced Data Temporary Softfork > > as closed, following the chain split yesterday during its mandatory > > signaling period, when its chain began rejecting as invalid all > > blocks that did not signal bit 4 and mining and block production > > stalled on the BIP 110 chain. > > > > Per BIP 3, a BIP may evolve from Deployed to Closed when it is no > > longer in active use. Any community member may initiate this status > > update by announcing it to the mailing list, and proceed if no > > objections have been raised for four weeks. BIPs are not deleted; > > they are retained for historical/educational interest after being > > updated to Closed. > > > > Regards, > > Jon > > > > -- > > 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/cf801753-e5b1-46bf-a0ae-9d88a0624829n%40googlegroups.com > > > a0ae-9d88a0624829n%40googlegroups.com? > > utm_medium=3Demail&utm_source=3Dfooter>. > > > > -- > > 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/CAMHHROy%3DNNoaRc828xp_Qr- > > GJqoDguTrowfBKsk0XuYsgaOhSg%40mail.gmail.com > d/msgid/bitcoindev/CAMHHROy%3DNNoaRc828xp_Qr- > > GJqoDguTrowfBKsk0XuYsgaOhSg%40mail.gmail.com? > > utm_medium=3Demail&utm_source=3Dfooter>. > > -- > 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/474c04c7-fa32-4f97-84ae-722f= 12f08f40%40murch.one > . > > > -- > 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/CAMHHROzXou09Sv0%3DXGNFd36Ng= 4Ld-iM44dvcX8SYOb8%3DdoMLRw%40mail.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/5911e0ad-b8f1-4cdb-bd6e-47f0= 32c72924%40app.fastmail.com > > . > --=20 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 e= mail to bitcoindev+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/= CACgYNOJ4MZi-rrZPAfSFTwgOMbdymQbQd8Lg%3Dis-E8f_NU_0bA%40mail.gmail.com. --000000000000b072b10658b00492 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> I could spin up a BIP 12 (OP_EVAL) node tomorrow, rej= ect P2SH by forking off at its activation height, and probably mine a whole= bunch of blocks trivially.

Well, in the past, there was an altcoin,= which supported OP_EVAL: it was called CoiledCoin. Back then, Luke had its= own mining pool, and used that power, to basically make their chain unusab= le, by mining empty blocks, only with the coinbase transactions, which rais= ed their difficulty to insane levels, where the community could no longer m= ine it, when he stopped.

And then, he wrote: https://bitcointal= k.org/index.php?topic=3D56675.msg676981#msg676981

> CoiledCoi= n now closed. Have a nice day.

Now, people can simply say, that afte= r all of these years, he simply got, what he deserved: "LukeCoin now c= losed. Have a nice day."

Of course, any user can use any coin: = CoiledCoin, BIP-110 coin, non-BIP-110 coin, or whatever. But if some chain = is dead, and nobody pushes it forward, then I guess BIP can be closed: if s= omeone wants to use a closed BIP, then it is just a choice of a given user.=

> Closing a BIP does not confiscate coins.

I guess some p= eople think, that if a BIP is there, then it is somehow supported, or accep= ted by the community. Which is simply not the case, because we have BIPs fo= r block size increases, which are used only by some altcoins.

Probab= ly it is a similar case, as it is with testnets being traded: some people b= elieve, that if a given testnet is included into Bitcoin Core, then it is m= ore valuable, just because it is included. Which is also why people are pat= iently waiting for testnet5 to be included, to trade it instantly, even tho= ugh anyone could simply launch a similar test network, and use it.

B= asically, including or excluding things into BIPs, or Bitcoin Core became m= ore political, than it should be. Users can use whatever they want, but now= , some people simply consider Bitcoin Core as a "brand", and a me= re inclusion of something to be worthy.

pon., 10 sie 2= 026 o 13:27=C2=A0Sjors Provoost <s= jors@sprovoost.nl> napisa=C5=82(a):
Hi Greg,

Closing a BIP does not confiscate coins. The only way to achieve that wo= uld a new BIP enforcing a confiscatory soft fork on top of the BIP 110 fork= ed chain. Or a checkpoint on the winning chain. Nobody is advocating for ei= ther.

Closing a BIP also doesn't ban anyone fr= om running a node or continuing to mine. But the odds of catching up are sl= im.

I'm not in a rush to close it, but wha= t would be your own criteria for when it's reasonable to do so?

I could spin up a BIP 12 (OP_EVAL) node tomorrow, reject = P2SH by forking off at its activation height, and probably mine a whole bun= ch of blocks trivially. Modern Bitcoin Core wouldn't reject those block= s, because checkpoints have been removed. But I would never catch up with t= he tip. Nobody would seriously considering reopening BIP12 in such a scenar= io, even if I ran a million nodes.

For BIP110, it = was obvious to me years ago [1] that this was never going to work, not as a= policy rule, and not as a consensus rule. For others it look longer realiz= e this, and some people never will. Hard to put an exact number on when to = close it, though now would be fine.

- Sjors
<= div>




On Sun, Aug 9, 2026, at 22:12, Greg Tonoski wrote:
The BIP-= 110 was activated at the block height as you (Mark Erhardt) approved in the= specification. There wasn't any other "adoption" criteria (e= specially "2.5%").

As the Bitcoin Whitep= aper says: "As long as honest nodes control the most CPU power on the = network, they can generate the longest chain and outpace any attackers. (..= .) Each node works on finding a difficult proof-of-work for its block"= . The chain is mined by many more nodes than the single one "Roughneck= s" that you mentioned below. Roughnecks' decision does not represe= nt the other nodes. Roughnecks node is free to leave at will as specified i= n the Bitcoin Whitepaper: "Nodes can leave and rejoin the network at w= ill (...)". Again, there are estimated 18 000 fully validating nodes i= n the Bitcoin network and they don't reject the BIP-110 soft-fork (a.k.= a. RDTS). I am running of the nodes and has just broadcast a transaction. I= t's not an altcoin transaction. The bitcoins should not be confiscated.= Therefore, I think that my objection is justified.

I look forward to a reply.

On S= un, 9 Aug 2026 at 21:42, Murch <murch@murch.one> wrote:
Hello Greg,

BIP=E2=80= =AF110 failed to achieve adoption in both phases of its deployment
attempt. It got just shy of 2.5% of blocks signaling readiness in the <= /div>
latest signaling period, and since RDTS nodes mandated signaling= , RDTS
nodes relegated themselves to a chain that only found tw= o blocks, while
the Bitcoin blockchain grew by 134 blocks. The = sole block author on the
RDTS chaintip has since announced that= they have ceased mining on the
stalled chaintip.
While it=E2=80=99s your choice to remain on the stalled chain= tip or to throw-in
with the hard fork that is now being discuss= ed, it=E2=80=99s clear that the
Bitcoin network rejected the so= ft fork. The minority hashrate chaintip
therefore constitutes a= forkcoin. Altcoins are not on-topic for the BIPs
repository, a= nd therefore, BIP110 should be advanced from Deployed to
Closed= as it is obsolete.

Murch

<= div> On 2026-08-09 11:36, Greg Tonoski wrote:
> Objection. Th= e Bitcoin Improvement Proposal 110 (BIP-110 Reduced Data
> T= emporary Softfork) has been activated. There are two blocks with the
=
> bit 4 signal (block height 961633) and the estimated 18 000 full= y
> validating nodes in the network. I keep running such a n= ode and
> accepting payments even if time interval between b= locks is temporarily
> longer until the next difficulty adju= stment.
>
> On Sun, 9 Aug 2026 at 20:07, Jon A= tack <jonnyata= ck@gmail.com
> <mailto:jonnyatack@gmail.com>> wrote:
>
>=C2=A0 =C2=A0 =C2=A0Hello list,
>
>=C2=A0 =C2=A0 =C2=A0I'd like to propose marking BIP 110= =C2=A0Reduced Data Temporary Softfork
>=C2=A0 =C2=A0 =C2=A0as= closed, following the chain split yesterday during its mandatory
>=C2=A0 =C2=A0 =C2=A0signaling period, when its chain began rejecting = as invalid all
>=C2=A0 =C2=A0 =C2=A0blocks that did not signa= l bit 4 and mining and block production
>=C2=A0 =C2=A0 =C2=A0= stalled on the BIP 110 chain.
>
>=C2=A0 =C2=A0= =C2=A0Per BIP 3, a BIP may evolve from Deployed to Closed when it is no
>=C2=A0 =C2=A0 =C2=A0longer in active use. Any community member= may initiate this status
>=C2=A0 =C2=A0 =C2=A0update by anno= uncing it to the mailing list,=C2=A0and proceed if no
>=C2=A0= =C2=A0 =C2=A0objections have been raised for four weeks. BIPs are not dele= ted;
>=C2=A0 =C2=A0 =C2=A0they are retained for historical/ed= ucational interest after being
>=C2=A0 =C2=A0 =C2=A0updated t= o Closed.
>
>=C2=A0 =C2=A0 =C2=A0Regards,
>=C2=A0 =C2=A0 =C2=A0Jon
>
>=C2=A0 = =C2=A0 =C2=A0--
>=C2=A0 =C2=A0 =C2=A0You received this messa= ge because you are subscribed to the Google
>=C2=A0 =C2=A0 = =C2=A0Groups "Bitcoin Development Mailing List" group.
= >=C2=A0 =C2=A0 =C2=A0To unsubscribe from this group and stop receiving = emails from it,
>=C2=A0 =C2=A0 =C2=A0send an email to bit= coindev+unsubscribe@googlegroups.com
>=C2=A0 =C2=A0 =C2= =A0<mailto:bitcoindev+unsubscribe@googlegroups.com>.
>=C2=A0 =C2=A0 =C2=A0To view this discussion visit https://g= roups.google.com/d/msgid/
>=C2=A0 =C2=A0 =C2=A0bitcoindev= /cf801753-e5b1-46bf-a0ae-9d88a0624829n%40googlegroups.com
>= =C2=A0 =C2=A0 =C2=A0a0ae-9d88a0624829n%40googlegroups.com?
&= gt;=C2=A0 =C2=A0 =C2=A0utm_medium=3Demail&utm_source=3Dfooter>.
>
> --
> You received this message = because you are subscribed to the Google
> Groups "Bitc= oin Development Mailing List" group.
> To unsubscribe fr= om this group and stop receiving emails from it, send
&g= t; To view this discussion visit https://groups.google.com/d/msgid= /
> bitcoindev/CAMHHROy%3DNNoaRc828xp_Qr-
&g= t; GJqoDguTrowfBKsk0XuYsgaOhSg%40mail.gmail.com <https://groups.googl= e.com/
> d/msgid/bitcoindev/CAMHHROy%3DNNoaRc828xp_Qr- <= /div>
> GJqoDguTrowfBKsk0XuYsgaOhSg%40mail.gmail.com?
= > utm_medium=3Demail&utm_source=3Dfooter>.

=
--
You received this message because you are subscribed t= o the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, s= end an email to bitcoindev+unsubscribe@googlegroups.com.


--
You received this message because you are= subscribed to the Google Groups "Bitcoin Development Mailing List&quo= t; group.
To unsubscribe from this group and stop receiving emai= ls from it, send an email to bitcoindev+unsubscribe@googlegroups.com.=
<= div>

--
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 bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google= .com/d/msgid/bitcoindev/5911e0ad-b8f1-4cdb-bd6e-47f032c72924%40app.fastmail= .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/CACgYNOJ4MZi-rrZPAfSFTwgOMbdymQbQd8Lg%3Dis-E8f_NU_0bA%40ma= il.gmail.com.
--000000000000b072b10658b00492--