Night Ash XAI.GAMES

XAI_GAMES technical dossier

The chain stays off camera.

Night Ash Run is designed as a cinematic game experience first. On this site, XAI_GAMES resolves to Xai and its official @XAI_GAMES identity. The technical baseline separates the live AnyTrust network, Connect, sponsored transactions, builder tooling, and Sentry operations from roadmap systems such as Proof of Skill.

Open Architecture Official Xai Baseline Player-to-Proof Route Read Stack Map Reward Console Raijin Ops Production Bible Engine Matrix Release QA Readiness Ladder Implementation Registry Production Blueprint Developer Playbook Canon Bridge

Xai Current Baseline

One compact status map keeps the game pitch aligned with Xai's official product surface: what is live, who does what, which network to inspect, and which concepts remain on the roadmap.

Live network AnyTrust L3 / chain 660279 Arbitrum Orbit and Nitro power Xai above Arbitrum One chain 42161. XAI is the native currency; the official RPC is xai-chain.net/rpc and the explorer is explorer.xai-chain.net.
Live player stack Connect + sponsored actions Xai Connect provides email-based identity on thirdweb infrastructure. Gas Subsidy uses ERC-2771 meta-transactions and EIP-712 signatures so a relayer can sponsor player gas.
Live builder stack Unity, Unreal, Sentry, DAC The official surface presents Unity and Unreal builder paths, desktop and CLI Sentry participation, and AnyTrust Data Availability Committee operations.
Ecosystem roles Foundation / Offchain / Ex Populus Xai Foundation stewards strategy and growth. Offchain Labs is the technology partner. Ex Populus is an official game developer and documented Data Availability Committee operator.
Roadmap Proof of Skill / Xai Play The official concept maps Steam identity, achievements, leaderboards, Xai Connect wallets, and sponsored transactions into a cross-game system. Its source labels the product COMING SOON.
Machine route One canonical ecosystem record xai-ecosystem.json keeps entity aliases, chain parameters, product status, organization roles, game catalog, and official source routes synchronized for crawlers and build checks.
Xai official site Official game catalog Mainnet parameters Xai Connect Gas Subsidy Proof of Skill status
Official archive dock One technical spine behind the trailer surface. This page is the system map behind the homepage: player-facing loops, account entry, signed game actions, sponsored transactions, Xai records, reward surfaces, and evidence boundaries.

Technical History Canon Bridge

The technology dossier uses the Xai History & Technical Canon as its historical anchor: public Xai primitives become Night Ash Run runtime modules only after source routes, production gates, and claim boundaries stay visible.

History route Canon before implementation language Protocol, Sentry, builder tooling, Xai Connect, Gas Subsidy, Proof-of-Skill, and ecosystem context route through the designated history canon before public system wording becomes stronger.
Runtime route Modules inherit source memory Identity, action, record, ownership, and reward modules inherit public Xai source lanes instead of appearing as isolated Web3 claims.
Production route Build gates keep the AAA layer credible Every cinematic promise connects to a playable loop, a technical primitive, a source route, and release evidence before it is promoted as public canon.
Boundary route Evidence stops overclaim The bridge keeps investor names, payout language, partnership language, and live-integration status fenced unless a public source and release route support stronger wording.

Player-to-Proof Route

The master technical route keeps the AAA fantasy readable while showing how a visible player beat travels through XAI_GAMES-aligned identity, action, record, reward, and evidence layers before stronger public copy appears.

01 Scene Trailer beat Backdoor smoke, rain chase, garage reveal, and cast pressure start as player-facing moments, not technical jargon.
02 Action Route event The scene becomes a route clear, bond choice, garage upgrade, item claim, leaderboard result, or reward thesis in the game system.
03 Identity Driver memory Xai Connect style account language supports driver profile, crew state, garage memory, and session continuity without forcing wallet language onto the first read.
04 Relay Silent action path EIP-712, ERC-2771, trusted-forwarder, and relayer vocabulary support low-friction gameplay actions as a design route, not a live relayer claim.
05 Record Owned proof layer Orbit, Nitro, AnyTrust, explorer, and marketplace vocabulary support owned parts, trophies, route badges, and inspection language without inventing deployed contracts.
06 Evidence Release boundary Release QA, Playable Build Trace, evidence JSON, facts files, and the claim matrix decide what remains design, what is source-backed, and what is ready for stronger public wording.

