Skip to content

Proto/Migration: Ghostnet specific code

Context

TL;DR; this MR introduce new Ghostnet specific stitching code during K -> L migration in order to fix its J -> K migration :-(

  • On Ghostnet, cycles are 4 time shorter (twice less blocks per cycles, twice more often) but the same VDF difficulty was set than on mainnet so it leading to an impossible challenge...
  • The user activated upgrade on Ghostnet occurred at a level which was not the end of a voting period "before itself" but should have become one given the global constant it rewrites! It completely messed up the voting logic which therefore needs a hard reboot See #3870 (closed)

Manually testing the MR

This MR introduce a tezt test that I'm not sure should be commit in octez in the end but gives the recipe for reproduction

Checklist

  • Document the interface of any function added or modified (see the coding guidelines)
  • Document any change to the user interface, including configuration parameters (see node configuration)
  • Provide automatic testing (see the testing guide).
  • For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
  • Select suitable reviewers using the Reviewers field below.
  • Select as Assignee the next person who should take action on that MR

Merge request reports

Loading