| Safe Haskell | None |
|---|---|
| Language | Haskell2010 |
Cardano.Tools.Credentials
Description
The forging credentials, as the consensus layer wants them.
Which files a tool was pointed at comes from cardano-config, as ordinary
node command-line options, and decoding them is cardano-keys's job. Left
for here is the step that produces consensus types: mapping the key material
onto ByronLeaderCredentials and ShelleyLeaderCredentials.
Synopsis
- data LeaderCredentials = LeaderCredentials {
- byronLeaderCredentials ∷ Maybe ByronLeaderCredentials
- shelleyLeaderCredentials ∷ [ShelleyLeaderCredentials StandardCrypto]
- readLeaderCredentials ∷ Config → Credentials → IO (Either String LeaderCredentials)
Documentation
data LeaderCredentials Source #
The credentials a Cardano protocol forges with: at most one Byron-era set, and any number of Shelley-based ones.
Constructors
| LeaderCredentials | |
Fields
| |
readLeaderCredentials ∷ Config → Credentials → IO (Either String LeaderCredentials) Source #
Read the credential files named on the command line and map them onto the consensus leader credentials.
As in the node, the Shelley-based credentials are the sum of what the
individual --shelley-* options name and what the bulk credentials file
holds. Supplying none is not an error; it yields no forgers.
The Byron genesis is needed because a Byron delegation certificate has to be issued by one of its genesis keys.