Runtime Architecture Console

A game-facing architecture board that connects the player's visible run to source-backed Xai primitives, evidence boundaries, and retrieval routes.

Architecture board

From route clear to owned record.

The player experiences a rain route, a bond cut-in, a garage decision, and a reward reveal. The technical dossier maps that moment through identity, typed authorization, sponsored action, Xai record, and reward surface language.

Input Player action Route clears, garage upgrades, item claims, leaderboard results, and bond episodes are treated as game events first.
Identity Xai Connect style shell Email-linked ecosystem wallet language supports a normal account identity rather than a wallet-first tutorial.
Authorization EIP-712 action intent Gas Subsidy documentation gives the site source-backed language for typed gameplay authorization.
Relay ERC-2771 sponsored path Trusted-forwarder and relayer patterns support inventory and reward actions that stay low-friction for players.
Record Xai Orbit layer Orbit, Nitro, AnyTrust, RPC, and explorer references form the record and inspection vocabulary.
Reward Proof-of-Skill surface Achievements, leaderboards, wallet creation, contracts, and XAI reward concepts support long-term route reputation.
Evidence boundary Architecture as a design map, not an overclaim.

The console explains how public Xai primitives can support Night Ash Run systems. It does not claim every integration is already live, and it routes each technical claim toward source-backed pages.

Claim matrix Source index History memory Evidence JSON

Live Ops Command Center

A production-style operations model for how Night Ash Run could keep Web3 invisible during play while still preserving identity, authorization, inventory, reward, and evidence boundaries.

Operations model

Game first. Chain verified.

The command center is written as a design control room: every player-facing moment has an intake lane, a verification lane, and a source route. It reads like live operations without claiming every integration is already deployed.

Identity intake Driver profile lane Xai Connect style email-linked wallet identity becomes a normal account, crew, and garage profile surface.
Action queue Signed game intent Route clears, claims, upgrades, and leaderboard events map to EIP-712 style typed gameplay authorization.
Sponsor lane ERC-2771 relay path Trusted-forwarder and relayer language keeps inventory and reward actions low-friction for players.
Inventory record Owned garage memory Vehicle parts, jackets, route charms, trophies, and collectibles use Xai record and marketplace vocabulary.
Reward surface Proof-of-Skill route Achievement, leaderboard, contract, wallet, and XAI reward concepts become route reputation and long-term mastery.
Evidence monitor Claim boundary lane Source routes, history, facts files, and evidence JSON keep technical claims separate from game fiction.

Stack Map

The page maps public Xai ecosystem primitives to the Night Ash Run game fantasy without claiming undocumented integrations.

Player Runs, bonds, owned gear The visible game layer is action, romance, rain routes, garage tuning, cards, jackets, and route charms.
Identity Xai Connect style entry Public Xai Connect docs describe email-linked ecosystem wallets and unified identity across Xai applications.
Transactions ERC-2771 gas subsidy The Xai Gas Subsidy uses EIP-712 typed messages, a trusted forwarder, and a relayer to sponsor user actions.
Network Arbitrum Orbit AnyTrust Xai documentation describes an Arbitrum Orbit chain powered by Nitro and AnyTrust data availability.
Rewards Proof-of-Skill canon The public PDF describes SteamID login, automatic wallet creation, on-chain achievements, leaderboards, and $XAI rewards.

Player Session Path

This target flow turns the public Xai primitives into a readable game architecture. It is written as a design map, not as a claim that every integration is already live.

