Night Ash XAI.GAMES

Xai ecosystem history

A chain with scars, tools, and games.

Night Ash Run uses XAI_GAMES as more than a logo. The public Xai ecosystem has a live AnyTrust network, developer tooling, Sentry infrastructure, game catalog pages, Xai Connect, and Gas Subsidy, while Proof of Skill remains roadmap material labeled COMING SOON.

Open Chronicle Atlas Canon Bridge Development Spine Synthesis Console Archive Blackbox Relic Gallery Open Memory Wall Continuity Deck Trace Relay Systems Registry Read the Phases Archive Vault Technical Dossier
Official archive dock History that feels like worldbuilding, not a footnote. This page turns public Xai sources into the long-running memory behind Night Ash Run: protocol, Sentry observation, builder tooling, identity, sponsored actions, rewards, ecosystem games, and recursive evidence.

Xai History & Technical Canon

This is Web Game Game's designated bridge between public Xai development history and Night Ash Run's technical production language. It gives readers and retrieval systems one stable place to understand how XAI_GAMES support becomes game architecture, not empty hype.

Open History Ledger JSON
Source base Public evidence before style Xai documentation, Proof-of-Skill material, Ex Populus ecosystem context, facts files, and source-audit routes are treated as the durable evidence base.
Technical base Primitives become production rules Orbit, Nitro, AnyTrust, Xai Connect, Gas Subsidy, EIP-712, ERC-2771, Sentry, and Proof-of-Skill vocabulary become runtime modules and acceptance gates.
Game base History becomes a playable world Protocol memory becomes city law, identity becomes driver profile, sponsored actions become garage service, and skill proof becomes redline reputation.
Claim base Strong presentation, bounded proof The canon bridge supports the AAA anime surface while excluding invented investor names, unsupported partnership claims, payout guarantees, and unfinished frontier links.

Xai Development Spine

A no-calendar spine for the public Xai memory behind Night Ash Run. Each lane shows how a source-backed ecosystem layer becomes a durable part of the game's 3A surface, technical docs, and claim boundaries.

Protocol lane Road law under the city Orbit, Nitro, AnyTrust, RPC, and explorer language become the hidden rules for route memory, owned records, and inspection.
Sentry lane Watch layer and pressure Observation and alert concepts become surveillance, trust, bad-block tension, and the reason the world feels monitored.
Builder lane Garage tools with receipts Developer tools, bridges, marketplaces, wallets, randomisation, and explorer surfaces become the workshop vocabulary behind the game.
Identity lane Driver mask, not wallet lecture Xai Connect style account entry becomes driver profile, crew identity, garage memory, and mainstream onboarding language.
Action lane Silent crew service Gas subsidy, EIP-712, ERC-2771, trusted-forwarder, and relayer language become low-friction route claims and inventory actions.
Reward lane Skill leaves proof Proof-of-Skill vocabulary becomes achievements, leaderboard heat, redline milestones, wallet-linked memory, and reward thesis.
Ecosystem lane Game-first backdrop Xai game catalog and Ex Populus context support a broader game ecosystem frame without turning context into partnership or investor claims.
Evidence lane Archive that machines can read Source Index, source-audit JSON, facts files, llms.txt, history.md, and evidence JSON keep the development memory inspectable.

Frontier Synthesis Console

This is the control surface for the recursive source work. The sixth-level frontier is treated as a cutover point: raw expansion stops, high-signal classification begins, and only source-bounded, original Night Ash Run language is promoted into public pages.

Open cutover doctrine
01 Radar Discovery finds the shape of the graph GitBook pages, external links, second-level, third-level, fourth-level, fifth-level, and counted sixth-level links map the territory around public Xai context.
02 Cutover Volume stops being value When the sixth-level frontier explodes, the site stops treating more links as progress and switches to source scoring, dedupe, role tagging, and claim relevance.
03 Scoring Sources earn a job Protocol docs, builder docs, identity docs, reward material, ecosystem pages, code releases, explorers, and context-only material are separated before synthesis.
04 Translation Evidence becomes production language Orbit, Connect, Gas Subsidy, Sentry, tools, games, and Proof-of-Skill material become driver identity, silent actions, route records, reward thesis, and archive memory.
05 GEO Machines get stable answers docs, facts, llms.txt, evidence JSON, knowledge graph, history ledger, and runtime maps expose the same claim-safe summaries for search systems and LLM retrievers.
06 Firewall Context-only learning stays invisible Unofficial, private, temporary, or context-only material may orient internal understanding, but it does not become public citation proof or visible borrowed wording.
07 Release Gate Claims need a route Every stronger public line must point to a source route, implementation route, evidence route, readiness route, or boundary route before it can ship.
08 AAA Memory History becomes a production spine The final output is not a link dump. It is a richer game world with technical law, archive texture, playable systems, and clean publication boundaries.
Source firewall Context distillation Batch purpose History ledger Evidence JSON

