The chart is getting interesting $BTW $VELVET

These two are definitely stealing some attention from the market.

And of course I’m here discovering them after the move started.

A blockchain can look perfectly orderly when everything is working. The interesting part is what happens when it doesn’t.

What caught my attention in Dusk is that the network doesn’t simply assume every block will arrive on time or that every provisioner will always be reachable.

Delayed or lost messages can cause multiple candidate blocks to reach consensus in the same round creating a fork. Dusk’s fallback procedure normally resolves this by selecting the candidate from the lowest iteration. A higher iteration block can therefore be reverted if a lower iteration candidate later reaches consensus.

But there’s a deeper fallback.

If enough consecutive iterations fail because provisioners are offline or isolated Dusk can enter emergency mode. Normal step timeouts are disabled and iterations continue until a candidate block reaches quorum. Multiple open iterations can run at the same time increasing the chance of reaching consensus although that also creates a higher possibility of forks.

That made me think about consensus differently.

The real test of a network isn’t only how it behaves when everything goes right.

It’s what happens when communication breaks down.

For financial infrastructure having defined behavior for those messy conditions may be just as important as achieving fast consensus under normal conditions.

@Dusk_Foundation $DUSK #dusk

What matters most during failures?