Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Dynamic block forging for the P2P mode #4024

Closed
wants to merge 4 commits into from
Closed

Dynamic block forging for the P2P mode #4024

wants to merge 4 commits into from

Commits on Jun 30, 2023

  1. Update ouroboros-consensus and cardano-api 

    Make code type check
    @bolt12
    bolt12 committed Jun 30, 2023
    Configuration menu
    Copy the full SHA
    90b8a2b View commit details
    Browse the repository at this point in the history

  2. Set initial block forging

    @bolt12
    bolt12 committed Jun 30, 2023
    Configuration menu
    Copy the full SHA
    65a3737 View commit details
    Browse the repository at this point in the history

  3. Moved UseLedger type to avoid circular imports 

    - The moving of UseLedger was needed in order to import `Cardano.Node.Protocol (ProtocolInstantiationError)`
- Added new constructors to Startup Tracer
    @bolt12
    bolt12 committed Jun 30, 2023
    Configuration menu
    Copy the full SHA
    ef82613 View commit details
    Browse the repository at this point in the history

  4. Update block forging configuration on SIGHUP 

    Block Forging can be enabled/disabled through SIGHUP signal. Sending
such a signal will trigger the node to read the block forging credential
files. Since the credential files are passed via CLI flags one can not
remove them without restarting the node. For this effect, in order for
one to be able to disable block forging, moving/renaming/deleting the
file at the specified path (for the credential flags) and then sending
the SIGHUP signal is what needs to be done. The code will detect that
the specified files do not exist and it will disable block forging,
while tracing the appropriate log messages.

In case one wants to start a block producing node (i.e. passing the
credentials in the respective flags) but doesn't want it to actually
behave as a BP, there's a new `--start-as-non-producing-node` flag that
will run the node with credentials as a normal node. However on SIGHUP
it will read the credential files and start forging.

Refactor code to accomodate the changes

Added EnabledBlockForging type

Co-authored-by: Marcin Szamotulski <coot@coot.me>
    @bolt12 @coot
    bolt12 and coot committed Jun 30, 2023
    Configuration menu
    Copy the full SHA
    9350e00 View commit details
    Browse the repository at this point in the history