This post is a supplement to those above, providing a high level overview of the configuration in each proposal (but with a focus on the salient details). I’ve built a rough and ready tool for doing this, where different values for each field are assigned colours making it easy to spot differences at a distance.
As we can see sev_enabled (middle turquoise) is not set explicitly, unlike existing application subnets. However it’s an optional field so this will have the same effect (all other subnets have this explicitly set to false). While this is as specified by the newly adopted IC Target Topology for the non-US new subnets, it is misaligned with regard to the IC Target Topology specification for the US subnet (it should be configured with the SEV feature). That being said, no subnets are currently configured with this feature (my understanding is that it’s still in the works).
Note that the dark blue discrepancies on the left with regard to dkg_dealings_per_block are due to [] having been used instead of null in a few update config proposals (same effect though).
Other than this (and the max_number_of_canisters point raised by timk11) we can see that the subnets are configured consistently with other application subnets. It’s also worth noting that deprecated fields are explicitly included in the config payload, but this is required.