Products

PaymentsSmart contractsAttributionIdentity verificationTokenizationTreasury & walletsComplianceGovernanceSecurity

Solutions

Platforms & marketplacesAgencies & service firmsEnergy & infrastructureAI agents & autonomous commerceReal-world assets

Developers

DocumentationAPI referenceNetwork statusBridge & webhooks

Company

Pricing Company Contact sales Sign in

XODIAK / Network status

Network status

Protocol state for xodiak-1, with the date each figure was read off the node. Current production has not been reverified for this page, and a fresh chain height proof is pending.

xodiak-1chain id
887,995height at 2026-09-03
2026-04-08genesis
Proof-of-Anchorconsensus

Protocol parameters.

ParameterValue
Chain idxodiak-1
Target block interval5 seconds
Genesis supply1,000,000,000 XDK
Micro unituxdk, 6 decimals
Block reward2 XDK
Minimum validator stake10,000 XDK
ConsensusProof-of-Anchor, committing at two thirds of attested reserve value
SignaturesML-DSA-65 (FIPS 204 / Dilithium-3)
Key exchangeML-KEM-768 (FIPS 203 / Kyber-768)
Transaction encodingQBC-G1

Dated record, with a 35 day stall we are not going to hide

The last verified figure for this page is height 887,995 at 2026-09-03. Current production is not reverified here, and a fresh proof is pending. The chain produced no block between 2026-07-29 and 2026-09-03. A committed block was written to storage while the chain state pointer was not advanced to match it, so every subsequent round failed height validation; the sole validator then went stale and was jailed, and the liveness check could not release it because the release pass ran only when at least one validator was already active. The causes above are the ones found at the time. Committed history was never affected and every block remains verifiable.

Two things follow that are worth knowing before you evaluate us. First, single-validator operation is a bootstrap posture, not a design target, and it is exactly why validator onboarding is the next piece of work. Second, block cadence is deliberately uneven under the protocol parameters: a transaction targets the next 5 second tick, but an idle network stamps a liveness block every 10 minutes rather than every 5 seconds. Those are design parameters, not a current liveness claim. Polling this endpoint twice in a row and seeing the same height is normal.

Ready to get started?

Create an account instantly, or talk to us about a settlement design for your business.

See what you'll pay

Per-settlement pricing tied to what actually moves. No seat licences, no hidden spread.

Pricing details

Start building

Open an account, sign a transaction, read a block. About ten minutes end to end.

Integration options