[rejected] Subnet safe mode

Proposals
1

I propose that we consider two distinct sets of requirements that subnets fall into:

  1. Unshackle the subnet owner, give him as much freedom as they need to build good stuff on the chain
  2. Limit what the subnet owner can do, to prevent rampant abuse (67, 71, 104, some people say 43, I’m sure there are many other examples)

Crucially Fish said the other day that sn64 and sn51 don’t need any more Tao to be pumped into their liquidity pools. They have more than enough… so… how about we introduce a distinction between the subnets operating modes, where:

  1. Subnets running with safe_mode = OFF can basically do whatever they want (just don’t damage the chain), but they don’t receive any Tao injections to their liquidity pools. Disable registration, change kappa to whatever you want, turn off CHK tax - no problem.
  2. Subnets running with safe_mode = ON (which is the default) are limited in such a way that they cannot abuse the position of the subnet owner to mess with the root stake validators etc
2

This has been shot down by @distributed_tensor who observed that it’d allow the owner to defraud the liquidity that was injected into the subnet before switching the subnet to unsafe mode.