I.1 Contents

	At a glance
What it is	Every chapter in this book, each with the one line that tells you what you get by reading it.
Where it sits	Front matter · Chapter I.1
Covers	[Front matter](/story/front-matter/) · [Prologue — The chronology](/story/part-0-chronology/) · [Part I — The story, 2016–2026](/story/part-i-the-story/) · [Part II — What the network still needs](/story/part-ii-what-is-needed/) · [Back matter](/story/back-matter/)

I.1.1 Front matter

What this book is, and how to read a history whose ending is still open.

• Contents — Every chapter in this book, each with the one line that tells you what you get by reading it.
• Copyright & sources — How this history was researched, what it is careful not to claim, and where every source is listed.
• Half title — The Story book: how The Root Network came to be, how it was left behind, and what people are doing about it now.
• Preface — how to read this book — This is a history whose ending is not written. Here is how the chapters are built, what they source, and how to read them without being led.
• Title page — The Story book — the history and background of The Root Network, 2016 to 2026, drawn from news, company filings, on-chain records and video.

I.1.2 Prologue — The chronology

The Futureverse → community handover as it was announced, dated and sourced.

• Timeline · The Futureverse → community handover — What happened to The Root Network between September 2025 and now — the receivership of Futureverse, the takeover by TRN Labs and a coalition of independent validators, and what the network's stewards are working on next.

I.1.3 Part I — The story, 2016–2026

How The Root Network came to be and how it was left behind: Centrality, the Futureverse roll-up, the launch with Ripple, the receivership, and the community rescue.

• The story of The Root Network, 2016–2026 — How The Root Network came to be and how it was left behind: Centrality, the Futureverse roll-up, the launch with Ripple, the big promises, the receivership, TRN Labs going quiet, and the community rescue. Sourced from news, company filings, X posts and 70+ YouTube transcripts.

I.1.4 Part II — What the network still needs

What operators can actually do about it: bootnodes, public RPCs, history, and the other jobs that are still open.

• What the network still needs — The jobs Futureverse's servers used to do quietly, which now need community operators: bootnodes, public RPCs, history recording, snapshots, bridge relaying and more. What each is, why it matters, and how to help.

I.1.5 Back matter

Where this suite is going, what has changed, and every source the story rests on.

• Changelog — Keep track of every change to The Root Network.
• Roadmap · TRN suite — What's shipped, what's in flight, and what's queued — ordered for the order that makes the most sense to actually implement in.

Associated docs

Where else you might go from here. Following one is optional — this chapter stands without them.

@futureverse/artm

See also — Asset Register Transaction Message (ARTM) describes the standard approach for parsing updates to the off-chain Asset Register database.

@futureverse/asset-register

See also — ## Installation

@futureverse/asset-register-react

See also — ## Installation

@futureverse/auth

See also — Provides an Open ID Connect Authentication library for FuturePass.

@futureverse/auth-core

See also — Provides common functionality / internals for Futureverse auth

@futureverse/auth-react

See also — Provides a React authentication provider for Futureverse Auth.

@futureverse/auth-react-native

See also — Provides React Native authentication components and providers for Futureverse Auth.

@futureverse/auth-ui

See also — A client-side React UI library that provides customizable authentication components and flows for Web3 wallets and Pass custodial authentication.