#dusk $DUSK @Dusk
I used to think that once a transaction was accepted, it was basically done. Then I looked closer at Dusk’s transaction lifecycle and found a distinction I hadn’t really considered: submitted, accepted, and finalized aren’t necessarily the same moment.
That sounds like a technical detail until a financial application starts acting on that transaction.
If an asset transfer, payment, or another instruction depends on it, acting before finality could mean building the next step on a state that isn’t actually settled yet. What I find interesting is that Dusk treats deterministic finality as part of the infrastructure needed for financial applications, rather than just another blockchain performance metric.
At what point should a financial application stop asking “was it accepted?” and start asking “is it final?”
@Dusk #dusk $BTC $BNB
I used to think that once a transaction was accepted, it was basically done. Then I looked closer at Dusk’s transaction lifecycle and found a distinction I hadn’t really considered: submitted, accepted, and finalized aren’t necessarily the same moment.
That sounds like a technical detail until a financial application starts acting on that transaction.
If an asset transfer, payment, or another instruction depends on it, acting before finality could mean building the next step on a state that isn’t actually settled yet. What I find interesting is that Dusk treats deterministic finality as part of the infrastructure needed for financial applications, rather than just another blockchain performance metric.
At what point should a financial application stop asking “was it accepted?” and start asking “is it final?”
@Dusk #dusk $BTC $BNB