One thing I always check with infrastructure projects is whether development continues when the timeline gets quiet.
Dusk’s public GitHub shows recent activity across PLONK, ZK tooling, Piecrust, DuskEVM, Schnorr signatures, Rusk and the wallet. A repository update alone does not prove adoption, but it shows work is continuing across several parts of the stack.
That matters because Dusk is tackling a difficult market problem: giving regulated assets transparency where useful, privacy where necessary, controlled disclosure for authorized parties and deterministic onchain settlement.
The real test will be turning these technical pieces into infrastructure that institutions and investors can actually use. For now, this is the kind of steady progress I’ll keep watching.
Which part of Dusk interests you most?
#dusk $DUSK @Dusk
Dusk’s public GitHub shows recent activity across PLONK, ZK tooling, Piecrust, DuskEVM, Schnorr signatures, Rusk and the wallet. A repository update alone does not prove adoption, but it shows work is continuing across several parts of the stack.
That matters because Dusk is tackling a difficult market problem: giving regulated assets transparency where useful, privacy where necessary, controlled disclosure for authorized parties and deterministic onchain settlement.
The real test will be turning these technical pieces into infrastructure that institutions and investors can actually use. For now, this is the kind of steady progress I’ll keep watching.
Which part of Dusk interests you most?
#dusk $DUSK @Dusk
Privacy and ZK tools
DuskEVM development
10 Stunde(n) übrig