Anchor Hardfork Update: New point release

Oxen is announcing changes to the rollout of Oxen Anchor Hardfork. A new point release (version 11.1.0) will be released in advance of the Anchor Hardfork release. 

Oxen 11.1.0 will contain all of the additional functionality which was slated for release in the Oxen Anchor Hardfork (now version 11.2.0), but will not trigger a hardfork. This functionality is described in detail here.

The decision to add the Oxen 11.1.0 point release has been made out of caution due to the Anchor Hardfork disabling new Service Node registrations, meaning any nodes which are deregistered will not be able to be re-registered until Session Token's mainnet launch.

Oxen 11.1.0 will be a non-mandatory upgrade; and it will not hardcode any values for the eventual Anchor Hardfork. 

This point release offers the opportunity to verify the proper function of new features in the Oxen mainnet environment without disabling new Service Node registrations. This provides more flexibility for both Session Contributors and the Oxen community to test the significant adjustments packaged in the new binaries (and catch any issues while Service Nodes can still be re-registered).

We have also received feedback from some node operators running multiple nodes who are concerned about the amount of requests which will be made to Arbitrum RPC providers. Over the next week we will be looking into streamlining L2 request caching to reduce the number of requests necessary for multi-node operators. This will ensure that  we have more robust mechanisms in place for when the L2 tracker becomes mandatory.

When will you release the Oxen 11.1.0 binaries? 

It is currently anticipated that Oxen 11.1.0 will be released on February 25. Developers are currently working on resolving a few technical issues before releasing 11.1.0.

The first relates to higher memory usage induced by storing snapshots of the Oxen blockchain. 

Additionally, in test builds we have witnessed nodes who restart oxend are performing a very slow rescan of the chain, which can cause a Service Node to become deregistered if it takes too long.

Fixes to both of these issues have already been identified, clearing the way for release of Oxen 11.1.0 next week.

Is Oxen 11.1.0 a mandatory upgrade? 

Oxen 11.1.0 is not a mandatory upgrade. However, operators are strongly encouraged to upgrade in order to test the migration candidate. This will also allow operators to experiment with new features, such as connecting to an Arbitrum One RPC node, before they become strict requirements (after the Anchor Hardfork).

When will the Oxen Anchor Hardfork Binaries be released?

The release date of Oxen Anchor hardfork binaries is pending the success of the migration candidate (Oxen 11.1.0). Currently, the release and live testing of 11.1.0 is taken to be part of the testing allowance which was originally scheduled for the period before the Landing Hardfork. 

Support

If you would like to discuss 11.1.0 or require help with your node, please reach out via the Oxen Service Nodes channel on Telegram for assistance.