Nimbus update: v1.0.12 release (Prater testnet support)
Prater's objective is to ensure that the network remains stable under a higher load than we've seen so far on mainnet. To elaborate a little, we want to make sure that the network is able to function properly with considerably more validators -- the genesis count for Prater was 210k (almost double the size of the Beacon Chain Mainnet).
How do things change with more validators? Ben Edgington provides a good explanation in his latest newsletter:
Increasing the number of validators increases the state size, increases the amount of work done to process that state, and increases the number of messages being gossipped on the network. Blocks also become fuller, which explores a new kind of constraint as clients need to optimise better for attestation inclusion.
Both Pyrmont and Prater will co-exist for the foreseeable future (we will be testing the Altair fork on Pyrmont, for example). However, in the medium term we expect Prater to replace Pyrmont.
If you're already validating with Nimbus, you should start thinking about transitioning from Pyrmont to Prater at some point over the next few weeks. However, there is no immediate rush, so please do so at your own convenience. If you're new to Nimbus then you could try starting directly with Prater.