I'll be precise:
Let's imagine 40% activate nprofile1qqsw3p5pela795rxxff34kgfafsaawhnkqp8ehmgm2my49dgx9fjclcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpzamhxue69uhhyetvv9ujucm0wfc82mfwvdhk6tcuxu0h5 (nprofile…u0h5)'s soft fork in 2026. The remaining 60% just keep doing nothing, i.e. they keep running their existing Core and Knots nodes, like Core 0.21 or Core 30 or Knots 29. Let's call the 60% the "Taproot" hashrate
Also, observe that many current blocks are incompatible with the RDTS rules, for example having OP_RETURNs greater than 83 bytes
The 60% running taproot will get a block roughly every 17 minutes, while the RDTS will find a block roughly every 25 minutes
The first hour or so could be interesting, and maybe Taproot miners will find a couple of blocks that satisfy the RDTS rules. But that won't last long, the Taproot chain will soon include blocks that are rejected by the RDTS hashrate
The chain will split, where the majority hash rate will ignore the RDTS chain because it doesn't have enough Proof of Work, and the RDTS will ignore the Taproot chain because it has RDTS-incompatible blocks
So basically, Luke Dashjr (nprofile…jrgs) was wrong at least three times in this one paragraph X post:
https://xcancel.com/LukeDashjr/status/1983145119176945910