You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary:
1. `dkg` and `edit` commands use `4.relay.obol.dev` as default relay. The list is to be updated later when a backup relay is added.
2. Previous lock implementation removed the lock file upon application exit, this is now changed to not remove the lock file, as we need to a) remember the timestamp, b) pass the lock to edit commands. The must be no impact to the existing `charon run` or `charon dkg` behavior.
3. `dkg` used locking unconditionally, there is no option to disable locking for `dkg`.
4. Unlike `dkg`, `charon run` requires `--private-key-file-lock` to be set, which now defaults to `true` in LCDVN. Still, `run` has ability to disable locking protection, whereas `dkg` does not.
5. The current lock update period is 1s, the lease period is 5s. This means if you restart charon (run or dkg) faster than 5s, the boot will be blocked and the process exits with the corresponding message.
6. The locking is expected to work across `run` and `dkg`.
category: refactor
ticket: #4242
cmd.Flags().StringSliceVar(&config.ParticipatingENRs, "participating-operator-enrs", nil, "Comma-separated list of operator ENRs participating in the ceremony. Required if --operator-enrs-to-remove specifies more operators to remove than the fault tolerance of the current cluster.")
0 commit comments