Update tests to use dusk_curves
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
Research direction
Start by locating the dusk-bls12-381 dependency in the test configuration and inspecting how the test base uses it. Replace that test dependency with dusk_curves, then run the test suite to confirm the tests compile and pass without changing crate code.
Written by the indexing model from the issue text.
Description
Summary
The whole Dusk stack is moving to use dusk_curves instead of bls12_381. Safe doesn't use it as part of the crate code, but yes as part of the test base. We should update the dependency dusk-bls12-381 to be dusk_curves instead.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 1
- Avg merge
- 21h 40m
- Merged PRs (30d)
- 6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100