Four tiers, five node roles,
fifteen regional anchors.

Every VXIR Wallet is a node. The infrastructure scales with adoption — operators earn their way up the tiers through proven reliability, never by buying in. At the top, fifteen regional masternodes anchor the whole network across every populated continent.

None of this is running yet — we're pre-funding, and we'll say so plainly. What follows is the network as designed and filed: the topology we stand up at launch and the staged path to get there. The genuinely hard part — the compiler — is already proven on mainnet. The network is the tractable part: batch compilation jobs distributed across an ordinary, tiered server fleet. No new invention required, just a disciplined build.
5
Node roles
15
Regional anchors
60
Backbone nodes at launch
0
Token · no node sale
Ordinary hardware. Deliberate arrangement.

Strip away the tier names and the network is straightforward: standard cloud servers running batch compilation jobs, arranged so that trust and capability are earned rather than purchased. The discipline isn't in the machines — it's in who is allowed to do what, and why.

The work, in plain terms

A wallet on a phone does light verification and routing telemetry. A hardened server in a data center does the heavy compilation and regional coordination. Everything in between is a graduated step from one to the other. These are well-understood server workloads — nothing here waits on a research breakthrough.

Why bother with tiers at all

Because a payments network earns institutional trust by being predictable. Tiering lets the network match responsibility to proven reliability — sensitive work only runs where reliability has been demonstrated, and the regional anchors stay under direct operational control. That's the whole point of the segmentation.

Capability escalates with trust.

Four privilege tiers, five node roles. Each step up means more hardware, a higher uptime commitment, and more network responsibility — and you rise only by proving you belong. The POS terminal is the network's merchant edge: a second role in the T2 band, sitting between the earned Relay node and the Compilation backbone. The meters on each rung show the escalation at a glance.

T1
Wallet Node
Free — every wallet runs one
The network's eyes.
Verification, corroboration, and routing telemetry — running quietly in the background of every VXIR Wallet. Just by being on, every user contributes to keeping the network honest and well-routed.
Hardware: any smartphone or computer  ·  Uptime: 6+ hrs/day (rolling 24h)  ·  Operator: every wallet user
Hardware
Uptime
Responsibility
T2
Relay Node
Earned — 85%+ Quality Score, 90 days
The connective tissue.
Transaction relay, routing, and settlement confirmation. A T1 operator graduates here only after sustaining a high Quality Score for ninety consecutive days — reliability is the price of admission, and it can't be skipped.
Hardware: consumer server or always-on workstation  ·  Uptime: 95%+ (rolling 30d)  ·  Operator: graduated T1 operators
Hardware
Uptime
Responsibility
T2 · POS
POS Node
Provisioned to onboarded merchants
The merchant edge.
The point-of-sale terminal where a customer actually pays. It captures the payment intent at checkout, hands it into the network for compilation and settlement, and confirms the result back to the merchant in seconds. A second role in the T2 band — relay-class, but on dedicated, VXIR-furnished hardware rather than an operator's earned machine.
Hardware: VXIR-furnished point-of-sale terminal  ·  Uptime: 95%+ (business-critical)  ·  Operator: the onboarded merchant
Hardware
Uptime
Responsibility
T3
Compilation Node
Application-only, opened by capacity need
The backbone.
Where intent actually becomes executable chain instructions — compiling VXIR IR into native calls for each rail. Labs-operated at first, with qualified external operators admitted by application. Compilation operators earn a 30% share of compilation revenue.
Hardware: VPS / dedicated server, 4–8 vCPU · 16–32GB  ·  Uptime: 95%+ (rolling 30d)  ·  Operator: Labs, then qualified externals
Hardware
Uptime
Responsibility
T4
Regional Masternode
VXIR Labs operational authority
The anchor and the trust layer.
One per region: the regional backbone that coordinates its T3 nodes, aggregates ENGRAM state, and enforces SLAs. Held and run by VXIR Labs so that security response and network health stay under direct authority — this is the layer institutions lean on.
Hardware: high-availability dedicated server  ·  Uptime: 99%+ (rolling 30d)  ·  Operator: VXIR Labs
Hardware
Uptime
Responsibility
Segmentation is the security model.

The tiers aren't org-chart decoration — they're how the network defends itself and stays healthy. Four principles do the work, and they're built into the filed architecture.

01

Privilege follows proven reliability

No node touches compilation or coordination until it has demonstrated uptime and a sustained Quality Score. Unproven nodes simply never reach the sensitive layers — which keeps the attack surface small by construction.

02

Hardware tracks responsibility

Light telemetry runs on a phone; ENGRAM aggregation and SLA enforcement run on hardened, high-availability servers. Resource always matches criticality, so the most important work runs on the most resilient machines.

03

No buy-in — ever

There's no public node sale and no token to purchase a position. Every path in requires capital commitment, sustained performance, or real technical contribution. That's the network's Sybil resistance: you can't flood it with nodes you simply bought.

