NexaRail — Controlled Validator Registration Open

Conversation Validation
1

NexaRail is a sovereign Layer 1 blockchain for decentralised railway settlement and payments, built with Cosmos SDK v0.47.17 and CometBFT v0.37.18. We’re opening controlled validator registration for our initial testnet.

What this is: We’re onboarding a small group of technical validators to test consensus stability, governance workflows, and infrastructure readiness. This is infrastructure testing only.

Chain config:

  • Chain ID: nexarail-testnet-1

  • Denom: unxrl | Ticker: NXRL | Prefix: nxr

  • 16 standard modules + 6 custom modules (fees, merchant, settlement, escrow, payout, treasury)

  • All live fund flags default to false — no real value flows

What this is NOT:

  • Not mainnet — no mainnet is live

  • Not a token sale — NXRL has not been offered for sale

  • Not an investment — testnet tokens have zero monetary value

  • Not permissionless — applications are reviewed

Who we’re looking for:

  • Linux server experience (required — no macOS/Docker Desktop)

  • Cosmos/Tendermint validator experience preferred

  • Ability to build from source and submit a gentx

  • Reliable communication during genesis coordination

How to apply:

Current status: Build/vet/test all pass — 14 packages. Docker rehearsal: 3 validators, height >20, peers ≥2. All 6 live fund flags default false. 3-7 validator slots available.

NexaRail is infrastructure under development. No mainnet launch date has been set. No token sale has occurred or is planned. Participation is for technical testing only.

1 Like
2

Hi Bradley,

Welcome to the forum.

Is there a whitepaper/litepaper for your project, or just some documentation about what it means to achieve?

3

Hi,

Thanks for the welcome.

At the moment we have project documentation, and I have now added a clearer litepaper-style overview for reviewers and validator operators.

The litepaper explains what NexaRail is aiming to achieve, the current technical status, the module architecture, the live-funds safety model, validator/testnet plans, and current limitations.

In short, NexaRail is being built as a Cosmos SDK / CometBFT sovereign L1 focused on payment infrastructure: merchant onboarding, settlement, escrow, payouts, treasury controls, and governance-gated live-funds functionality. The native denom is unxrl and the display ticker is NXRL.

Mainnet is not live, there is no token sale, and testnet tokens have no monetary value. We are currently in controlled testnet preparation, with external validator onboarding pending and live-funds flags disabled by default.

Litepaper:
docs/NEXARAIL_LITEPAPER.md

Short summary:
docs/NEXARAIL_LITEPAPER_SUMMARY.md

4

Thanks, will read that :+1:

1 Like
5

Quick NexaRail update.

Since my last post, I’ve been focused on making the project easier for technical reviewers and future validators to inspect rather than waiting on external validator interest.

Current status:

  • Mainnet is not live.

  • There is no token sale.

  • Testnet/devnet tokens have no monetary value.

  • External validators are still pending.

  • Live-funds flags remain disabled by default.

What has been completed:

  • Controlled Testnet RC1 package created and verified.

  • Local RC1 devnet launch package created.

  • Linux and macOS binaries built with SHA256 checksums.

  • Release verification passes: 37/37 checks.

  • Predeployment checks pass: 23/23.

  • Local 5-agent runtime evidence is complete.

  • Product-flow rehearsal passed: 487 pass / 0 fail.

  • REST readback parity is now 36/36 for custom query surfaces.

  • Local dashboard created for read-only devnet inspection.

  • Node.js and Python read-only clients added.

  • REST example scripts added.

  • Local write-flow examples added, dry-run by default.

  • Developer smoke checks pass.

The chain currently includes custom modules for:

  • merchant onboarding

  • fee configuration

  • settlement

  • escrow

  • treasury controls

  • payouts

The live-funds safety model is still conservative. These remain false by default:

settlement.live_enabled=false
settlement.treasury_routing_enabled=false
settlement.burn_routing_enabled=false
escrow.live_enabled=false
treasury.live_enabled=false
payout.live_enabled=false

What has been proven locally:

  • block production on a 5-agent local testnet

  • query/readback

  • bank transactions

  • governance proposal/voting flow

  • governance-controlled live-flag enable/disable cycle

  • 1-hour soak test

  • restart matrix

  • merchant/settlement/escrow/treasury/payout product flows

  • burn supply-delta evidence

  • custom REST readback

  • local devnet launch and reviewer workflow

What is still pending:

  • external validator cohort

  • gentx collection

  • final external testnet genesis

  • multi-machine/Linux rehearsal with independent operators

  • external audit

  • legal review

  • public controlled testnet launch

The goal right now is to keep improving the chain and developer/reviewer experience while external validators are pending. The latest work makes it possible to clone the repo, verify the RC1 package, launch a local devnet, query live flags, inspect module state through REST, and use simple Node/Python examples without needing a public network.

Relevant docs in the repo:

  • docs/NEXARAIL_LITEPAPER.md

  • docs/release/RC1_REVIEWER_README.md

  • docs/release/RC1_QUICKSTART.md

  • docs/release/RC1_EVIDENCE_SUMMARY.md

  • docs/developers/DEVELOPER_QUICKSTART.md

  • docs/api/REST_READBACK_ROUTES.md

This is still infrastructure testing and development, not a mainnet launch.

1 Like
6

Short update: NexaRail now has a verified Controlled Testnet RC1 package and a self-contained local devnet/reviewer workflow.

Still not mainnet, no token sale, and testnet/devnet tokens have no monetary value. External validators are still pending.

Recent progress:

  • RC1 package verified: 37/37 checks

  • Predeployment checks: 23/23

  • Product-flow rehearsal: 487 pass / 0 fail

  • REST readback parity: 36/36

  • Local 5-agent runtime evidence complete

  • Governance live-flag enable/disable proven locally

  • Local dashboard added

  • Node/Python read-only clients added

  • REST examples and write-flow examples added

Live-funds flags remain disabled by default, including settlement, escrow, treasury, payout, treasury routing, and burn routing.

Current focus: keep improving developer/reviewer usability while external validators are pending. The repo now includes a litepaper, RC1 reviewer docs, quickstart, evidence summary, REST docs, developer quickstart, local devnet launcher, and examples.

This is infrastructure testing and development only, not a public launch.