Technical documentation

One network. Explicit operating boundaries.

A concise public guide to integration, validation, governance and security. Signed deployment packages and operator manuals are distributed through controlled channels.

01

Network model

31 equal-power validators: 30 bank-designated seats and one permanent Superlab seat. Progress requires 21/31; membership changes require 25/31.

02

Chain identity

Testnet uses annurax-testnet-1. Mainnet reserves annurax-1. A ledger-resetting Testnet restart increments the numeric suffix.

03

API and Explorer

Annurax API v1 exposes chain status, accounts, blocks, transactions, validator registry and verified assets through rate-limited HTTPS ingress.

04

Keys and signing

Banks generate and retain validator private keys. The portal handles public inputs and unsigned actions only. Master Annurax signs outside the portal.

05

Bank onboarding

Admission checks legal standing, technical capacity, provider/ASN/region diversity, key custody, monitoring, backup and incident response.

06

Security scope

Private VPS acceptance is complete with scope limits. Public Testnet, independent operators and external audit remain separate gates.

API v1

Public API surface

GET /v1/chain GET /v1/ready GET /v1/blocks/{height} GET /v1/transactions/{hash} GET /v1/accounts/{address} GET /v1/governance/validators GET /v1/assets
Never send seed phrases, private keys or real funds through the website, application dossier or support channel.