Update changelog for 2020.11.0. (#3307)

CHANGELOG.md

@@ -1,50 +1,38 @@
 # Changelog
 
-## Timeline to Mainnet
-
-The journey to launching the beacon chain is in its final stage with the announcement of the Eth2 deposit contract, and minimum genesis time of Tuesday, December 1, 2020 12:00:00 PM UTC.
-
-Teku is ready to be a part of the Mainnet launch, and we're coordinating with other client teams to make the launch a success. Here's a timeline of key events, including the Teku releases that will lead up to Mainnet launch.
-
-**Note**: The exact genesis time depends on when enough deposits are received. If it takes longer
-to reach the minimum validators required, then the Mainnet genesis won't be set until enough 
-validators are registered.  The Mainnet chain will then start 7 days after the genesis 
-is set. There will be a Teku release within the 7 days before the Mainnet chain starts, and users 
-should ensure they upgrade to it.
-
-----------------------------------------------------------------------------------------------------
-Event                            | Scheduled Date       | Notes
----------------------------------|----------------------|-------------------------------------------
-Teku 0.12.14 release             | 11 November          | Includes the Mainnet ready specification available with the `--network mainnet` command line option.
-Teku 20.11.0-RC1 release         | 18 November          | Makes `mainnet` the default network. Legacy options and APIs will be removed, see [20.11.0-RC1 Breaking Changes](#20.11.0-RC1)
-Earliest date for Mainnet genesis state to be set | 24 November | If enough deposits are received by this time, the Mainnet genesis state will be generated. Otherwise this will be delayed until enough deposits are received
-Teku 20.11.0 release             | Around 26 November   | First full production-ready release of Teku.
-Earliest date for Mainnet launch | 1 December   | This will be delayed if required deposit amounts are not received by 24 November. The chain will always launch 7 days after the genesis state is set. 
-
-### Mainnet Genesis Release
+## Upcoming Breaking Changes
 
-Regardless of the Mainnet launch date, users should expect a Teku release in the week leading up to 
-the chain starting. It is important to upgrade your nodes to this version before the chain starts to
-ensure a smooth launch.
+- Docker images are now being published to `consensys/teku`. The `pegasys/teku` images will continue to be updated for the next few releases but please update your configuration to use `consensys/teku`.
+- `--validators-key-files` and `--validators-key-password-files` have been replaced by `--validator-keys`. The old arguments will be removed in a future release.
 
-### CalVer Versioning
+## 20.11.0
 
-Teku will adopt the CalVer versioning convention for our production ready releases using the 
-`YY.M.patch` format. `YY` for year (20, 21, 22 etc), `M` for month (1, 2, 3, …, 11, 12) and `patch` for patch release number.
+The beacon chain is set to launch with the MainNet genesis state now set. The beacon chain will launch on 1 December 2020 at 12:00:23 UTC. 
+Teku 20.11.0 is fully production ready and has full support for the beacon chain Mainnet.
 
-The final release on the old versioning system will be 0.12.14.
+### Breaking Changes
 
-The first production-ready release will be 20.11.0.  
+- REST API endpoint `/eth/v1/beacon/pool/attestations` now accepts an array of attestations instead of a single attestation.
 
-#### Backward Compatibility Policy
+### Additions and Improvements
 
-Only versions with a 0 patch number may contain backwards incompatible changes (e.g. 20.11.0, 20.12.0 etc).
-Upcoming backwards incompatible changes will be noted in the changelog at least one month prior to being applied.
+- Full support for Eth2 MainNet. Genesis state and bootnodes are now configured as part of the `--network mainnet` option. 
+- Voluntary exits and slashings submitted via the REST API are now broadcast to the gossip network.
+- Added `/teku/v1/admin/liveness` endpoint which always returns 200 OK to be used to check if the REST API is live.
+- Added `dependent_root` field to attester and block producer duties as well as 
+  `current_duty_dependent_root` and `previous_duty_dependent_root` to the `head` events to aid validator clients in determining when duties are invalidated by changes in the chain.
+- Tightened validation of data from the beacon node in the validator client to ensure blocks and attestations from far future slots are not signed. 
 
-## Upcoming Breaking Changes
+### Bug Fixes
 
-- Docker images are now being published to `consensys/teku`. The `pegasys/teku` images will continue to be updated for the next few releases but please update your configuration to use `consensys/teku`.
-- `--validators-key-files` and `--validators-key-password-files` have been replaced by `--validator-keys`. The old arguments will be removed in a future release.
+- Fixed incorrect expected attestation metric.
+- Fixed incorrect `beacon_previous_correct_validators` metrics.
+- Fixed race condition during validator startup which could lead to duties not being performed for the first two epochs.
+- Provide a human-friendly error message when the `--network` argument is unknown.
+- Provide more human-friendly error messages when invalid options are given to the `voluntary-exit` subcommand.
+- Avoided duplicate epoch processing during block creation.
+- Reduce noise from `UNKNOWN_PARENT` errors when syncing.
+- Drop discovery session when a malformed `authheadermessage` packet is received.
 
 ## 20.11.0-RC2