#dusk I have been looking at $DUSK from that angle especially its Merkle architecture and the use of Poseidon with zero-knowledge opening proofs.
The opportunity is interesting: privacy-preserving state commitments could make confidentiall applications more practical without removing verifiabillity.
But technical capabillity alone does not create demand. The the weakness is whether developers actually build applications that generate recurring state updates, proofs and transactions.
I have been looking at @Dusk_Foundation ’s developer activity, contract usage, proof-generation frequency, transaction growth and liquidity conditions. If those improve together I’d become more confident that the infrastructure is translating in to genuine network demand rather than simply adding an other technical feature.
#dusk $DUSK @Dusk
The opportunity is interesting: privacy-preserving state commitments could make confidentiall applications more practical without removing verifiabillity.
But technical capabillity alone does not create demand. The the weakness is whether developers actually build applications that generate recurring state updates, proofs and transactions.
I have been looking at @Dusk_Foundation ’s developer activity, contract usage, proof-generation frequency, transaction growth and liquidity conditions. If those improve together I’d become more confident that the infrastructure is translating in to genuine network demand rather than simply adding an other technical feature.
#dusk $DUSK @Dusk