The performance upgrade [Blocktrades planned and built for Hive](https://peakd.com/hive-139531/@blocktrades/one-block-irreversibility-for-delegated-proof-of-stake-dpos) which will be included with hardfork 26 may have caught many by surprise in a positive way.

From a very high-level view, what takes 45 seconds now to turn a block into an irreversible block on Hive - which is already very fast in the crypto space - will be reduced to 3 seconds or less (until the next block is produced) in most cases with One-Block Irreversibility protocol changes.

Dan describes in detail how that will be achieved, as well as the similarities and the difference between block irreversibility in DPOS protocols and confirmed blocks in POW protocols. So if you want to know more, read his post I linked above.

So, this is a **performance upgrade**, because blocks reach the irreversibility status much quicker and can be relied on that they won't be changed afterward through forking. A reversible block can be reversed through forking, which can happen if witnesses don't agree on the state of the blockchain at some point. Micro-forks are actually something quite common.

A reversed block may not be something critical when you cast a vote or comment, because you'll do it again if it didn't work the first time.

But if you spend some HIVE or HBD, you really want that transaction to go through as planned.

Because let's say you pay HIVE or HBD for something. Let's say a Splinterlands pack. If the transaction is reversed while it's still not in the irreversible state, you get back your HIVE or HBD, but if the store has already given you the pack, it's their loss, because you get the product, they don't get the payment.

The problem is, apparently, [most dapps don't wait for blocks to become irreversible](https://peakd.com/hive-139531/@themarkymark/re-mahdiyari-rbldt0).
![image.png](https://images.hive.blog/DQmcrDS4NT9pQejcx9MjgkRiXsr7Gf2AmYeZBNkp7rqZweC/image.png)

I understand their owners, degrading user experience keeps people from using their interfaces. And if the risks are not high, they take them.

But looks like from HF26 onwards, they don't have to take those risks either if they switch their code to waiting for a block to become irreversible, without degrading the UX.

Much better will be for newer dapps, which will use HAF for development, and they won't have to deal with these background operations while taking advantage of the One-Block Irreversibility (OBI) that HAF will use.

From this point of view, OBI will **improve security** in the Hive ecosystem as well.

And with the recent Terra LUNA/UST events clear in our minds, many have reconsidered the security features of Hive as positive and necessary, while not so long ago they just hindered our growth (which is also true).

Posted Using [LeoFinance <sup>Beta</sup>](https://leofinance.io/@gadrian/one-block-irreversibility-for-hive-means-better-performance-but-also-better-security-for-existing-dapps)