04

The anchor stays under authority

All fifteen regional masternodes are VXIR Labs-operated, so security responses and SLA enforcement never depend on anonymous operators. The trust anchor is held, not delegated — the foundation institutional confidence is built on.

Three ways up the network.

There's more than one door, but every door asks for something real. Whichever path an operator takes, they arrive having proven capital, consistency, or capability.

Path 01

Financial

Early backers who bring capital and conviction enter directly at the compilation tier during the pre-seed window.

Brings: capital, early belief
Entry: T3 direct · immediate access
Path 02

Grind

The earned route: start as a T1 wallet, sustain quality, graduate to relay, then apply for compilation as capacity opens.

Brings: consistency, geographic coverage
Entry: T1 → T2 → T3 · application window
Path 03

Builder

Engineers who contribute code, integrations, or expertise petition in on the strength of their technical work.

Brings: code, integrations, expertise
Entry: petition → T2 · application window

One rule across all three: no public node sale, no token purchase. Every path into the network requires capital commitment, sustained performance, or meaningful technical contribution — and operators share 30% of compilation revenue, with an annual performance bonus pool that pays earliest contributors the most.

Fifteen masternodes. Every populated continent.

At launch, fifteen T4 regional masternodes form the backbone — each one coordinating three T3 compilation nodes, for a sixty-node fleet positioned for sub-100ms compilation latency wherever demand is. These are the planned positions; we stand them up in stages.

Regional anchors 15 Compilation nodes 45 Backbone total 60 Continental coverage 8 zones
Node 01
New York
AWS us-east-1
US East · institutional finance
Node 02
San Francisco
AWS us-west-2
US West · Silicon Valley · AI
Node 03
Mexico City
AWS us-east-1 relay
Central America · Caribbean
Node 04
São Paulo
AWS sa-east-1
South America · LATAM
Node 05
London
AWS eu-west-2
UK · Western Europe fintech
Node 06
Vilnius
Regional provider
Eastern Europe · Nordics · Baltics
Node 07
Rome
Regional provider
Southern Europe · Mediterranean
Node 08
Dubai
AWS me-south-1
Gulf states · MENA · Europe–Asia bridge
Node 09
Nairobi
Oracle Cloud / regional
East Africa
Node 10
Cape Town
AWS af-south-1
Southern Africa
Node 11
Lagos
Equinix / local
West Africa · Nigeria fintech
Node 12
Mumbai
AWS ap-south-1
India · South Asia
Node 13
Singapore
AWS ap-southeast-1
Southeast Asia · ASEAN
Node 14
Tokyo
AWS ap-northeast-1
Japan · South Korea · Taiwan
Node 15
Sydney
AWS ap-southeast-2
Oceania · Australia · New Zealand

Positions aren't fixed forever. A quarterly topology review uses latency heatmaps, demand concentration, and wallet-density maps to keep the anchors where the network needs them — with VXIR Labs holding final authority on every placement.

Authority earned through work, not tokens.

Governance is scoped tightly to network health and operator welfare, split across three bodies that can't reach into each other's domain. No one votes their way into protocol or security decisions.

Body 01 · Founding Authority

VXIR Labs

Holds protocol upgrades, security responses, API pricing, IR specification, and masternode operation. These are engineering and security calls that need speed and expertise — not subject to vote.

Body 02 · Operator Voice

Operator Assembly

Seven elected seats from active operators, awarded by Quality Score. Scope: reward fairness, uptime thresholds, expansion input, grievances. It advocates for workers — it can't touch architecture, security, or pricing.

Body 03 · Adopter Input

Protocol Advisory

Protocols that integrate VXIR advise on regional expansion and capacity. Advisory only. Labs weighs the input through a network-health lens and makes the final call.

A staged build on proven ground.

We don't switch on sixty nodes overnight, and we don't need to. The network comes up in three honest phases — each one self-funding the next, each one a normal infrastructure milestone.

Months 0–6Centralized

Two to three regions, Labs-operated

Prove the network mechanics end to end on a small, fully-controlled footprint. Grants and adjacent revenue bridge the early gap.

Months 6–12Expansion

Fifteen regions · 60-node backbone

Stand up the full regional topology and open the founding operator cohort. This is where the map above becomes real.

Month 12+Decentralization

External T3 operators · all three paths open

Qualified external operators come online, the 70/30 revenue split goes live, and the network opens to the financial, grind, and builder paths.

The vision is simple, and that's the point.

This isn't a moonshot. It's a tiered fleet of ordinary servers running batch compilation jobs, brought up in stages, funded as it grows. The compiler — the genuinely novel part — is already proven on mainnet. What's left is the disciplined, well-understood work of distributing it across regions and earning trust one tier at a time.

Target network launch: Q1 2027. Every step between here and there is a normal infrastructure milestone — nothing here requires an invention we don't already have in hand.