Use mocked crypto for speeding up

Open
#31 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
haskell
Domain
blockchain, cryptography

Research direction

Start with Cardano.Ledger.Crypto.Crypto in libs/cardano-ledger-core/src/Cardano/Ledger/Crypto.hs and the concrete crypto types in eras/shelley/test-suite/src/Test/Cardano/Ledger/Shelley/ConcreteCryptoTypes.hs. Determine how mocked hashes could replace StandardCrypto for the emulator’s tests, then compare test speed to confirm the change improves performance.

Written by the indexing model from the issue text.

Description

enhancement 
          No, we use an instance of `Cardano.Ledger.Crypto.Crypto`, which is [`StandardCrypto`](https://github.com/IntersectMBO/cardano-ledger/blob/master/libs/cardano-ledger-core/src/Cardano/Ledger/Crypto.hs#L40-L45). By using mock hashes we can probably speed everything up a bit. Take a look [here](https://github.com/IntersectMBO/cardano-ledger/blob/master/eras/shelley/test-suite/src/Test/Cardano/Ledger/Shelley/ConcreteCryptoTypes.hs#L52-L57).

`

Originally posted by @euonymos in https://github.com/mlabs-haskell/clb/issues/24#issuecomment-2025939180

Dominant language
Haskell
Stars
10
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mlabs-haskell/clb

All issues in mlabs-haskell/clb

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.