Fields

• unConfigPath ∷ FilePath
   

Fields

• unDB ∷ FilePath
   

Fields

• unGenesisFile ∷ FilePath
   

Fields

• unMaxConcurrencyBulkSync ∷ Word
   

Fields

• unMaxConcurrencyDeadline ∷ Word
   

Fields

• byronCertFile ∷ !(Maybe FilePath)
   
• byronKeyFile ∷ !(Maybe FilePath)
   
• shelleyKESFile ∷ !(Maybe FilePath)
   
• shelleyVRFFile ∷ !(Maybe FilePath)
   
• shelleyCertFile ∷ !(Maybe FilePath)
   
• shelleyBulkCredsFile ∷ !(Maybe FilePath)
   

Fields

• npcAlonzoGenesisFile ∷ !GenesisFile
   
• npcAlonzoGenesisFileHash ∷ !(Maybe GenesisHash)
   

Fields

• npcByronGenesisFile ∷ !GenesisFile
   
• npcByronGenesisFileHash ∷ !(Maybe GenesisHash)
   
• npcByronReqNetworkMagic ∷ !RequiresNetworkMagic
   
• npcByronPbftSignatureThresh ∷ !(Maybe Double)
   
• npcByronApplicationName ∷ !ApplicationName

  Update application name.

• npcByronApplicationVersion ∷ !NumSoftwareVersion

  Application (ie software) version.

• npcByronSupportedProtocolVersionMajor ∷ !Word16

  These declare the version of the protocol that the node is prepared to run. This is usually the version of the protocol in use on the chain now, but during protocol updates this version will be the one that we declare that we are ready to move to. This is the endorsement mechanism for determining when enough block producers are ready to move to the next version.

• npcByronSupportedProtocolVersionMinor ∷ !Word16
   
• npcByronSupportedProtocolVersionAlt ∷ !Word8
   

Fields

• npcConwayGenesisFile ∷ !GenesisFile
   
• npcConwayGenesisFileHash ∷ !(Maybe GenesisHash)
   

Fields

• npcTestEnableDevelopmentHardForkEras ∷ Bool

  During the development and integration of new eras we wish to be able to test the hard fork transition into the new era, but we do not wish to generally have the node advertise that it understands the new era. Avoiding advertising new development eras until they are ready makes it practical to include new not-yet-ready eras into the main release version of the node without the danger that operators on the mainnet will prematurely advertise that their nodes are capable of crossing the next hard fork.

  It should always remain at the default of false for nodes running on the mainnet.

  This flag should be set to true for nodes taking part in testnets for testing the new era.

• npcTestShelleyHardForkAtEpoch ∷ Maybe EpochNo

  For testing purposes we support specifying that the hard fork happens at an exact epoch number (ie the first epoch of the new era).

  Obviously if this is used, all the nodes in the test cluster must be configured the same, or they will disagree.

• npcTestShelleyHardForkAtVersion ∷ Maybe Word

  For testing purposes we support specifying that the hard fork happens at a given major protocol version. For example this can be used to cause the Shelley hard fork to occur at the transition from protocol version 0 to version 1 (rather than the default of from 1 to 2) which can make the test setup simpler.

  Obviously if this is used, all the nodes in the test cluster must be configured the same, or they will disagree.

• npcTestAllegraHardForkAtEpoch ∷ Maybe EpochNo

  For testing purposes we support specifying that the hard fork happens at an exact epoch number (ie the first epoch of the new era).

  Obviously if this is used, all the nodes in the test cluster must be configured the same, or they will disagree.

• npcTestAllegraHardForkAtVersion ∷ Maybe Word

  For testing purposes we support specifying that the hard fork happens at a given major protocol version.

  Obviously if this is used, all the nodes in the test cluster must be configured the same, or they will disagree.

• npcTestMaryHardForkAtEpoch ∷ Maybe EpochNo

  For testing purposes we support specifying that the hard fork happens at an exact epoch number (ie the first epoch of the new era).

  Obviously if this is used, all the nodes in the test cluster must be configured the same, or they will disagree.

• npcTestMaryHardForkAtVersion ∷ Maybe Word

  For testing purposes we support specifying that the hard fork happens at a given major protocol version.

  Obviously if this is used, all the nodes in the test cluster must be configured the same, or they will disagree.

• npcTestAlonzoHardForkAtEpoch ∷ Maybe EpochNo

  For testing purposes we support specifying that the hard fork happens at an exact epoch number (ie the first epoch of the new era).

  Obviously if this is used, all the nodes in the test cluster must be configured the same, or they will disagree.

• npcTestAlonzoHardForkAtVersion ∷ Maybe Word

  For testing purposes we support specifying that the hard fork happens at a given major protocol version.

  Obviously if this is used, all the nodes in the test cluster must be configured the same, or they will disagree.

• npcTestBabbageHardForkAtEpoch ∷ Maybe EpochNo
   
• npcTestBabbageHardForkAtVersion ∷ Maybe Word

  For testing purposes we support specifying that the hard fork happens at a given major protocol version.

  Obviously if this is used, all the nodes in the test cluster must be configured the same, or they will disagree.

• npcTestConwayHardForkAtEpoch ∷ Maybe EpochNo
   
• npcTestConwayHardForkAtVersion ∷ Maybe Word

  For testing purposes we support specifying that the hard fork happens at a given major protocol version.

  Obviously if this is used, all the nodes in the test cluster must be configured the same, or they will disagree.

Fields

• npcShelleyGenesisFile ∷ !GenesisFile
   
• npcShelleyGenesisFileHash ∷ !(Maybe GenesisHash)