Closed
Milestone
Nov 24, 2021–Mar 31, 2022
Tenderbake Activation
The main objective is to ensure Tenderbake can be safely activated. Normally this milestone ends once we observe that Tenderbake has been activated and works as expected.
"Maintenance" tasks:
-
test the migration - fix any appearing issues related to Tenderbake (observed for instance on the testnet), and not covered by other crew (like "mempool")
- resolve other remaining issues, raised during the previous milestone (which are not critical), see the list of issues or the NL analogue milestone; this includes improving the code quality overall, both in the protocol, and in the baker; do this in the order of their priority
- check coverage and improve if necessary
- improve documentation
- assists developers with Tenderbake-related issues, if needed
-
new blog post, before injection - communicate with indexer and block explorer developers/maintainers, so that they smoothly adapt their tools to Tenderbake
Consensus-related tasks for protocol J:
- Everywhere: reduce
preserved_cycles
(nomadic-labs/tezos#351) - Proto: simplify activity rules, if possible
- Baker: fix remaining issues (see again NL milestone);remove TODOs and FIXMEs (34 occurrences)
- Baker: use deterministic nonces