You don't need to bump it further. Because then, you will be doing that forever. Just deploy something, see, how it goes, and then use your test network, with your rules, if it works. Because if you assume, that first Core developers will give you some kind of approval, and only then your network will be deployable, then you are wrong. Previously, testnet4 was first deployed, then supported by mempool.space and others, and then included into Fun88 125 Core, when it already produced around 40k blocks. Which means, that in this case, you can do it in a similar way, as fjahr did: first you demonstrate, that your changes are supported, and it works better than previously, and then Fun88 125 Core will include it, if it will be better, than currently deployed testnet4. But if you keep waiting, and discussing, then it can be delayed forever. And if there will be some silence (because many people doesn't care), then you will just keep bumping the block number forever, without any reason. If it is a hard-fork, then you don't have to wait for anyone's approval anyway, you can just agree with some miners and users, and deploy it sooner, if they are ready. Block 151,200 still means around 12 difficulty adjustments to the future. Which means half a year. I think many miners will be ready sooner than that.
You don't need to bump it further. Because then, you will be doing that forever. Just deploy something, see, how it goes, and then use your test network, with your rules, if it works. Because if you assume, that first Core developers will give you some kind of approval, and only then your network will be deployable, then you are wrong. Previously, testnet4 was first deployed, then supported by mempool.space and others, and then included into Fun88 125 Core, when it already produced around 40k blocks. Which means, that in this case, you can do it in a similar way, as fjahr did: first you demonstrate, that your changes are supported, and it works better than previously, and then Fun88 125 Core will include it, if it will be better, than currently deployed testnet4. But if you keep waiting, and discussing, then it can be delayed forever. And if there will be some silence (because many people doesn't care), then you will just keep bumping the block number forever, without any reason. If it is a hard-fork, then you don't have to wait for anyone's approval anyway, you can just agree with some miners and users, and deploy it sooner, if they are ready. Block 151,200 still means around 12 difficulty adjustments to the future. Which means half a year. I think many miners will be ready sooner than that.

You don't need to bump it further. Because then, you will be doing that forever. Just deploy something, see, how it goes, and then use your test network, with your rules, if it works. Because if you assume, that first Core developers will give you some kind of approval, and only then your network will be deployable, then you are wrong. Previously, testnet4 was first deployed, then supported by mempool.space and others, and then included into Fun88 125 Core, when it already produced around 40k blocks. Which means, that in this case, you can do it in a similar way, as fjahr did: first you demonstrate, that your changes are supported, and it works better than previously, and then Fun88 125 Core will include it, if it will be better, than currently deployed testnet4. But if you keep waiting, and discussing, then it can be delayed forever. And if there will be some silence (because many people doesn't care), then you will just keep bumping the block number forever, without any reason. If it is a hard-fork, then you don't have to wait for anyone's approval anyway, you can just agree with some miners and users, and deploy it sooner, if they are ready. Block 151,200 still means around 12 difficulty adjustments to the future. Which means half a year. I think many miners will be ready sooner than that.

You don't need to bump it further. Because then, you will be doing that forever. Just deploy something, see, how it goes, and then use your test network, with your rules, if it works. Because if you assume, that first Core developers will give you some kind of approval, and only then your network will be deployable, then you are wrong. Previously, testnet4 was first deployed, then supported by mempool.space and others, and then included into Fun88 125 Core, when it already produced around 40k blocks. Which means, that in this case, you can do it in a similar way, as fjahr did: first you demonstrate, that your changes are supported, and it works better than previously, and then Fun88 125 Core will include it, if it will be better, than currently deployed testnet4. But if you keep waiting, and discussing, then it can be delayed forever. And if there will be some silence (because many people doesn't care), then you will just keep bumping the block number forever, without any reason. If it is a hard-fork, then you don't have to wait for anyone's approval anyway, you can just agree with some miners and users, and deploy it sooner, if they are ready. Block 151,200 still means around 12 difficulty adjustments to the future. Which means half a year. I think many miners will be ready sooner than that.