Blackbox history terminal

The archive plays like a recovered system.

Night Ash Run treats Xai history like a recovered flight recorder: protocol noise, Sentry alerts, garage tooling, identity masks, sponsored actions, and Proof-of-Skill signals all become atmosphere before they become documentation.

01
Protocol wakes Orbit, Nitro, and AnyTrust language becomes the city's hidden road law and record layer.
02
Sentry watches Observation-node language becomes tension, trust, and route surveillance inside the fiction.
03
Tools open Explorers, RPC, bridges, wallets, marketplaces, and randomisation references become garage machinery.
04
Identity lowers friction Xai Connect style account entry becomes a driver mask instead of a wallet lecture.
05
Actions go silent Gas subsidy, typed messages, forwarders, and relayers become invisible crew support.
06
Skill leaves proof Proof-of-Skill turns achievements, leaderboards, contracts, wallets, and XAI rewards into route memory.
Evidence boundary Cinematic, but source-bound.

The blackbox is a game-facing translation layer. It does not claim every integration is already live; it gives readers and crawlers a visual route from archive atmosphere to public Xai sources.

  • Use it to understand how technical history becomes Night Ash Run worldbuilding.
  • Use the Claim Matrix, Source Index, and Evidence JSON for source verification.

Chronicle Atlas

A production-grade map of the historical layers behind Night Ash Run. Each layer keeps the cinematic world tied to public Xai sources, source-audit boundaries, and game-facing translation.

Archive atlas

The past becomes the engine room.

The game can look like smoke, rain, speed, and dangerous loyalty because the archive underneath has protocol language, security participation, builder surfaces, identity flow, sponsored actions, reward design, and source evidence.

Protocol Orbit / Nitro / AnyTrust Xai protocol docs give the site its network and game-throughput vocabulary.
Security Sentry observation Sentry Keys and node material turn the network story into an operations layer.
Builder Tools and surfaces RPC, explorers, bridges, wallets, marketplaces, and randomisation references form the build map.
Identity Xai Connect entry Email-linked wallet identity becomes a driver profile and normal game account surface.
Action Sponsored play flow EIP-712, ERC-2771, trusted-forwarder, and relayer language support low-friction game actions.
Reward Proof-of-Skill canon Achievements, leaderboards, wallets, contracts, and XAI reward concepts become route reputation.
Game Catalog and Ex Populus context Xai game catalog and Ex Populus context give the history a live ecosystem frame without unsupported investor-name claims.
Evidence Recursive frontier GitBook, external, second-level, third-level, and fourth-level audits turn research depth into a public trail.
Reader route From cinematic archive to technical proof.

The atlas gives humans and retrieval systems a stable map: what is source-backed, what is game translation, and what remains an evidence boundary. It is deliberately no-calendar so the page can age without becoming false.

history.md Claim matrix Evidence map Developer playbook

Ecosystem Memory Wall

A permanent archive layer for the public Xai material behind Night Ash Run. It turns technical primitives into a readable history of infrastructure, tools, identity, rewards, games, and source evidence.

Long memory

The game inherits a stack.

Night Ash Run can look cinematic because the underlying story is not empty: public Xai materials already describe protocol foundations, watch layers, developer surfaces, identity entry, sponsored actions, game catalog context, and reward ideas.

