Open
Milestone
Adaptive issuance - Backlog
This milestone gathers Adaptive issuance backlog, ie thing that should be done "later".
Mandatory known for Q
-
Backpost tests from alpha to Paris (2 days) !13573 (merged) - Needs to be done before removing feature flags, since this will make tests no longer backward compatible
-
Tests: explicitly check expected errors !13504 (merged) -
Make sure that the documentation is up to date for Q, e.g. backport !13105 (merged) (2 days) -
Documentation improvements (3 days) -
Forward port AI doc from Paris to Alpha !13695 (merged) -
Clarify BLOCKS_PER_CYCLEand remove autostaking line !13730 (merged) -
Fix block time for Paris !13730 (merged)
-
Mandatory TBD for Q
-
Sort through issues to make sure we don't miss anything important (2 days) -
List important use cases, make sure they appear in the tests (3 days)
Do as soon as possible, but not blocking for Q snapshotting (because lib_protocol is not affected)
Documentation
See #7262
Tests (need to pass CI)
-
Improve error checking in tests (2 days) -
#7153 Test all staking operations on last block of a cycle -
#7096 (closed) Make deactivation checks more accurate !12678 (merged) -
#5653 (closed) Proto/test/token: test total supply update !13863 (merged)
After protocol Q
Clean up
-
#5604 AI: handle storage of computed rewards more cleanly -
#7369 Plugin: clean up RPC registration -
See other issues with label "code quality" -
Improve documentation in the code (3 days)
Dead-code removal
-
Remove feature flags and AI activation cycle check (2 days) -
Quick clean up -
Remove all O -> P stitching helpers (hours) -
Remove deprecated storage tables that are straightforward to remove (hours)
-
-
Remove per-block vote (2 days) - Deprecate the command-line argument, so that it's not a breaking change
-
Remove set-deposit-limit (2 days) - See MR from Mehdi, but it will need to be updated
- Clear tables during stitching?
-
Remove auto-staking code (hours) - Prerequisite: feature flags have been removed
-
Complex deprecated storage clean-up (3 days) - It's complex because iterating over all contracts at migration time would take several minutes
-
Offline, gather the list of keys for which there is data to remove -
on mainnet -
on ghostnet
-
-
clean-up code that iterates over (only) these keys at migration time
Test quality
-
#7362 (closed) AI/test/deactivation: use tolerated_inactivity_period proto constant
Potential UX improvements
-
allows proper baker exit in two step (Exit-unstake ; finalise) - The "command" should on top of unstaking everything, prevent the rewards to be distributed to bakers frozen-deposit.
Loading
Loading
Loading
Loading