MEER BANO
860 Публикации
MEER BANO
Crypto Educator | Market Analyst & Trader | Sharing Insights & Strategies |
Трейдер с регулярными сделками
8.5 мес.
330 подписок(и/а)
9.9K+ подписчиков(а)
1.9K+ понравилось
Посты
Все
Цитирования
Видео
Активно
PINNED
Проверено
I run a small Python script on my laptop in Islamabad that does heavy hashing for a side project, and I once tried moving it into a sandboxed environment thinking it would run just as fast since the logic didn't change. It ran noticeably slower, and until I read about Dusk's Piecrust VM I never actually understood why that happens at a technical level.
I assumed all smart contract execution inside a WASM virtual machine runs at roughly native speed, since WASM is usually marketed as near native performance.
That's not accurate for cryptographic operations specifically. Research cited in the whitepaper shows WASM execution can run 45 to 255 percent slower than native code for complex applications, mainly from virtualized memory management and extra instruction handling inside the sandbox.
That's exactly why Piecrust doesn't run things like ZK proof verification, hashing, or signature checks inside the WASM sandbox at all. It exposes host functions instead, direct native calls for operations like hash, verify_plonk, verify_groth16_bn254, verify_schnorr, and verify_bls. The contract calls out to native code for the expensive cryptographic work, then comes back into WASM for everything else. That's a deliberate architectural split, not a workaround.
What the whitepaper admits directly is that Dusk hasn't quantified actual power savings from this setup yet. So I can't tell you a real efficiency number, because Dusk itself hasn't published one.
The real test for DUSK is whether this host function approach keeps holding up as contract complexity grows on mainnet.
Has anyone benchmarked Piecrust's host function calls against pure WASM execution themselves?
@Dusk #dusk $DUSK
I assumed all smart contract execution inside a WASM virtual machine runs at roughly native speed, since WASM is usually marketed as near native performance.
That's not accurate for cryptographic operations specifically. Research cited in the whitepaper shows WASM execution can run 45 to 255 percent slower than native code for complex applications, mainly from virtualized memory management and extra instruction handling inside the sandbox.
That's exactly why Piecrust doesn't run things like ZK proof verification, hashing, or signature checks inside the WASM sandbox at all. It exposes host functions instead, direct native calls for operations like hash, verify_plonk, verify_groth16_bn254, verify_schnorr, and verify_bls. The contract calls out to native code for the expensive cryptographic work, then comes back into WASM for everything else. That's a deliberate architectural split, not a workaround.
What the whitepaper admits directly is that Dusk hasn't quantified actual power savings from this setup yet. So I can't tell you a real efficiency number, because Dusk itself hasn't published one.
The real test for DUSK is whether this host function approach keeps holding up as contract complexity grows on mainnet.
Has anyone benchmarked Piecrust's host function calls against pure WASM execution themselves?
@Dusk #dusk $DUSK
💰 One of the reason we think $BTC will drop below $45k :
2021 Top to 2026 Top : 1.8x
2022 Bottom to 2026 Top : 8.1x
Realistic Calculations :
2026 Top to Next Top : 1.4x ($175k)
2026 Bottom to Next Top : 4.1x
$44k * 4x -> $175k
$35k * 5x -> $175k
2026 Bottom Should be : $44k - $35k
And Final Top Around : $175k
$ONG $ZEC
2021 Top to 2026 Top : 1.8x
2022 Bottom to 2026 Top : 8.1x
Realistic Calculations :
2026 Top to Next Top : 1.4x ($175k)
2026 Bottom to Next Top : 4.1x
$44k * 4x -> $175k
$35k * 5x -> $175k
2026 Bottom Should be : $44k - $35k
And Final Top Around : $175k
$ONG $ZEC
Follow , repost , comment and claim red packet 🎁🎁🎁
🚀 WLD — Long Setup
Entry: 0.3968 (current market)
🎯 Target: 0.6320 (swing)
🛡️ SL: 0.3742
📈 AI narrative heating up + reclaimed HTF VAL with a breakout higher.
⚠️ Risk: 🟡 Medium — stick to the plan.
$WLD
Entry: 0.3968 (current market)
🎯 Target: 0.6320 (swing)
🛡️ SL: 0.3742
📈 AI narrative heating up + reclaimed HTF VAL with a breakout higher.
⚠️ Risk: 🟡 Medium — stick to the plan.
$WLD
I keep an old cash register receipt roll from my father's shop in Sialkot, every entry stacked one after another and nothing ever gets erased once it's printed. That's the picture I had of UTXO systems, notes just pile up chronologically and stay there. Reading Phoenix broke that assumption a bit.
Phoenix does use a UTXO structure, but calls them notes, stored in a Merkle tree rather than a flat ledger. When you spend a note, you don't delete it, you generate a nullifier instead, a value derived from the note's secret key that proves it's been spent without revealing which note in the entire tree it was. The network just tracks the list of used nullifiers. Notes physically stay in the tree forever, growing larger with every transaction, spent or not.
That detail is what actually reframed how I see this. The privacy isn't coming from hiding transactions off chain, it's coming from making every note indistinguishable from every other unspent note once a nullifier appears. Nobody, including validators, can point at the tree and say which specific leaf just got spent. Ownership and balance are proven entirely through a zero knowledge proof, so the network verifies math instead of verifying visible amounts.
What the whitepaper doesn't tell me is how tree size affects proof generation time as the note count grows over years of mainnet activity. That's a real scaling question I can't answer from the source material.
The real test for DUSK is whether Phoenix stays fast to use once the note tree gets genuinely large.
Does anyone know how large the Phoenix note tree currently is on Dusk mainnet?
@Dusk #dusk $DUSK
Phoenix does use a UTXO structure, but calls them notes, stored in a Merkle tree rather than a flat ledger. When you spend a note, you don't delete it, you generate a nullifier instead, a value derived from the note's secret key that proves it's been spent without revealing which note in the entire tree it was. The network just tracks the list of used nullifiers. Notes physically stay in the tree forever, growing larger with every transaction, spent or not.
That detail is what actually reframed how I see this. The privacy isn't coming from hiding transactions off chain, it's coming from making every note indistinguishable from every other unspent note once a nullifier appears. Nobody, including validators, can point at the tree and say which specific leaf just got spent. Ownership and balance are proven entirely through a zero knowledge proof, so the network verifies math instead of verifying visible amounts.
What the whitepaper doesn't tell me is how tree size affects proof generation time as the note count grows over years of mainnet activity. That's a real scaling question I can't answer from the source material.
The real test for DUSK is whether Phoenix stays fast to use once the note tree gets genuinely large.
Does anyone know how large the Phoenix note tree currently is on Dusk mainnet?
@Dusk #dusk $DUSK
I sent a bank transfer to a supplier in Gujranwala yesterday and the receipt showed everything, my account, his account, the exact amount, nothing hidden. I assumed Dusk being a privacy chain meant every single transaction on it worked the opposite way, everything obfuscated by default, no exceptions.
That assumption doesn't hold once you look at Moonlight. It's a fully transparent, account based model, closer to how Ethereum works than to Zcash. Every account has a public key acting as an identifier, and the network tracks a visible nonce and balance for it directly. Ownership gets proven with a straightforward digital signature, the network checks the sender has enough funds, and the nonce has to be exactly one higher than the account's current count to stop replay attacks.
What actually reframed this for me is realizing Dusk isn't a privacy chain that happens to allow transparency as an afterthought. It runs Moonlight and Phoenix side by side as two equally supported transaction models, and only Phoenix handles the obfuscated side. That means Dusk is deliberately built for a world where financial institutions need both, a public audit trail for some transactions and shielded details for others, not one universal privacy default. That's a more mature design choice than a lot of privacy coins even attempt.
What the whitepaper doesn't say is how much of actual network usage runs through Moonlight versus Phoenix in practice. I have no real transaction split to point to.
The real test for DUSK is whether institutions actually use Moonlight for the compliant side of their operations once real volume shows up.
Does anyone know the current Moonlight versus Phoenix transaction split on Dusk mainnet?@Dusk #dusk $DUSK
That assumption doesn't hold once you look at Moonlight. It's a fully transparent, account based model, closer to how Ethereum works than to Zcash. Every account has a public key acting as an identifier, and the network tracks a visible nonce and balance for it directly. Ownership gets proven with a straightforward digital signature, the network checks the sender has enough funds, and the nonce has to be exactly one higher than the account's current count to stop replay attacks.
What actually reframed this for me is realizing Dusk isn't a privacy chain that happens to allow transparency as an afterthought. It runs Moonlight and Phoenix side by side as two equally supported transaction models, and only Phoenix handles the obfuscated side. That means Dusk is deliberately built for a world where financial institutions need both, a public audit trail for some transactions and shielded details for others, not one universal privacy default. That's a more mature design choice than a lot of privacy coins even attempt.
What the whitepaper doesn't say is how much of actual network usage runs through Moonlight versus Phoenix in practice. I have no real transaction split to point to.
The real test for DUSK is whether institutions actually use Moonlight for the compliant side of their operations once real volume shows up.
Does anyone know the current Moonlight versus Phoenix transaction split on Dusk mainnet?@Dusk #dusk $DUSK
📉 $BTC LTF Update
Post-move consolidation — price is now ranging on the lower timeframe. Weekend liquidity is thin, so expect muted action.
Two key levels marked on the chart. A tap on either could trigger a sweep toward the opposite side.
🔍 Watching for a directional push once range edges are tested.
Post-move consolidation — price is now ranging on the lower timeframe. Weekend liquidity is thin, so expect muted action.
Two key levels marked on the chart. A tap on either could trigger a sweep toward the opposite side.
🔍 Watching for a directional push once range edges are tested.
My electricity meter reader in Rawalpindi got a warning notice last month for skipping our street on his rounds, nothing severe, just a formal note in his file. I assumed Dusk treats provisioner misbehavior the same flat way, one warning system, penalties scale up the same regardless of what you actually did wrong.
That's not how it works. Dusk splits faults into two clearly separate categories with completely different consequences. A minor fault, like failing to broadcast a candidate block when you were chosen as generator, results in suspension and soft slashing. A major fault, like broadcasting an invalid block, double voting, or putting out two different candidate blocks for the same iteration, triggers hard slashing instead.
The distinction that actually reframed this for me is what soft slashing versus hard slashing actually does. Soft slashing just locks a portion of your stake, which lowers your weight in future sortition rounds but doesn't destroy anything. Hard slashing straight up burns part of your stake, permanently, with the burned amount increasing based on how severe or repeated the fault is. One is a timeout. The other is a real financial loss with no way back.
What the whitepaper doesn't specify is the exact percentage or DUSK amount burned per major fault tier. Without that number I can't tell anyone how costly a specific violation actually is in real terms.
The real test for DUSK is whether hard slashing stays severe enough to actually deter double voting once stake concentration grows.
Does anyone know the real burn percentages Dusk applies for major faults?
#dusk $DUSK @Dusk
That's not how it works. Dusk splits faults into two clearly separate categories with completely different consequences. A minor fault, like failing to broadcast a candidate block when you were chosen as generator, results in suspension and soft slashing. A major fault, like broadcasting an invalid block, double voting, or putting out two different candidate blocks for the same iteration, triggers hard slashing instead.
The distinction that actually reframed this for me is what soft slashing versus hard slashing actually does. Soft slashing just locks a portion of your stake, which lowers your weight in future sortition rounds but doesn't destroy anything. Hard slashing straight up burns part of your stake, permanently, with the burned amount increasing based on how severe or repeated the fault is. One is a timeout. The other is a real financial loss with no way back.
What the whitepaper doesn't specify is the exact percentage or DUSK amount burned per major fault tier. Without that number I can't tell anyone how costly a specific violation actually is in real terms.
The real test for DUSK is whether hard slashing stays severe enough to actually deter double voting once stake concentration grows.
Does anyone know the real burn percentages Dusk applies for major faults?
#dusk $DUSK @Dusk
My tailor in Lahore splits earnings with his two apprentices on a flat percentage every single job, same cut no matter how much work the apprentices actually put in that day. I assumed Dusk's 80/10/10 block reward split worked the same way, fixed shares handed out no matter what.
Only the 10 percent to Dusk and roughly the base structure are fixed. The generator's 80 percent actually splits into two pieces, a locked in 70 percent and a variable 10 percent that depends entirely on how many votes the generator includes in the block certificate. Leave votes out, and that variable slice shrinks. Include every known vote, and the generator earns the full 80.
That detail flipped how I saw this system. It's not really an 80/10/10 split, it's a compliance incentive dressed up as a reward split. The generator is financially pushed to gather as many validator signatures as possible before finalizing a block, which directly strengthens the odds that voters actually get their own 10 percent share too. The voter reward pool is distributed based on credits held, tying back to the weighted committee system I covered before.
What the whitepaper doesn't clarify is how often generators in practice submit blocks with incomplete vote sets, whether that's rare or a real recurring behavior. I can't answer that from the source material.
The real test for DUSK is whether this incentive structure keeps generators including full vote sets once network activity scales up.
Does anyone know if Dusk publishes real generator vote inclusion rates anywhere?
#dusk $DUSK @Dusk
Only the 10 percent to Dusk and roughly the base structure are fixed. The generator's 80 percent actually splits into two pieces, a locked in 70 percent and a variable 10 percent that depends entirely on how many votes the generator includes in the block certificate. Leave votes out, and that variable slice shrinks. Include every known vote, and the generator earns the full 80.
That detail flipped how I saw this system. It's not really an 80/10/10 split, it's a compliance incentive dressed up as a reward split. The generator is financially pushed to gather as many validator signatures as possible before finalizing a block, which directly strengthens the odds that voters actually get their own 10 percent share too. The voter reward pool is distributed based on credits held, tying back to the weighted committee system I covered before.
What the whitepaper doesn't clarify is how often generators in practice submit blocks with incomplete vote sets, whether that's rare or a real recurring behavior. I can't answer that from the source material.
The real test for DUSK is whether this incentive structure keeps generators including full vote sets once network activity scales up.
Does anyone know if Dusk publishes real generator vote inclusion rates anywhere?
#dusk $DUSK @Dusk
$BTC Taps key resistance level near $80k. Correction is expected if it fails to hold above it.
A customs clearance I was tracking in Karachi port sat in "under review" for three days before jumping straight to "cleared" with no stages in between shown on the portal. I expected Dusk block finality to work the same way, pending then final, one jump. That's not how rolling finality operates at all.
There are four distinct states a block moves through, and the jump between them depends entirely on what happened in the iterations before it. A block starts as attested if zero prior iterations in that round failed, meaning no other candidate could have possibly beaten it to consensus. If any prior iterations did fail without a fail attestation, it starts as accepted instead, meaning a lower iteration block could still theoretically replace it.
The part that actually reshaped my thinking is how confirmed and final aren't really about the block itself. An attested block becomes confirmed once a single successor is attested or confirmed. But an accepted block needs 2 times n consecutive attested or confirmed blocks stacked on top of it, where n is the count of non attested prior iterations. So two similarly aged blocks can take completely different amounts of time to reach the same confidence level, depending purely on how clean their iteration history was.
What the whitepaper doesn't give me is a real average timeframe, in seconds or blocks, for something to go from accepted to final on live Dusk infrastructure. I can't manufacture that number.
The real test for DUSK is whether this variable path to finality still feels fast enough for everyday users moving funds.
Has anyone tracked how long a real transaction took to hit final status on Dusk?
#dusk $DUSK @Dusk
There are four distinct states a block moves through, and the jump between them depends entirely on what happened in the iterations before it. A block starts as attested if zero prior iterations in that round failed, meaning no other candidate could have possibly beaten it to consensus. If any prior iterations did fail without a fail attestation, it starts as accepted instead, meaning a lower iteration block could still theoretically replace it.
The part that actually reshaped my thinking is how confirmed and final aren't really about the block itself. An attested block becomes confirmed once a single successor is attested or confirmed. But an accepted block needs 2 times n consecutive attested or confirmed blocks stacked on top of it, where n is the count of non attested prior iterations. So two similarly aged blocks can take completely different amounts of time to reach the same confidence level, depending purely on how clean their iteration history was.
What the whitepaper doesn't give me is a real average timeframe, in seconds or blocks, for something to go from accepted to final on live Dusk infrastructure. I can't manufacture that number.
The real test for DUSK is whether this variable path to finality still feels fast enough for everyday users moving funds.
Has anyone tracked how long a real transaction took to hit final status on Dusk?
#dusk $DUSK @Dusk
$BTC is strongly bullish, but the current candle is extended after a very sharp move from ~$62.7K to ~$79.5K. I would not chase a long at $77.9K.
Key levels from your chart:
🟢 Resistance
$79,555: recent high
$80,400: next visible resistance
🟡 Support
$76,700: immediate pullback zone
$74,300: EMA 7 and stronger dynamic support
$72,975: important structural support
$69,400: EMA 25 area
Indicators
EMA 7 > EMA 25 > EMA 99 = strong bullish structure
MACD is strongly positive and expanding
Volume is rising with the move
Price is considerably above the EMA 7, so a cooling period would be normal
My trade plan
Preferred LONG: Wait for a pullback toward $76.7K to $74.3K and look for bullish 4H confirmation.
Possible targets: $79.5K → $80.4K → higher if $80.4K breaks
Breakout LONG: If BTC gets a clean 4H close above $80.4K with strong volume, a continuation setup becomes more attractive.
SHORT: I wouldn't short simply because BTC looks overextended. A short becomes more interesting only if $74.3K breaks decisively and the 4H structure starts turning bearish.
Bottom line: 🔥 Trend = bullish.
⚠️ Entry at $77.9K = poor risk/reward after this vertical move.
Patience for a pullback or confirmed $80.4K breakout is safer than chasing.
Key levels from your chart:
🟢 Resistance
$79,555: recent high
$80,400: next visible resistance
🟡 Support
$76,700: immediate pullback zone
$74,300: EMA 7 and stronger dynamic support
$72,975: important structural support
$69,400: EMA 25 area
Indicators
EMA 7 > EMA 25 > EMA 99 = strong bullish structure
MACD is strongly positive and expanding
Volume is rising with the move
Price is considerably above the EMA 7, so a cooling period would be normal
My trade plan
Preferred LONG: Wait for a pullback toward $76.7K to $74.3K and look for bullish 4H confirmation.
Possible targets: $79.5K → $80.4K → higher if $80.4K breaks
Breakout LONG: If BTC gets a clean 4H close above $80.4K with strong volume, a continuation setup becomes more attractive.
SHORT: I wouldn't short simply because BTC looks overextended. A short becomes more interesting only if $74.3K breaks decisively and the 4H structure starts turning bearish.
Bottom line: 🔥 Trend = bullish.
⚠️ Entry at $77.9K = poor risk/reward after this vertical move.
Patience for a pullback or confirmed $80.4K breakout is safer than chasing.
Two vendors in Karachi's Saddar market once both claimed they sold me the same phone case first, and the shopkeeper just went with whoever grabbed the receipt book first. I figured Dusk handles competing blocks the same crude way, whichever one the network sees first wins.
That's backwards from how fallback actually works. When two candidate blocks both reach consensus in the same round, which can happen from delayed or lost messages during network congestion, Dusk doesn't favor whichever arrived first. It favors whichever reached consensus at the lowest iteration number. A block at iteration 5 can get replaced by one at iteration 2 if that lower iteration block also achieves quorum. The fallback procedure reverts the local chain to right before the higher iteration block, accepts the lower iteration one instead, and discards every successor that was built on top of the discarded block.
What actually shifted my thinking is the iteration 0 exception. A block that reaches consensus at iteration 0 can never be replaced by a lower iteration block, since there isn't one. It can still get reverted later, but only if something upstream of it, one of its ancestors, gets reverted first. So finality on Dusk isn't really about a single block's status, it's inherited from everything sitting underneath it.
What the whitepaper doesn't quantify is how often forks like this actually happen once the network is under real congestion at scale, not just in theory.
Anyone seen a real fallback event happen on a Dusk block yet?
#dusk $DUSK @Dusk
That's backwards from how fallback actually works. When two candidate blocks both reach consensus in the same round, which can happen from delayed or lost messages during network congestion, Dusk doesn't favor whichever arrived first. It favors whichever reached consensus at the lowest iteration number. A block at iteration 5 can get replaced by one at iteration 2 if that lower iteration block also achieves quorum. The fallback procedure reverts the local chain to right before the higher iteration block, accepts the lower iteration one instead, and discards every successor that was built on top of the discarded block.
What actually shifted my thinking is the iteration 0 exception. A block that reaches consensus at iteration 0 can never be replaced by a lower iteration block, since there isn't one. It can still get reverted later, but only if something upstream of it, one of its ancestors, gets reverted first. So finality on Dusk isn't really about a single block's status, it's inherited from everything sitting underneath it.
What the whitepaper doesn't quantify is how often forks like this actually happen once the network is under real congestion at scale, not just in theory.
Anyone seen a real fallback event happen on a Dusk block yet?
#dusk $DUSK @Dusk
$HEMI taking a breather after that massive push 😬
📉 HEMI sitting at $0.009006 (+37.02%) — pullbacks were bound to happen after sweeping the $0.009750 local high.
⚠️ Key levels to watch:
* Support Zone: $0.00829 - $0.00850 (aligns with the 7 EMA). Holding above this keeps the parabolic structure intact.
* Resistance: Reclaiming $0.00975 opens the door to test the psychological $0.010 mark.
* Risk Zone: Losing $0.0082 could trigger a deeper correction back toward the 25 EMA around $0.00715.
MACD histogram is showing slight cooling on the 4H, so this next candle will set the tone.
The question:
Quick consolidation before breaking $0.010, or deeper pullback first? 👀
$VELVET $ACE
📉 HEMI sitting at $0.009006 (+37.02%) — pullbacks were bound to happen after sweeping the $0.009750 local high.
⚠️ Key levels to watch:
* Support Zone: $0.00829 - $0.00850 (aligns with the 7 EMA). Holding above this keeps the parabolic structure intact.
* Resistance: Reclaiming $0.00975 opens the door to test the psychological $0.010 mark.
* Risk Zone: Losing $0.0082 could trigger a deeper correction back toward the 25 EMA around $0.00715.
MACD histogram is showing slight cooling on the 4H, so this next candle will set the tone.
The question:
Quick consolidation before breaking $0.010, or deeper pullback first? 👀
$VELVET $ACE
up
0%
down
100%
no idea
0%
1 проголосовали • Голосование закрыто
$ACE just lost the momentum it built 😬
📉 ACE at $0.186 — sellers are pushing it back below the 25 EMA.
⚠️ The key zone for me is $0.183-$0.188. If buyers defend it, a reclaim of $0.203 could bring momentum back.
💀 But lose $0.183 with confirmation, and that recovery setup starts looking weak.
MACD is already cooling off, so I’m watching the next 4H candle closely.
The question:
Bounce from here or deeper reset? 👀
$VELVET $HEMI
📉 ACE at $0.186 — sellers are pushing it back below the 25 EMA.
⚠️ The key zone for me is $0.183-$0.188. If buyers defend it, a reclaim of $0.203 could bring momentum back.
💀 But lose $0.183 with confirmation, and that recovery setup starts looking weak.
MACD is already cooling off, so I’m watching the next 4H candle closely.
The question:
Bounce from here or deeper reset? 👀
$VELVET $HEMI
This market is moving way too fast 😭
🔥 $BTW at $0.633 — insane momentum, but that 0.7788 spike shows how dangerous chasing can get.
📈 $VELVET at $0.6718 — bounce is holding, but it still has to reclaim $0.72-$0.73 to really change the structure.
👀 $HEMI at $0.00911 — my sneaky one. Strong breakout, and $0.0085-$0.0086 is the zone I’d watch on a pullback.
Three charts. Three different stories.
The real question now:
Which one survives the cooldown? 👀
🔥 $BTW at $0.633 — insane momentum, but that 0.7788 spike shows how dangerous chasing can get.
📈 $VELVET at $0.6718 — bounce is holding, but it still has to reclaim $0.72-$0.73 to really change the structure.
👀 $HEMI at $0.00911 — my sneaky one. Strong breakout, and $0.0085-$0.0086 is the zone I’d watch on a pullback.
Three charts. Three different stories.
The real question now:
Which one survives the cooldown? 👀
velvet
46%
BTW
36%
HEMI
18%
22 проголосовали • Голосование закрыто
VELVET (VELVET) 4H chart read
From the chart, $0.65 to $0.66 is the key decision zone.
Support
$0.64 to $0.65: immediate support
$0.60 to $0.62: stronger support
$0.57: major downside support
Resistance
$0.68 to $0.70: first resistance
$0.73 to $0.75: stronger resistance, near EMA25
$0.90+: major resistance
Indicators
Price: ~$0.658
EMA7: $0.655, almost directly under price
EMA25: $0.728, still well above price
EMA99: $0.657, almost exactly at current price
MACD is still negative, but the histogram is improving.
Trade bias
Right now I'd call it neutral to slightly bullish for a bounce, not a confirmed reversal.
Long setup: A 4H close above $0.68 to $0.70 with increasing volume would give a cleaner confirmation. Targets could be $0.73 to $0.75, then higher.
Short setup: If price loses $0.64, especially with a 4H close below it, the setup weakens and $0.60 to $0.62 becomes the next area to watch.
The biggest mistake here would be chasing the recent +32% move while price is still sitting around the EMA99 and below the EMA25.
$VELVET
From the chart, $0.65 to $0.66 is the key decision zone.
Support
$0.64 to $0.65: immediate support
$0.60 to $0.62: stronger support
$0.57: major downside support
Resistance
$0.68 to $0.70: first resistance
$0.73 to $0.75: stronger resistance, near EMA25
$0.90+: major resistance
Indicators
Price: ~$0.658
EMA7: $0.655, almost directly under price
EMA25: $0.728, still well above price
EMA99: $0.657, almost exactly at current price
MACD is still negative, but the histogram is improving.
Trade bias
Right now I'd call it neutral to slightly bullish for a bounce, not a confirmed reversal.
Long setup: A 4H close above $0.68 to $0.70 with increasing volume would give a cleaner confirmation. Targets could be $0.73 to $0.75, then higher.
Short setup: If price loses $0.64, especially with a 4H close below it, the setup weakens and $0.60 to $0.62 becomes the next area to watch.
The biggest mistake here would be chasing the recent +32% move while price is still sitting around the EMA99 and below the EMA25.
$VELVET
Проверено
We had a load shedding stretch in Islamabad last week where the grid just kept failing over and over, and every time it came back the backup system had to restart from scratch instead of picking up where it left off. I assumed Dusk's emergency mode worked the same way, network stalls, it just keeps retrying the same fixed timeout until something sticks.
That's not what happens. Emergency mode only kicks in after 16 consecutive failed iterations, and once it activates, the whole timeout structure gets removed. Iterations don't expire anymore, they run indefinitely until a candidate block actually gets proposed and reaches quorum in both validation and ratification. NoCandidate and NoQuorum votes get disabled too, so every step has to properly succeed before the next one starts.
What actually reframed this for me is that multiple of these open iterations can run at once. That's not a flaw, it's intentional, it raises the odds that at least one produces a valid block. The tradeoff is more fork risk, which gets resolved by always picking whichever candidate reached consensus at the lowest iteration number.
There's also a last resort inside the last resort. If even the final iteration stalls, provisioners holding the majority of total stake can request an emergency block, a special empty block signed by Dusk with no transactions in it, just to keep the round moving.
What the whitepaper doesn't say is how often this has actually triggered on real Dusk infrastructure so far. I have no data to back a frequency claim.
The real test for DUSK is how rarely emergency mode needs to fire once mainnet runs at real scale.
Has anyone actually witnessed emergency mode trigger on Dusk yet?
@Dusk #dusk $DUSK
That's not what happens. Emergency mode only kicks in after 16 consecutive failed iterations, and once it activates, the whole timeout structure gets removed. Iterations don't expire anymore, they run indefinitely until a candidate block actually gets proposed and reaches quorum in both validation and ratification. NoCandidate and NoQuorum votes get disabled too, so every step has to properly succeed before the next one starts.
What actually reframed this for me is that multiple of these open iterations can run at once. That's not a flaw, it's intentional, it raises the odds that at least one produces a valid block. The tradeoff is more fork risk, which gets resolved by always picking whichever candidate reached consensus at the lowest iteration number.
There's also a last resort inside the last resort. If even the final iteration stalls, provisioners holding the majority of total stake can request an emergency block, a special empty block signed by Dusk with no transactions in it, just to keep the round moving.
What the whitepaper doesn't say is how often this has actually triggered on real Dusk infrastructure so far. I have no data to back a frequency claim.
The real test for DUSK is how rarely emergency mode needs to fire once mainnet runs at real scale.
Has anyone actually witnessed emergency mode trigger on Dusk yet?
@Dusk #dusk $DUSK
I spent an hour today going back and forth with a court clerk in Lahore about what actually counts as proof of a hearing outcome versus just a note in a file. That mental picture stuck when I got to Dusk's attestation system. I assumed an attestation was just a fancy word for a confirmed block, one status, done.
Wrong. An attestation is proof that a quorum was reached in one specific iteration, and it comes in two forms. A success attestation proves a supermajority, two thirds of committee credits, voted Valid. A fail attestation proves a majority, half plus one, voted Invalid, NoCandidate, or NoQuorum. Both are equally valid proofs, they just prove opposite outcomes.
Here's the part that reframed it for me. Since more votes can come in after quorum is technically reached, it's possible to end up with multiple valid attestations for the same iteration. So each block actually carries an attestation of the previous block, called a block certificate, which locks in one specific set of voters as the official record. That certificate is what decides rewards and penalties, not just any attestation floating around.
What the whitepaper doesn't tell me is how often multiple competing attestations actually show up in practice versus being a rare edge case. I can't fake certainty there.
The real test for DUSK is whether block certificates stay unambiguous once network conditions get messy at scale.
Has anyone seen a real case of competing attestations on a Dusk block yet?
@Dusk #dusk $DUSK
Wrong. An attestation is proof that a quorum was reached in one specific iteration, and it comes in two forms. A success attestation proves a supermajority, two thirds of committee credits, voted Valid. A fail attestation proves a majority, half plus one, voted Invalid, NoCandidate, or NoQuorum. Both are equally valid proofs, they just prove opposite outcomes.
Here's the part that reframed it for me. Since more votes can come in after quorum is technically reached, it's possible to end up with multiple valid attestations for the same iteration. So each block actually carries an attestation of the previous block, called a block certificate, which locks in one specific set of voters as the official record. That certificate is what decides rewards and penalties, not just any attestation floating around.
What the whitepaper doesn't tell me is how often multiple competing attestations actually show up in practice versus being a rare edge case. I can't fake certainty there.
The real test for DUSK is whether block certificates stay unambiguous once network conditions get messy at scale.
Has anyone seen a real case of competing attestations on a Dusk block yet?
@Dusk #dusk $DUSK
My uncle in Peshawar sits on a small mosque committee where every member gets exactly one vote regardless of how much they've donated to the building fund. I assumed Dusk's voting committees worked the same way, one provisioner picked equals one vote counted, simple headcount toward quorum.
That assumption fell apart once I read how votes are actually weighted inside a committee. Each member holds a number of credits, and those credits come straight out of the deterministic sortition process I wrote about earlier. A committee has a fixed total of 64 credits distributed across selected provisioners. When votes get counted, a member's vote isn't counted once, it's multiplied by however many credits they hold. Someone with 3 credits effectively casts 3 votes toward quorum.
This reframes what quorum even means here. Reaching a two thirds supermajority isn't about two thirds of the people in the room agreeing, it's about two thirds of the 64 credits agreeing. A committee could theoretically have fewer individual provisioners but still hit quorum fast if a few of them hold heavy credit weight. Votes get aggregated using BLS signatures too, with a bitset marking exactly which members are included, which keeps verification efficient even with weighted votes.
What the whitepaper doesn't clarify is how often credit distribution actually gets lopsided in a single committee versus staying fairly even. Without real data I can't say how common heavy weighted members are.
The real test for DUSK is whether credit weighted voting stays fair once fewer large stakers start dominating committee credits.
Does anyone know the average credit spread seen in real Dusk committees so far?
@Dusk #dusk $DUSK
That assumption fell apart once I read how votes are actually weighted inside a committee. Each member holds a number of credits, and those credits come straight out of the deterministic sortition process I wrote about earlier. A committee has a fixed total of 64 credits distributed across selected provisioners. When votes get counted, a member's vote isn't counted once, it's multiplied by however many credits they hold. Someone with 3 credits effectively casts 3 votes toward quorum.
This reframes what quorum even means here. Reaching a two thirds supermajority isn't about two thirds of the people in the room agreeing, it's about two thirds of the 64 credits agreeing. A committee could theoretically have fewer individual provisioners but still hit quorum fast if a few of them hold heavy credit weight. Votes get aggregated using BLS signatures too, with a bitset marking exactly which members are included, which keeps verification efficient even with weighted votes.
What the whitepaper doesn't clarify is how often credit distribution actually gets lopsided in a single committee versus staying fairly even. Without real data I can't say how common heavy weighted members are.
The real test for DUSK is whether credit weighted voting stays fair once fewer large stakers start dominating committee credits.
Does anyone know the average credit spread seen in real Dusk committees so far?
@Dusk #dusk $DUSK
Войдите, чтобы посмотреть больше материала