Skip to content
Snippets Groups Projects

[Version-unspecific] Only halt after THOR height specified by HaltSigning and HaltSigning%s Mimir keys, like all other Halt keys

Merged Multipartite requested to merge Multi/HaltSigning-after-THOR-height into develop
All threads resolved!

[Version unspecific]

Intended to close #2047 (closed)
'Bifrost should respect future height in HaltSigning'.

My current impression is that no versioning is needed for this.
(No observation consensus issues, nor predicted switchover-timing usage.)

My thought process code references for referring to the THOR height,
in that every other Halt key does so and HaltSigning has to (since it can't be set chain-specifically),
are here:
#2047 (comment 2083042237)

As always, feedback is welcome!

Edited by Multipartite

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Asmund THORSec approved this merge request

    approved this merge request

  • Multipartite added 11 commits

    added 11 commits

    • dee92049...c6ee6d76 - 10 commits from branch develop
    • b4ad67c6 - Only halt after THOR height specified by HaltSigning and HaltSigning%s Mimir...

    Compare with previous version

  • Pluto resolved all threads

    resolved all threads

  • Pluto enabled an automatic merge when all merge checks for b4ad67c6 pass

    enabled an automatic merge when all merge checks for b4ad67c6 pass

  • merged

  • Multipartite mentioned in issue #2064

    mentioned in issue #2064

  • Multipartite mentioned in merge request !3721 (merged)

    mentioned in merge request !3721 (merged)

  • Please register or sign in to reply
    Loading