1.9.9-beta
The version in Settings reads 1.9.9-beta, and that suffix is the whole of this release. To scale Hexncoin for high availability, the team is testing network upgrades and clustering: running the platform across several nodes behind one address, so a failure on any one of them routes to another instead of taking the system down. This build carries the same apps and features as 1.9.9; it is published only so those infrastructure changes can be verified against live traffic and real data points rather than a staging copy. Once the findings are reviewed and the community has chosen a build codename, v2 ships with the full set of functionality and features held back for it.
3 changes in this release
Highlights
- 01
Clustering and network upgrades under test
Hexncoin is moving from a single serving path onto a cluster of nodes behind one address. The routing layer is learning to spot an unhealthy node and send the request to a healthy one, so a restart, a slow response or a failed deploy stops being an outage. This beta runs that setup against real visitors so the failover behaviour is measured rather than assumed.
- 02
A build published to be measured
1.9.9-beta exists to collect data points: response times, failover counts, cache hit rates and how the cluster holds up under real load. Nothing in the app layer changed from 1.9.9, so any movement in those numbers comes from the infrastructure and not from new code. The build is temporary and is replaced once the results are in.
- 03
v2 follows a community codename vote
Every Hexncoin build so far has carried a codename, and the next major one does not have its yet. The community picks it, and v2 then ships with the functionality and features that were set aside while the platform's foundations were reworked. Until then, this beta is the current build.
Everything in this release
New1
- The reported version is 1.9.9-beta, a temporary measurement build. The apps and features are unchanged from 1.9.9; the next full version is v2, published after the community names it.
Improved2
- The serving path is moving onto a multi-node cluster behind a single address, with routing that fails a request over to a healthy node instead of returning an error.
- Network routing and the cache and storage layers were reworked so any node in the cluster can answer a request, which is what makes node-level failover possible.
Every version of Hexncoin, newest first.