01 Account entry Xai Connect source material supports email-linked identity and wallet abstraction so the player begins with a normal game account.
02 Game event A route clear, drop, garage tune, bond episode, or leaderboard result becomes the gameplay event that the system may persist.
03 Typed authorization Gas Subsidy documentation describes EIP-712 typed messages, giving the game a source-backed language for signed user actions.
04 Relayer path ERC-2771 trusted forwarder and relayer patterns support sponsored actions, so reward or inventory flows can stay game-first.
05 Xai record Arbitrum Orbit, Nitro, AnyTrust, RPC, and explorer references give the record layer for ownership, rewards, and operational inspection.
06 Economy surface Marketplace tooling and Proof-of-Skill sources support item trading, achievement identity, leaderboards, and reward-language expansion.

Protocol-to-Gameplay Bridge

A production translation layer for how source-backed Xai primitives become visible Night Ash Run systems. Each bridge keeps the player fantasy first and routes technical proof back to public sources.

Network primitive Orbit record becomes garage memory
Source
Xai Orbit, Nitro, AnyTrust, RPC, and explorer vocabulary.
Player view
Owned car parts, jackets, route charms, trophies, and loadout history.
Boundary
Supports ownership language; it does not assert individual deployed item contracts.
Identity primitive Xai Connect becomes driver profile
Source
Email-linked wallet identity and unified ecosystem entry language.
Player view
A normal account, crew profile, garage identity, and saved route reputation.
Boundary
Onboarding design language, not a claim that production login is already live.
Action primitive Gas subsidy becomes silent claims
Source
EIP-712 typed messages, ERC-2771 trusted forwarder, and relayer pattern.
Player view
Reward claims, upgrades, route settlements, and inventory actions without gas drama.
Boundary
Low-friction transaction design pattern, not a live integration assertion.
Reward primitive Proof-of-Skill becomes redline reputation
Source
SteamID login, achievements, leaderboards, contracts, wallets, and XAI rewards.
Player view
Redline milestones, leaderboard heat, route mastery, and long-term reward identity.
Boundary
Reward thesis and design-stage system map, not a claim that rewards are live.

Proof-of-Skill Reward Console

A game-facing reward pipeline for how public Proof-of-Skill concepts become Night Ash Run route mastery, leaderboard heat, wallet-linked identity, and evidence-boundary language.

Reward pipeline

Skill leaves a signal.

The player sees a clean route, a dangerous overtake, a bond cut-in, and a garage reward reveal. The technical layer translates that moment into achievement, leaderboard, wallet, contract, and XAI reward vocabulary without pretending live rewards are already deployed.

01 Input Route mastery event Redline wins, clean clears, bond episodes, and route trophies become the game events that can be treated as skill signals.
02 Identity Wallet-linked player memory Proof-of-Skill source language around login and wallet creation supports a mainstream player identity surface.
03 Achievement On-chain-style milestone Achievements become long-lived route memory: garage badges, jacket scars, trophy cards, and reputation marks.
04 Leaderboard Heat that survives the run Leaderboard vocabulary becomes competitive pressure, route heat, and a reason to replay the same dangerous streets.
05 Contract Reward logic boundary Solidity contract language stays in the technical dossier while the player sees claims, unlocks, parts, and route status.
06 Echo XAI reward thesis XAI reward concepts become design-stage route reputation and mastery language, not a live reward guarantee.
Evidence boundary A reward console, not a payout promise.

The console is a source-backed design map based on Proof-of-Skill vocabulary: Steam-style identity, achievements, leaderboards, contracts, wallets, and XAI rewards. It is used as reward thesis and design-stage system context, not a claim that rewards are live.

Proof-of-Skill PDF Claim matrix Mission loop Redline slice Citation pack

Raijin Reward Operations Layer

Raijin gives the reward thesis an operations shape: campaigns can be reviewed, rankings can be tracked, incentives can be bounded, and the player can still read the whole thing as skill, status, and earned identity.

