Just went deeper into Dusk’s Rolling Finality again.A block starts as Accepted, becomes Attested after enough votes, then moves to Confirmed, and finally Final.The interesting part is the difference between n=0 and n>0: • The first iteration (n=0) gets the fast path. Once it reaches Attested, it can already be treated as irreversible. • Later iterations still need extra confirmations even after becoming Attested.Makes sense the network doesn’t want a later block generator to get the same instant finality if the first attempt fails.Curious how these rules are currently implemented and whether the confirmation requirements can change over time. @DuskFoundation $DUSK #dusk