#dusk I have been looking at Dusk’s cryptography work again, and the part that caught my attention is how the team is still maintaining its curve infrastructure rather than treating it as finished work.

The Dusk curves repository, which wraps the project’s curve implementations, was updated as recently as June 8, 2026. That matters because BLS12-381 sits underneath several parts of Dusk’s proving and cryptographic stack.

I have been looking at this more closely because Dusk is not using BLS12-381 as some isolated library. Its PLONK implementation is built over BLS12-381, with KZG commitments and custom gates for its proving system. The project also continues to describe that library as unstable and says more testing and analysis are encouraged.

That part feels more interesting to me than another partnership announcement. Cryptography libraries are easy to ignore when everything works. But once they sit underneath proofs, signatures and private transactions, small implementation details become important.

I am not sure what’s going on with broader ecosystem attention lately. It feels quiet. Still, seeing active work around the core cryptographic layer makes me think the team is focused more on infrastructure than noise right now. @Dusk
$DUSK