As of network epoch 14493 (at 22:05:51 UTC on Tue 12th July), the validators and other nodes coordinated a smooth transition to a new set of engine rules, the first coordinated update of its kind.
This protocol update arose in accordance with the policy announced here (Planned Updates to Radix Network Fees and Emissions | The Radix Blog | Radix DLT) which aims to keep fees and emissions broadly stable and aligned with the tokenomics.
Future protocol updates may arise semi-regularly to maintain this alignment.
If any nodes are not working after the update, they should upgrade to 1.3.1 as a priority (Release 1.3.1 · radixdlt/radixdlt · GitHub).
If you haven’t been staying up to date, you can learn more about the fork here!
From a node runner perspective the fork went really well: 99/100 nodes in the validating set forked properly. Only one node, Trust Staking, failed to fork due to not having updated to 1.3.0 in time.
When the fork went live nodes lost 25 peers, from 254~ to 229, probably because some backup nodes were still running an old version of the node, but this had no impact on the network.
Due to missed proposals from Trust Staking and Radix DLT Staking, epoch 14493 lasted 48 minutes instead of the usual 35~ minutes. Epoch duration started decreasing at epoch 14498, when Trust Staking successfully updated and fixed its node:
| EPOCH | DURATION | USER TXNS | FEES | STAKED | UNSTAKED | PROPOSALS MISSED | VALIDATOR CHANGES |
|---|---|---|---|---|---|---|---|
| 14500 | 00:34:47 | 7 | 0.3480 | 0 | 0 | 0 | |
| 14499 | 00:34:57 | 14 | 1.6063 | 5,000 | -5,992 | 0 | |
| 14498 | 00:39:45 | 28 | 1.7412 | 197 | 0 | 40 | |
| 14497 | 00:45:06 | 53 | 3.8032 | 100,490 | 0 | 90 | |
| 14496 | 00:45:23 | 52 | 2.6411 | 0 | 0 | 90 | |
| 14495 | 00:45:29 | 53 | 8.6225 | 3,345 | 0 | 90 | |
| 14494 | 00:45:37 | 23 | 2.0725 | 1,000 | 0 | 92 | |
| 14493 | 00:48:17 | 68 | 4.2667 | 18,742 | 0 | 113 | |
| 14492 | 00:34:01 | 40 | 3.7600 | 0 | 0 | 0 |
The Radix Node Runners community is ready and prepared for all future forks. 
Credits to @Peachy for the screenshot and @Stuart for his amazing dashboard that provides lots of insight on network status.