Skip to content

Patching and deployment ​

How changes and patches are put live on the KriptoNyx platform, and how each is verified and, if necessary, rolled back.

The rule for every change ​

Every change, to any component, follows the same five steps:

Step
1. ChangeThe component's source, in its own repository
2. BuildFrom that source
3. PublishUsing that component's own deploy procedure
4. VerifyRun a full health sweep. All 39 checks must pass before the change is considered live
5. Roll backTo the previous release if any check fails — then investigate

The monitoring doubles as the post-deploy test. A deploy is not finished when it is published; it is finished when the sweep passes.

By component ​

Chain node ​

The previous release is kept before an upgrade. The new one is installed and the node restarted, and it must return to fully synced with the chain height advancing — exactly what the Synced, Blocks being produced and Height advancing checks assert. Rollback restores the previous release.

Consensus upgrades are separate

An upgrade that changes consensus cannot be rolled out one node at a time. It is coordinated with the other validators at an agreed block height, outside this procedure. Validators should see Operating a node.

Web applications ​

The explorer, staking, DEX, ICO and faucet are each built from source and published by their own deploy procedure, then verified.

For the DEX the previous build is kept alongside the new one, so it can be restored immediately — its build is served from disk, so a failed build would otherwise take the live site down with it.

Backend services ​

The API, the bridge and the explorer's account service are updated from source and restarted under the process manager, then verified. Application processes are restarted automatically if they fail, and brought back automatically after a server restart.

Documentation ​

This site is rebuilt from source and republished. The build fails on a broken internal link, so a bad cross-reference is caught before it is published rather than becoming a 404 for a reader.

TLS certificates ​

Renewed automatically, and checked independently by the monitoring, which flags any certificate within 14 days of expiry.

Cadence ​

AreaPractice
Operating systemSecurity updates are applied automatically every day. The continuous health checks catch any regression within minutes
DependenciesSecurity advisories are reviewed at each change to a component
Chain nodeReleases are applied as published, by the procedure above. Consensus upgrades are coordinated at an agreed height
CertificatesRenewed automatically, and independently monitored

Rollback ​

Every component has a defined rollback, used whenever the post-deploy sweep fails:

ComponentRollback
Chain nodeRestore the kept previous release and restart
DEXRestore the kept previous build
ExplorerRestore the copies of changed files taken before the change
Staking, ICO, faucet and backend servicesRevert the change in source, rebuild, republish
DocumentationRevert the change in source and republish
CertificatesNot applicable — renewal is automatic and non-destructive

Where the detail is ​

This page describes the process. The live results are on the status page, and the public summary of this procedure is at How KriptoNyx is monitored and patched. The detailed operational runbook — hosts, commands and per-component rollback steps — is maintained by the operators and is available on request.

KriptoNyx testnet — chain ID 3009 (kriptonyx_3009-1)