Merge pull request #17 from adrem1/patch-2
removed Shelley references
removed Shelley references
cardano-cli
```
We will be told that one available subcommand is `shelley`, and typing
We will be told that one available subcommand is `node`, and typing
```text
cardano-cli shelley
cardano-cli node
```
will display available sub-subcommands, one of which is `node`. We can continue drilling down the hierarchy:
will display available sub-subcommands, one of which is `key-gen`. Typing
```text
cardano-cli shelley node
```
and learn about the sub-sub-subcommand `key-gen`. Typing
```text
cardano-cli shelley node key-gen
cardano-cli node key-gen
```
will inform us about the parameters this command takes, so we can for example generate a key-pair of offline keys and a file for the issue counter by typing
```text
cardano-cli shelley node key-gen \
cardano-cli node key-gen \
--cold-verification-key-file cold.vkey \
--cold-signing-key-file cold.skey \
--operational-certificate-issue-counter-file cold.counter
2409: Upgrade to cabal-3.4.0.0 for documentation r=newhoggy a=newhoggy Co-authored-by: John Ky <[email protected]>
Use this function to replace the common functionality of: - `unsafePartitionCoin` - `unsafePartitionTokenQuantity`
- Model a lower-level "weakly-typed" metadata, which is essentially just a JSON object. - Model a level above this layer that translates from the "weakly-typed" metadata into a "strongly-typed" metadata. - Use the "weakly-typed" metadata type in all lower-level areas: - The database/storage layer - The server layer - The webhook layer - All these layers don't care much about what form the metadata is in, and so the weak type is more appropriate here. - Use the "strongly-typed" metadata type in the PR validator. - This is the only area where we want the stronger types. - Shuffle tests around accordingly, write new tests. - Cleanup the codebase a bit.
2409: Upgrade to cabal-3.4.0.0 for documentation r=newhoggy a=newhoggy Co-authored-by: John Ky <[email protected]>