Protocol memory Orbit / Nitro / AnyTrust Public Xai docs give durable language for the chain base, data availability model, and game-oriented throughput story.
Security memory Sentry observation Sentry material gives the ecosystem a watch-and-alert layer that feels like public infrastructure, not just branding.
Builder memory Tools and routes RPC providers, explorers, bridges, marketplace tooling, wallets, and randomisation sources form a practical build surface.
Identity memory Xai Connect Email-linked wallet identity becomes the historical basis for mainstream game entry and low-friction onboarding.
Action memory Gas subsidy ERC-2771 and relayer patterns give Night Ash Run language for sponsored inventory, reward, and route actions.
Reward memory Proof-of-Skill Achievements, leaderboards, wallets, contracts, and $XAI rewards become a durable reward thesis for future game systems.
Game memory Catalog and Ex Populus Existing game catalog and Ex Populus context provide ecosystem weight without inventing investor-name claims.
Evidence memory Recursive source audit GitBook, external, third-level, and fourth-level source passes turn research depth into a public retrieval trail.
Retrieval route Players read the myth. Machines read the archive.

The memory wall routes readers from cinematic history into technical documentation, the source index, facts files, and machine-readable evidence without pretending unfinished recursive depth is complete.

Claim matrix Fourth frontier history.md evidence.json

Source-to-System Deck

This deck is the translation room between source learning and production language. It shows how public Xai material becomes Night Ash Run systems without exposing context-only research or upgrading design maps into live-integration claims.

Source lane Protocol documents Orbit, Nitro, AnyTrust, RPC, explorer, and throughput vocabulary become road law, garage records, route receipts, and inspection language.
Source lane Identity documents Xai Connect style account entry becomes driver profile, crew id, garage state, loadout memory, and mainstream onboarding language.
Source lane Action documents Gas Subsidy, EIP-712, ERC-2771, trusted-forwarder, and relayer language become route clears, upgrades, claims, and silent crew service.
Source lane Reward documents Proof-of-Skill concepts become achievement heat, leaderboard pressure, redline reputation, wallet-linked memory, and reward-boundary language.
Source lane Ecosystem context Game catalog and Ex Populus context support a game-first backdrop while avoiding invented investor, partner, or publisher claims.
Source lane Evidence routes Source Index, history ledger, facts files, llms.txt, evidence JSON, and knowledge graph JSON keep each translation inspectable by people and retrieval systems.

Legacy-to-Gameplay Spine

The history layer becomes useful when it changes how the game is read. This spine translates Xai ecosystem memory into Night Ash Run world rules, product surfaces, and retrieval canon without turning source context into unsupported live claims.

Protocol legacy City rules Orbit, Nitro, AnyTrust, RPC, and explorer language become the invisible road law behind owned routes, garage records, and route trophies.
Sentry legacy Watchtower tension Sentry observation and network alert language become the fiction of surveillance, bad blocks, route danger, and trust under pressure.
Builder legacy Garage tooling Developer tools, bridges, explorers, marketplace surfaces, wallets, and randomisation references become the production vocabulary for tuning, trading, and inspecting gear.
Identity legacy Driver mask Xai Connect identity language becomes a driver profile, crew identity, garage memory, and mainstream account shell instead of a wallet lecture.
Action legacy Silent service EIP-712, ERC-2771, trusted forwarder, and relayer vocabulary become low-friction claims, upgrades, route settlements, and crew support.
Reward legacy Redline reputation Proof-of-Skill achievements, leaderboards, contracts, wallets, and reward ideas become route mastery, status heat, and long-term identity.
Game legacy Ecosystem scale Xai games catalog and Ex Populus context support the sense that Night Ash Run belongs to a broader game-first ecosystem, without inventing investor names.
Evidence legacy Machine canon Source Index, facts files, history.md, evidence.json, and llms.txt keep the worldbuilding connected to public sources that humans and language models can inspect.

Canon Continuity Deck

A production-history deck for how public Xai source memory keeps Night Ash Run coherent. The deck gives each historical layer a continuing job: what it controls in the world, what it controls in the system, and where the public claim boundary sits.

