IntersectMBO / IntersectMBO/cardano-base
Move all algorithms designed for testing into `testlib`
- Dominant language
- Haskell
- Stars
- 105
- Forks
- 54
- Avg merge
- 9d 2h
- Merged PRs (30d)
- 4
Description
Blocked by #641
There are a whole bunch of Crypto algorithms that are not designed to be used in production and exist for testing purposes only. Precisely because of their purpose they need to be moved into `cardano-crypto-class:testlib`:
* `Cardano.Crypto.Hash.NeverUsed`
* `Cardano.Crypto.Hash.Short`
* `Cardano.Crypto.KES.Mock`
* `Cardano.Crypto.KES.NeverUsed`
* `Cardano.Crypto.KES.Simple`
* `Cardano.Crypto.DSIGN.Mock`
* `Cardano.Crypto.DSIGN.NeverUsed`
* `Cardano.Crypto.VRF.Mock`
* `Cardano.Crypto.VRF.NeverUsed`
* `Cardano.Crypto.VRF.Simple`
Contributor guide
Research direction
Start by reading the dependency noted in #641, then inspect the listed Cardano.Crypto.Hash, KES, DSIGN, and VRF modules in cardano-crypto-class. Confirm how testlib is structured and track each named algorithm through its package references. Done means all listed testing-only algorithms are moved into testlib without leaving production-facing copies or broken references.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- cryptography
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100