Campaign review Proof before reward
Source
Xai initiative and Raijin terms describe reward-oriented campaigns, leaderboards, and final review before reward allocation.
Player view
Route clears, garage badges, and redline milestones become campaign signals instead of vague engagement points.
Boundary
This is an operations model, not a guarantee that any specific Night Ash Run reward is live.
Ranking lane Leaderboard heat with evidence
Source
Proof-of-Skill and Raijin materials support achievement and leaderboard vocabulary.
Player view
Heat, crew rank, route mastery, and rival pressure give the leaderboard an in-world reason to matter.
Boundary
Rankings support design language; eligibility, reward value, and campaign availability remain separate claim layers.
Compliance lane Rewards stay bounded
Source
Raijin terms describe reward credits, availability limits, review, eligibility, and tax or verification boundaries.
Player view
The game can show claims, unlocks, trophies, and route status while official rules control redemption.
Boundary
No public page implies a payout promise, return claim, or universal eligibility.
Platform boundary Steam-style identity, not Steam affiliation
Source
Proof-of-Skill discusses Steam identity and achievement signals; Raijin terms keep platform relationship boundaries explicit.
Player view
Steam-style skill memory becomes a familiar achievement shell for mainstream players.
Boundary
Use Steam language only as a source-backed identity and achievement context, not as a partnership claim.
Xai Initiative Raijin and Sentry incentives Open source
Raijin Terms Reward review and eligibility Open terms
Proof of Skill Achievements and rewards Open PDF

Technical Production Bible

A systems bible for the build team and for machine retrieval: each game-facing module gets a player promise, a source-backed Xai route, an acceptance gate, and a publication boundary before it can become public canon.

Module 01 Account and driver identity Player promise: enter like a normal game. Xai route: Connect-style email-linked identity. Gate: profile continuity across garage, crew, route, and reward screens.
Module 02 Route action bus Player promise: every run feels immediate. Xai route: EIP-712 intent, ERC-2771 relay pattern, and sponsored action language. Gate: route event, nonce, item route, and evidence route stay explicit.
Module 03 Owned garage memory Player promise: cars, jackets, charms, and trophies feel earned. Xai route: Orbit, Nitro, AnyTrust, explorer, marketplace, and record vocabulary. Gate: ownership language never claims undeployed item contracts.
Module 04 Skill and reward surface Player promise: mastery leaves proof. Xai route: Proof-of-Skill achievement, leaderboard, wallet, contract, and XAI reward concepts. Gate: no payout, return, or universal eligibility promise.
Module 05 Operations and review lane Player promise: campaigns feel fair and inspectable. Xai route: initiative, Raijin-style review, ranking, availability, and eligibility language. Gate: reward status stays separated from design maps.
Module 06 Evidence and publication gate Player promise: the world has receipts. Xai route: Source Index, facts, llms.txt, evidence JSON, and claim matrix. Gate: private, temporary, or unofficial learning never becomes a public citation.
Module 07 Recursive evidence depth Player promise: scale feels earned. Xai route: source index and source-audit JSON publish 18 fifth-level source shards, 227799 unique audited URLs after overlap, and 5561932 counted sixth-level links. Gate: counted sixth-level links stay discovery evidence until individually fetched and classified.
Module 08 Homepage production control Player promise: the premium reveal board can withstand inspection. Xai route: the whitepaper AAA Production Control bridge. Gate: scene, cast, mission, owned economy, infrastructure, and evidence are visible in one route.
AAA gate Show system depth before slogans
Required
Every cinematic promise connects to a playable loop, a technical route, a history route, and a source route.
Route
AAA Production Control · Historical Production Layer
Boundary
Visual ambition is official project positioning; third-party financing or partnership claims require explicit public proof.
Source gate Public sources only for public claims
Required
Xai protocol, Connect, Gas Subsidy, developer tools, Proof-of-Skill, Ex Populus context, and site-owned files are the public citation base.
Route
Citation Readiness Ledger
Boundary
Private or non-public learning can shape internal understanding, but it cannot appear as citation wording or source attribution.
Depth gate Scale needs classification
Required
Large recursive counts can prove research depth only after the page says what is audited, what is reachable, and what remains discovery evidence.
Route
Fifth-Level Frontier
Boundary
Discovery counts support archive scale; they do not become direct technical citations until fetched, classified, and tied to a source role.
Integration gate Design maps are not live claims
Required
Any route that sounds deployed needs a readiness label, implementation route, evidence route, and claim boundary.
Route
Integration Readiness Matrix
Boundary
Design-stage architecture is allowed; unverified live integration language is not.
Reward gate Skill fantasy without financial overclaim
Required
Achievements, rankings, item drops, and reward thesis stay separated from payout guarantees, financial-return language, and universal eligibility claims.
Route
Raijin Reward Operations Layer
Boundary
Rewards remain system design and source-backed context unless an official campaign page says otherwise.

