D17 DOCS
Getting started

Five-minute start

Install the repository, select a network, and run the terminal against your own RPC.

Requirements

  • Node.js 22.13 or newer
  • an HTTP JSON-RPC endpoint for Sepolia, mainnet, or both
  • an optional WebSocket RPC endpoint for lower-latency updates
  • a browser wallet only when you want to sign transactions

Two separate repositories

This page describes the companion D17 application repository, whose root contains apps/web, apps/api, and contracts. This documentation repository contains the Fumadocs/Scalar site only. To run the documentation itself, use npm install && npm run dev from this repository's root.

Install the companion application

npm install
cp apps/web/.env.example apps/web/.env.local

Set NEXT_PUBLIC_D17_DATA_MODE=rpc, add the public RPC URLs you intend to use, then start the app:

npm run dev:rpc

Open the local URL printed by the companion web app. Its top navigation changes between Sepolia and mainnet without requiring two application repositories.

What to check

  1. The network label matches the selected chain.
  2. The five canonical factory addresses appear in the contract section.
  3. Existing launches load on Sepolia; mainnet is an honest empty state until a launch exists.
  4. No wallet prompt appears for display reads.
  5. The deploy page simulates against your configured RPC, but signs only after your wallet confirms.

Add the optional read API later

Direct RPC is the simplest local arrangement. If you want indexed first-load snapshots, launch discovery, server-side logo handling, and application WebSocket notifications, continue with API self-hosting. Changing data mode does not change the contracts or transaction path.

Start here

The minimum context you need before using or running D17.

Networks and read modes

Keep chain identity, display reads, and wallet writes separate.

On this page

RequirementsInstall the companion applicationWhat to checkAdd the optional read API later