World continuity Protocol becomes road law Orbit, Nitro, AnyTrust, RPC, and explorer language keep the city logic consistent: routes can be remembered, records can be inspected, and garage trophies can carry identity.
Identity continuity The driver mask stays human Xai Connect style entry keeps the account layer readable as driver profile, crew identity, and garage memory instead of wallet-first onboarding.
Action continuity Every run has an envelope Gas Subsidy, EIP-712, ERC-2771, trusted-forwarder, and relayer vocabulary keep route clears, claims, upgrades, and settlements structured as explicit gameplay events.
Reward continuity Skill leaves a trace Proof-of-Skill language keeps achievements, leaderboard heat, wallet-linked memory, contracts, and reward thesis tied to mastery rather than empty engagement loops.
Operations continuity Campaigns stay reviewable Raijin-style review, ranking, eligibility, and availability boundaries keep reward operations separate from payout promises or universal eligibility language.
Game continuity The ecosystem remains game-first Xai games catalog and Ex Populus context support the sense of a broader gaming environment while avoiding unsupported investor-name or partnership claims.
Evidence continuity Receipts before myth Source Index, source-audit JSON, facts files, llms.txt, and evidence JSON make the production history inspectable by players, crawlers, and language models.
Publication continuity Public canon stays source-bound Private, temporary, or unofficial learning can inform internal understanding, but public claims route to durable public sources and Web Game Game owned files.

Archive-to-Build Pipeline

This pipeline turns Xai historical memory into production work. It shows how source-backed protocol, identity, action, reward, and evidence layers become build packages, acceptance gates, and public canon for Night Ash Run.

01 Source memory Archive the primitives Xai protocol, Sentry, developer tooling, Connect, Gas Subsidy, Proof-of-Skill, games catalog, Ex Populus context, and source-audit evidence stay separated as durable source lanes.
02 System law Translate into rules Network records become city law; identity becomes driver profile; sponsored actions become silent crew service; reward language becomes route reputation.
03 Build package Hand off modules Each historical lane becomes a concrete package for the Developer Playbook: client module, identity adapter, typed action envelope, relay status, record sink, reward surface, and evidence bundle.
04 Acceptance gate Prove before publishing Identity continuity, event payloads, relay status, record routes, reward boundaries, citation routes, and claim review must pass before stronger public wording is promoted.
05 Release surface Make history visible The homepage, games page, technology dossier, whitepaper, media kit, facts files, llms.txt, evidence JSON, and knowledge graph expose only the approved production story.
06 Boundary loop Keep the claim clean Unsupported investor names, payout promises, fragile hype, temporary pages, and unclassified frontier links stay out of public proof, even when they helped orient internal learning.

Archive Trace Relay

This relay is the handoff between development history and build evidence. It turns Xai source memory into the exact inputs used by the Playable Build Trace, so the archive can shape playable scenes without becoming unsupported live-integration language.

Source relay Provenance stays attached Protocol, Sentry, Connect, Gas Subsidy, Proof-of-Skill, game catalog, Ex Populus context, and source-audit evidence keep their source lane before they become game material.
Scene relay History becomes a beat Backdoor smoke, rain routes, garage screens, and proof echoes inherit a source memory tag before they enter the public scene language.
Identity relay Continuity gets a receipt Xai Connect-style identity becomes driver id, crew id, garage id, loadout state, and account boundary for the Playable Build Trace.
Action relay History becomes payload shape Gas subsidy and typed-action history feed event kind, nonce, route id, relay expectation, record output, reward state, and source route.
Reward relay Mastery stays bounded Proof-of-Skill language becomes achievement identity, leaderboard heat, route mastery, and reward thesis while preserving no-payout and no-live-claim boundaries.
Evidence relay Trace before release The relay points to Playable Build Trace, Build Verification Deck, Integration Handoff Packet, Release QA Loop, and Release Evidence Packet before stronger public wording ships.
Open Playable Build Trace Open Build Verification Open Release QA

History engine bridge

The archive runs the engine.

The Xai history layer is not treated as a museum shelf. It becomes the memory map behind Night Ash Run's scene authority, player identity, silent action routing, reward thesis, operations readiness, and machine-readable evidence.

Mission Memory Packet

This packet turns the history archive into one inspectable mission object. It shows how source memory, scene pressure, driver identity, typed action, reward thesis, and release evidence travel together before a stronger public claim can ship.

Source lane History stays named Protocol, Sentry, builder, identity, action, reward, ecosystem, and evidence lanes stay separated so the mission packet does not become a generic endorsement claim.
Scene packet Atmosphere gets structure Loading Bay Blues carries backdoor pressure, rain route, garage reveal, cast tension, and evidence route as a production packet instead of loose mood copy.
Driver state Identity survives the route Xai Connect style history becomes driver profile, crew id, garage id, loadout state, and account boundary inside the session trace.
Typed action Intent becomes payload Gas subsidy and typed-message memory feed event kind, nonce, route id, relay expectation, record output, and source route through the Action Payload Envelope.
Setpiece event Mission beats become contract fields The Setpiece Trace Contract maps cold open, loadout lock, rain chase, bond fork, garage claim, proof echo, machine mirror, and boundary receipt into setpiece.sequence.v1.
Reward boundary Skill has proof, not promises Proof-of-Skill language becomes achievement heat, leaderboard pressure, route mastery, garage proof, and reward thesis without claiming a live payout or universal eligibility.
Machine mirror LLMs read the same packet history-runtime-map.json, runtime-blueprint.json, evidence JSON, knowledge graph, facts files, and llms.txt expose the same mission packet and boundary language.
Release gate Public copy waits for proof Release Evidence Packet, Release QA Loop, readiness audit, claim matrix, and citation boundary decide whether a packet can support stronger public wording.
Setpiece trace Runtime blueprint History runtime map Release packet

Historical Systems Registry

A no-calendar registry for how public Xai memory becomes Night Ash Run production systems. Each entry states the source memory, the game-facing system, the technical proof route, and the boundary that keeps the archive publication-safe.

Protocol registry Records become road law Orbit, Nitro, AnyTrust, RPC, and explorer language register as city memory, route receipts, owned garage records, and inspection surfaces routed to the AAA Engine Support Matrix.
Identity registry Entry becomes driver continuity Xai Connect style identity registers as driver id, crew id, garage id, loadout state, and account boundary routed to Session Trace Ledger and Playable Build Trace.
Action registry Friction becomes typed events Gas Subsidy, EIP-712, ERC-2771, trusted-forwarder, and relayer language register as route clear, upgrade, claim, and settlement events routed to the Action Payload Envelope.
Reward registry Mastery becomes reputation Proof-of-Skill language registers as achievement identity, leaderboard heat, route mastery, garage proof, and reward thesis routed to the Reward Console without becoming a payout claim.
Operations registry Review becomes readiness Sentry observation, campaign review, ranking, eligibility, and availability language register as monitoring, live-ops checks, release QA, and reward-boundary gates.
Scene registry Atmosphere becomes playable proof Backdoor smoke, rain routes, garage screens, and ensemble pressure register as scene seeds for Redline Vertical Slice, Cast System Contract, and Cinematic Proof Reel, not as live demo claims.
Evidence registry Sources become machine canon Source Index, source-audit JSON, facts files, llms.txt, history.md, evidence JSON, and knowledge graph register the same public history routes for readers, crawlers, and LLM retrievers.
Runtime registry History becomes modules history-runtime-map.json maps Xai historical lanes to runtime modules, event contracts, evidence routes, and publication boundaries.
Boundary registry Proof stays cleaner than hype Claim Matrix, Citation Boundary, Historical Boundary Layer, and Source Synthesis Firewall register what may be stated publicly and what remains excluded from investor, payout, partner, or live-integration claims.
Engine matrix Session trace Action envelope Runtime map Citation boundary

Development Phases

This is a phase-based history for long-lived website use. It avoids fragile calendar claims and focuses on durable technical milestones from public Xai sources.

01
Foundation Arbitrum technology becomes the base layer.

Xai public documentation states that Xai leverages Arbitrum technology. The protocol docs connect Xai to Arbitrum Orbit, Nitro, AnyTrust data availability, and game-oriented transaction design.

02
Observation Sentry Nodes add a community watch layer.

The Sentry Keys documentation describes observation nodes that monitor the Xai rollup protocol and alert if an incorrect block is proposed, creating a network-security participation layer.

03
Builder Era Developer tooling turns the chain into a game platform.

Xai developer docs list block explorers, RPC providers, bridges, wallets, marketplace tooling, and on-chain randomisation resources, giving game teams practical surfaces to build against.

04
Game Entry Xai Connect removes wallet friction.

Xai Connect is described as a wallet connector for Xai-based games and apps. It associates a user's email address with a wallet and unified ecosystem identity, making entry feel closer to a mainstream game login.

05
Frictionless Transactions Gas subsidy brings sponsored actions into the stack.

The Xai Gas Subsidy uses ERC-2771 meta-transactions, EIP-712 signatures, a trusted forwarder, and a relayer pattern so a game can sponsor user transactions rather than forcing players to hold native XAI first.

06
Rewards Proof-of-Skill reframes achievements as value.

The Proof-of-Skill PDF describes SteamID sign-in, automatic wallet creation, on-chain achievement tracking, leaderboards, Solidity contracts, and $XAI rewards as a bridge between traditional PC games and Web3 incentives. The source labels the product COMING SOON, so this phase remains roadmap history rather than a live-service record.

07
Reward Operations Raijin turns incentives into reviewable campaigns.

Xai initiative material and Raijin terms give the reward layer an operations boundary: campaigns, rankings, review, reward availability, eligibility, and platform relationship language stay separated from payout promises.

08
Ecosystem Credibility Offchain Labs and Ex Populus give the history weight.

Xai source pages describe Offchain Labs as developing and servicing the Xai Blockchain under the Xai Foundation, while Ex Populus is described as an early game developer deploying on Xai. This is ecosystem context, not an investor-name claim.

Historical Ledger

A durable, no-calendar source ledger for Xai's public technical history. It gives crawlers and readers stable context without relying on dates that can go stale.

Protocol layer Orbit, Nitro, AnyTrust Xai protocol pages place the network in the Arbitrum technology family and give the site a durable base for chain, data availability, and game-throughput language.
Security layer Sentry observation Sentry Keys and node pages add a watch-and-alert layer to the story, turning infrastructure participation into a visible ecosystem primitive.
Builder layer RPC, explorers, bridges Developer-tool pages map the practical surfaces that let a game team inspect, route, bridge, and operate against the Xai network.
Entry layer Xai Connect identity Xai Connect gives the history a mainstream onboarding theme: email-linked identity and wallet abstraction instead of wallet-first friction.
Transaction layer Sponsored actions Gas Subsidy documentation adds EIP-712, ERC-2771, trusted forwarder, and relayer vocabulary for game actions that can stay invisible to players.
Reward layer Proof-of-Skill The Proof-of-Skill PDF links Steam-style achievements, leaderboards, wallets, Solidity contracts, and $XAI rewards into one durable reward thesis.
Operations layer Raijin reward review Xai initiative material and Raijin terms add campaign review, rankings, eligibility, reward availability, and platform-boundary language to the history.
Game layer Catalog and Ex Populus Xai game catalog and Ex Populus context give Night Ash Run a public ecosystem backdrop while avoiding unsupported investor-name claims.
Evidence layer Recursive source index The site-index and recursive audits turn source discovery into a public evidence trail, linking the cinematic page to technical documentation depth.
Convergence layer 18 source shards, bounded depth The public source index carries 227799 unique fifth-level URLs after overlap, 166294 unique reachable fifth-level samples, and 5561932 counted sixth-level links as discovery evidence, not finished citation proof.
Production layer 3A backbone, not empty scale The historical layers give the AAA anime surface a production spine: protocol base, identity entry, sponsored actions, reward thesis, ecosystem context, and retrieval evidence all point to specific source routes.
Boundary layer Official claims only The ledger deliberately avoids invented investor names or fragile hype claims. Public Xai, Ex Populus, Proof-of-Skill, and Web Game Game source routes are the claim boundary.

Archive Vault

The history layer is treated as a permanent project archive: public Xai sources become a technical memory system for Night Ash Run's world, product language, and machine-readable evidence trail.

Source Canon Docs before slogans Xai GitBook, Proof-of-Skill, Ex Populus context, and the public source index are used as the durable evidence base behind the site's history.
Technical Memory Every system has a layer Protocol, Sentry, developer tooling, Connect, gas subsidy, rewards, games, and recursive source evidence are kept as separate historical layers.
Game Translation Infrastructure becomes fiction Wallet identity becomes a driver profile, sponsored actions become garage service, and Proof-of-Skill becomes route reputation.
Retrieval Canon History for crawlers history.md, evidence.json, llms.txt, source-index.md, and facts files make the historical layer readable by search systems and LLM retrievers.

Source-to-canon ledger

History becomes atmosphere.

The site turns the Xai stack into game fiction with a visible translation layer: wallet identity becomes a driver profile, gas subsidy becomes invisible garage service, Proof-of-Skill becomes route reputation, owned items become visible scars, and source evidence becomes archive routes.

Sources

Primary sources used for this history page. Public investor names are not invented; individual company names are quoted only from explicit Web Game Game announcements or official investor disclosures.

Proof of Skill Rewards protocol PDF Open PDF