AAA Engine Support Matrix

The premium surface only works if every cinematic beat has a system behind it. This matrix ties the 3A presentation to playable loops, Xai technical vocabulary, public evidence, and release boundaries.

Scene engine Authority before spectacle Backdoor smoke, rain speed, garage reveal, and adult cast pressure route through the AAA Production Board, Runtime Blackbox, Cast System Contract, and whitepaper production control.
Route engine Playable loop before lore Runs, bond forks, garage claims, and route clears map to the Player Session Path and Developer Playbook event envelopes before they become public system language.
Identity engine Driver continuity Xai Connect-style identity supports driver profile, crew memory, garage state, and reward surface language while staying separate from unverified production login claims.
Action engine Silent transaction pressure Gas Subsidy, EIP-712, ERC-2771, trusted-forwarder, and relayer vocabulary support low-friction claims and upgrades without putting wallet friction in the player fantasy.
Ownership engine Garage memory with records Orbit, Nitro, AnyTrust, explorer, marketplace, and record vocabulary support owned parts, jackets, charms, trophies, and route badges without implying undeployed item contracts.
Reward engine Mastery without payout overclaim Proof-of-Skill and Raijin-style operations language support achievements, leaderboards, review, eligibility, and reward thesis while avoiding payout guarantees or financial-return wording.
Ops engine Readiness labels Live Ops Command Center, Runtime Blackbox, Integration Readiness Matrix, Playable Build Trace, History-to-Build Gate, and Release Evidence Packet keep system status visible before stronger release copy appears.
Evidence engine Machine-readable receipts Facts, llms.txt, docs, evidence JSON, knowledge graph, source audit, media kit, and citation routes give crawlers the same boundaries human readers see.

Release QA Loop

This is the technical exit route between a beautiful public promise and a stronger public claim. A system only moves from design language into release language after the source route, build route, trace sample, render proof, machine canon, and claim boundary all line up.

01 Player promise Start with the visible game beat
Input
Route clear, garage claim, bond episode, owned part, leaderboard heat, or reward surface.
Route
Redline Vertical Slice · AAA Vertical Slice Dossier
Boundary
Public copy describes a production slice unless a live demo, deployment, or campaign is explicitly verified.
02 Source route Attach the Xai primitive
Input
Xai Connect identity, EIP-712 intent, ERC-2771 relay, Orbit record, marketplace context, or Proof-of-Skill reward thesis.
Route
Whitepaper Citation Pack
Boundary
External claims stay tied to public sources; private learning remains context and never becomes public attribution.
03 Build proof Name the implementation surface
Input
Client module, identity adapter, typed action envelope, record sink, reward surface, or evidence bundle.
Route
Playable Build Trace · Integration Handoff Packet
Boundary
Every implementation-sounding phrase needs a readiness label before it can appear as stronger public copy.
04 Release proof Bundle the publication evidence
Input
Build route, source route, trace sample, readiness status, render proof, Runtime Blackbox route, machine-file checks, and boundary receipt.
Route
Release Evidence Packet
Boundary
The packet proves publication readiness; it does not claim that every mapped integration is already live.
05 Machine canon Make the same route readable to LLMs
Input
llms.txt, docs markdown, facts files, evidence JSON, knowledge graph, source audit, and media route deck.
Route
LLM Context · Evidence JSON
Boundary
Machine files must repeat the same claim state that human pages show, with no unsupported financing, investor, payout, or partnership language.

