Skip to content

Improve merge UX by removing --merge and adding preparedness indicators #3260

Closed
@michaelsproul

Description

Description

Here's a plan to improve merge UX:

  • deprecate the --merge flag, by enabling everything it does currently by default
  • clean up the logs for merge-related functionality so that:
    • if a Bellatrix epoch is set, we log loudly about the absence of EE endpoints, suggested fee recipients, etc
    • if no Bellatrix epoch is set, we do not log loudly about the absence of merge-related config (this might involve disabling some services that were previously enabled by the --merge flag)
  • add an HTTP endpoint and/or routine log message to reassure users that their node is "merge ready", which checks the presence of all necessary flags

Metadata

Assignees

No one assigned

    Labels

    UX-and-logsbellatrixRequired to support the Bellatrix Upgradev2.4.0Required for releasing v2.4.0

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions