🚨 JUST IN:
ईरान के सुप्रीम लीडर आयतुल्लाह अली ख़ामेनेई ने राष्ट्रपति डोनाल��ड ट्रंप के खिलाफ कड़ा बयान दिया।
ख़ामेनेई ने कहा:
“मैं अमेरिका के नेताओं को स्पष्ट कर दूँ — ‘अमेरिका की मौत’ का मतलब अमेरिकी जनता से नहीं है, बल्कि ट्रंप और उनकी टीम से है।”
#Iran #BreakingNews
To everyone who supported me — THANK YOU ❤️🙏
Your support, trust and encouragement mean more than you know.
I truly appreciate every single one of you. 🫶#9😎 @DuskFoundation
Much love & respect. ❤️
@Usama80777611@EleNaincy65175 Mirza Mustafa Qaiser
Privacy and compliance get treated as a tradeoff more often than not — the more you hide, the less a regulator can verify, and the more you disclose, the less privacy is actually left. Dusk's design doesn't start @DuskFoundation#dusk dusk-network:native
Native issuance is different again the asset itself is created and managed on-chain so issuance transfers servicing and settlement happen around the ledger instead of using a token as a wrapper over a separate system of record.
#dusk@DuskFoundation dusk-network:native
Every blockchain has to solve a boring problem before it can solve an exciting one: how do blocks, transactions, and votes actually reach every node without flooding the network.
@DuskFoundation#dusk dusk-network:native
@AdexZendaya@DuskFoundation Fair point 👀 But now I’m curious — if you had to choose, would you prioritize privacy or verifiability first in a regulated market?
Privacy alone just hides data — useful, but incomplete for a regulated market where someone still needs to verify a transaction happened correctly. Access controls alone just gate who can act — useful dusk-network:native @DuskFoundation#dusk
Groth16 and PLONK are both proof systems but different one Groth16 verified through one host function PLONK through another exposed as genuinely separate operations rather than one unified verify proof call.
dusk-network:native #dusk@DuskFoundation
i've noticed something about myself whenever the crypto market starts moving fast.
when everything turns green, suddenly doing nothing feels like the wrong decision.
i start thinking:
"what if it keeps going up without me?"
and that's usually when FOMO gets loudest.
funny thing is, one sharp pullback can completely flip the emotion.
now it's:
"why did i buy so quickly?" 😅
same market. same chart.
completely different feeling.
that's probably one of the biggest lessons volatility has taught me.
the difficult part isn't always reading where the market might go next.
sometimes it's recognizing when the chart has started making the decision for me.
so i'm trying to get better at slowing that process down.
what actually caused the move?
is there something fundamental behind it, or am i reacting because everyone on my timeline suddenly sounds bullish?
how much risk am i genuinely comfortable taking if the price moves the other way?
i don't need to catch every green candle.
and every red candle doesn't automatically mean something is broken.
sometimes doing more research and waiting until i understand what i'm looking at is a decision too.
i'd rather miss part of a pump than keep making decisions because FOMO convinced me there was no time to think.
still learning.
still researching.
still trying to make fewer emotional decisions.
DYOR.
Educational only, not financial advice.
Instead of treating the network like a flat group where every node keeps broadcasting to nearby peers, messages can move through selected peers as they travel across the network.
@DuskFoundation#dusk dusk-network:native
Now I see two separate protocols doing parallel jobs Same category of problem Two different environments needing their own answer That distinction changed how I read the whole application layer now @DuskFoundation dusk-network:native #dusk
I don't need either of those things for the hypothetical project. That's really what decided it — not which environment is more advanced, just which one actually matches what I'd be building.
@DuskFoundation dusk-network:native #dusk
The contract is the thing you call and execute against. The protocol defines the rules and structure that contract operates within.
I'd already run into a similar distinction with Zedger.
@DuskFoundation dusk-network:native #dusk