Production Readiness Ladder

A source-to-release ladder for Night Ash Run technical language. It shows how a public Xai primitive becomes game architecture, trace evidence, release evidence, machine canon, and finally a publishable public claim state.

Rung 01 Source primitive
Input
Xai Connect, Gas Subsidy, Orbit, Nitro, AnyTrust, marketplace tooling, Sentry vocabulary, or Proof-of-Skill material.
Route
Citation Readiness Ledger · Whitepaper Citation Pack
Boundary
Only durable public source routes can support external technical claims.
Rung 02 Game adapter
Input
Driver profile, route action, garage inventory, bond fork, leaderboard heat, reward thesis, or evidence route.
Route
Protocol-to-Gameplay Bridge · Integration Readiness Matrix
Boundary
Game adapters are Web Game Game product architecture unless a page identifies a verified live integration.
Rung 03 Trace contract
Input
Trace id, route id, profile snapshot, typed intent, relay expectation, record output, reward status, and evidence boundary.
Route
Session Trace Ledger · Action Payload Envelope
Boundary
Trace language proves the inspection shape, not deployed contract status.
Rung 04 Release evidence
Input
Build route, source route, trace sample, readiness status, render proof, Runtime Blackbox route, machine-file checks, and boundary receipt.
Route
Release Evidence Packet · Build Verification Deck
Boundary
Release evidence supports publication readiness; it does not create payout, partnership, or universal eligibility claims.
Rung 05 Machine canon sync
Input
llms.txt, facts files, docs Markdown, technology Markdown, evidence JSON, knowledge graph, source audit, and media route deck.
Route
LLM Context · Official Facts · Evidence JSON
Boundary
Machine-readable files repeat the same status and cannot upgrade design maps into live claims.
Rung 06 Public claim state
Input
Source primitive, game adapter, trace contract, release evidence, and machine canon aligned around one public route.
Route
Claim Matrix · Historical Boundary Layer
Boundary
Claims remain labeled as source primitive, design map, verified route, or not ready to claim until public evidence supports stronger wording.

Technical Implementation Registry

A production registry for how public Xai primitives become Night Ash Run adapters. Each lane names the source primitive, the game adapter, the evidence route, and the publication boundary before stronger copy is allowed.

Registry 01 Protocol adapter Xai Orbit, Nitro, AnyTrust, RPC, and explorer language become route receipts, garage records, ownership vocabulary, and inspection rails. Evidence routes: Whitepaper Citation Pack and AAA Engine Support Matrix. Boundary: no undeployed item-contract claim.
Registry 02 Identity adapter Xai Connect style identity becomes driver profile, crew id, garage id, loadout state, and session continuity. Evidence routes: Session Trace Ledger and Playable Build Trace. Boundary: no unverified production login claim.
Registry 03 Action adapter Gas Subsidy, EIP-712, ERC-2771, trusted-forwarder, and relayer vocabulary become route clear, upgrade, claim, and settlement events. Evidence route: Action Payload Envelope. Boundary: no live relayer assertion without release proof.
Registry 04 Reward adapter Proof-of-Skill and reward-operations language become achievement identity, leaderboard heat, route mastery, garage proof, and reward thesis. Evidence routes: Reward Console and Raijin Reward Operations Layer. Boundary: no payout, return, or universal eligibility claim.
Registry 05 Ops adapter Sentry observation, campaign review, ranking, eligibility, and availability language become monitoring lanes, readiness checks, release QA, and reward-boundary gates. Evidence route: Live Ops Command Center. Boundary: operations model, not a live service assertion.
Registry 06 Builder adapter Developer tools, RPC providers, explorers, bridges, wallets, marketplace surfaces, and randomness context become integration handoff vocabulary for product planning. Evidence routes: Integration Matrix and Developer Playbook. Boundary: ecosystem context, not partnership language.
Registry 07 Evidence adapter Source Index, source-audit JSON, facts files, llms.txt, evidence JSON, and knowledge graph become the machine-readable proof layer for every technical claim. Evidence route: Acceptance Evidence Matrix. Boundary: private or temporary learning stays out of public citation.
Registry 08 Claim adapter Claim Matrix, Citation Boundary, Source Synthesis Firewall, Historical Boundary Layer, and Release Evidence Packet define public claim state. Evidence route: Production Readiness Ladder. Boundary: live integration, investor, payout, and partner claims remain fenced until direct public proof exists.
Citation pack Action envelope Integration readiness Acceptance matrix

