Piecrust takes a simple approach:
Keep smart-contract logic inside WASM for security and portability.
Move heavy crypto operations like hashing, ZK verification, and signatures to native host functions.
Less overhead.
Better performance.
Still deterministic across nodes.
Sometimes the best VM design is knowing what not to run inside the sandbox.
#Dusk dusk-network:native @dusk
Good evening Friend 🌅✨
Woke up thinking about something interesting this morning—
What if an airdrop was something you could only give to others, not claim for yourself?
That’s exactly what @commonsmade is doing 🔥
You only get 5 vouches and 5 slashes.
Choose carefully, because this time the airdrop is in the hands of the community.
Magic Internet Money just got more fun! 🦍💰
Who are you vouching for today?
Drop it in the comments 👇
https://t.co/fzVAWlHWQa
Not comment Good morning plzz comment this 👇👇👇👇👇👇
“Hey @commonsmade I vouch for @Shuvando
The more I look at Dusk, the more interesting Phoenix becomes.
Its nullifier system lets the network know a note was spent without revealing which note.
That’s the part I like: privacy without giving up verification.
Dusk isn’t trying to hide everything — just reveal what the network actually needs to know.
@DuskFoundation #DUSK
Most people see @DuskFoundation as just another privacy chain.
I think the bigger idea is privacy that still works with regulated finance.
Phoenix gives notes fresh one-time keys, making repeated payments harder to link. The view key can still reveal what matters without giving spending power.
That balance between privacy, selective disclosure and settlement is what makes dusk-network:native interesting.
#DUSK