Congratulations! We are officially in the Hive Evolution territory!
Hivefork 26 happened at precisely 12pm GMT. (that was 3pm my time, as you can see below)
All this impressive work and testing were put together by some of the smartest people on this blockchain for over a year, for 3 seconds in the spotlights. Enough time to generate a new block and switch from version 1.25.0 to version 1.26.0, where the consensus of block producers (witnesses) was.
Most people didn't even realize hardfork happened, because there was nothing to notice, initially. If the hardfork is successful, you won't be aware of it right away. If there is something terribly wrong, then it will become obvious.
After the hardfork time passes, and you get a confirmation it happened (like I did from the official channel up there), you can start to poke around and see if the changes that come with the hardfork really work.
But even then it might be too soon.
Because to prevent any potential issues during or immediately after the hardfork, you will notice some services and apps (or parts of apps) may not work properly for a while.
They'll slowly come back to normal operation on the other side of the fork.
Some operations that are newly introduced with the hardfork may not have support in the apps yet, even if they work as intended at the core level.
This is the case for RC delegations from Hive Evolution, which was one of the most expected new features of HF26. Even if it seems to work as intended at the core level (or if you broadcast the custom json yourself - see an example in the screenshot below), the interfaces don't have RC delegations support added already, although they are working on it.
It's too soon to say that the hardfork was flawless. Bugs can be found even a week after the hardfork happens. But it was most likely the most tested hardfork from the history of Hive (including its legacy), and I wouldn't be surprised if there really aren't any significant issues discovered post-hardfork.
I already experienced some very quick operations. Probably the one-block irreversibility has something to do with it. Optimizations the Blocktrades team made in different parts of the core code surely has an impact as well. I can't wait to see if that has an influence on the speed of transactions on Hive-Engine too. When dealing with lots of operations, especially related to diesel pools, a speed improvement would be fantastic. Since they are custom jsons on Hive, and if their speed was increased, I don't see why that wouldn't reflect on the speed of transactions in HE.
This was a major fork. We don't even realize how big yet. But we will.
Happy Fork Day, Everyone!