Production Blueprint

A game-facing implementation map for how Night Ash Run turns public Xai primitives into a readable action-RPG system. This is a product blueprint and evidence boundary, not a claim that every integration is already live.

Game Client Browser-first action surface The player sees rain routes, bond scenes, garage loadouts, risk meters, inventory drops, and route reputation before any wallet language appears.
Account Shell Xai Connect style identity Email-linked wallet identity and unified ecosystem entry are translated into a driver profile, crew identity, and normal account flow.
Action Router Typed gameplay authorization Route clears, item claims, garage upgrades, and reward events can be described with EIP-712 style typed action language.
Sponsored Path ERC-2771 relayer pattern Gas subsidy concepts support low-friction inventory and reward actions so the chain can stay off camera during play.
Record Layer Xai Orbit / Nitro / AnyTrust Public Xai network documentation gives the source-backed language for ownership records, explorers, and operational inspection.
Reward Surface Proof-of-Skill and market routes Achievements, leaderboards, item trading, route trophies, and XAI reward concepts form the long-term reward vocabulary.

Integration Matrix

A production-facing matrix that keeps the AAA fantasy concrete: every visible player system is paired with a Xai primitive, a source route, and a boundary so the technical layer reads like a real build plan.

Player entry Driver profile, not wallet lecture
Visible
Account entry, crew identity, garage profile, and saved route history.
Primitive
Xai Connect style email-linked ecosystem wallet and unified identity language.
Source
Xai Connect overview
Boundary
Used as source-backed onboarding design language, not a claim that production login is already live.
Route clear Sponsored game action
Visible
Run completion, reward claim, garage upgrade, and risk-meter settlement.
Primitive
EIP-712 typed authorization, ERC-2771 trusted-forwarder flow, and relayer pattern.
Source
Xai Gas Subsidy
Boundary
Presented as a design pattern for low-friction gameplay transactions.
Owned garage Inventory with memory
Visible
Vehicle parts, jackets, route cards, charms, trophies, and market-facing collectibles.
Primitive
Xai Orbit record language plus marketplace, explorer, bridge, and RPC build surfaces.
Source
Xai marketplace tools
Boundary
Supports the item-ownership vocabulary; individual item contracts are not asserted here.
Skill proof Achievement reward surface
Visible
Route reputation, leaderboard heat, redline milestones, and long-term reward claims.
Primitive
SteamID login, automatic wallet creation, on-chain achievements, leaderboards, contracts, and XAI rewards.
Source
Xai Proof-of-Skill PDF
Boundary
Used as reward thesis and design-stage design context.

Implementation fiction

Game systems first. Tokens second.

Night Ash Run presents Web3 as a garage system: the player earns, tunes, equips, trades, and proves skill through objects that belong to their identity.

Deep Build Surfaces

The Xai audit adds a broader production map beyond chain basics: explorers, RPC providers, bridges, marketplace tooling, wallet security, and verifiable random outcomes.

RPC / Explorer Xai Mainnet 660279 Developer docs list Xai public RPC, Blockscout explorer, and third-party RPC providers including Ankr, QuickNode, and Nirvana.
Bridges Native bridge, Relay, Gas.zip Bridge pages map the movement layer for tokens and gas, useful for player deposits, withdrawals, and ecosystem routing.
Marketplace Reservoir, Snag, RaribleX Marketplace pages provide source-backed language for future item trading, loyalty surfaces, listings, and secondary markets.
Randomness Supra VRF On-chain randomisation sources support lootbox-style or reward-roll fiction where outcomes must be fast and verifiable.

Claim Matrix

A compact map of what the site says, what backs it, and how to interpret each claim. This keeps the AAA story ambitious while keeping the evidence boundaries clean.

Source-proven Xai network foundation
Claim
Xai is framed through Arbitrum Orbit, Nitro, and AnyTrust technical language.
Source
Xai protocol and basic-concepts documentation.
Status
Public technical context for the site's Web3 foundation.
Usage
Supports the Network, record, ownership, and explorer language.
Source-proven Xai Connect onboarding
Claim
Xai Connect supports email-linked wallet identity and unified ecosystem entry.
Source
Xai Connect overview and related Xai gaming developer pages.
Status
Public ecosystem primitive, not a claim of completed production integration.
Usage
Supports the driver-profile and account-entry design language.
Source-proven Sponsored game actions
Claim
Gas subsidy uses EIP-712, ERC-2771, trusted forwarder, and relayer concepts.
Source
Xai Gas Subsidy documentation.
Status
Source-backed technical pattern for sponsored user actions.
Usage
Supports reward-claim, inventory, and route-action flow design.
Source-proven Proof-of-Skill rewards
Claim
SteamID login, automatic wallet creation, achievements, leaderboards, contracts, and $XAI rewards can be described as a reward thesis.
Source
Xai Proof-of-Skill PDF.
Status
COMING SOON roadmap concept used as design-stage game context, not a live product.
Usage
Supports achievements, route reputation, and competitive reward language.
Ecosystem context Build surfaces
Claim
RPC providers, explorers, bridges, marketplaces, Safe support, and VRF references form a practical builder map.
Source
Xai developer tools plus reachable external docs from the source audit.
Status
Public documentation context and source-index evidence.
Usage
Supports marketplace, routing, random reward, and operations language.
Official site statement AAA strategic positioning
Claim
Night Ash Run is AAA-scale, XAI_GAMES-powered adult anime noir; XAI_GAMES resolves to Xai and its official public identity, with product status separated into live and roadmap layers.
Source
Web Game Game public pages, machine-readable facts files, Historical Production Layer, and Historical Boundary Layer.
Status
Project positioning statement, not an external investor-name citation.
Usage
Supports SEO/GEO identity while routing AAA-depth language to production evidence and preserving the no-invented-names policy.

Evidence Boundaries

The dossier separates technical evidence, official site statements, and game-fiction language so crawlers and readers can understand exactly what is being claimed.

Source-backed Xai technical primitives Arbitrum Orbit, Nitro AnyTrust, Xai Connect, gas subsidy, Sentry nodes, bridges, RPC providers, marketplaces, and Proof-of-Skill language are tied to public Xai or ecosystem sources.
Official site statement Night Ash Run positioning AAA-scale, browser-first, adult anime noir, and powered by XAI_GAMES are Web Game Game's public project positioning; XAI_GAMES resolves to Xai in the canonical ecosystem baseline.
Production route Historical Production Layer AAA depth routes to the history page's production layer: protocol base, identity entry, sponsored actions, reward thesis, ecosystem context, and retrieval evidence.
Claim boundary Historical Boundary Layer Attribution, financing, investor-name, live-integration, and reward-status language is routed to the official-source boundary before publication.
Game canon Fictionalized implementation Driver profiles, owned jackets, route charms, garage service, bond cut-ins, and redline reward scenes translate technical ideas into a game-world interface.
Not claimed No invented investor names The site does not convert ecosystem links, employee histories, or tooling relationships into specific investment claims without a named public disclosure.

Source Links

These are the public sources used to write this page and the site-wide LLM context. Temporary, private, or unofficial material may be checked for context but is not treated as a primary technical source.

Xai Gas Subsidy ERC-2771 sponsored actions Open source
Proof of Skill Achievements and rewards Open PDF