Documentation

Quick Start

Build your first stablecoin project

Five steps to move from a blank workspace to a simulated or deployed contract using the current builder UI.

Before you begin

You will need a StablecoinRoadmap account to create projects and save versions. Deployment requires a Web3 wallet and a configured environment if you want to use API-backed features or integrations.

Step 1

Request a demo

Book a demo to unlock projects, version history, and deployment settings.

Open

Step 2

Create a workspace project

Use the Projects workspace to name your build and manage versions.

Open

Step 3

Open the builder

Switch between the visual builder, AI coach, and Solidity editor as you design.

Open

Step 4

Simulate contract behavior

Run the simulation panel to test basic flows and inspect state updates in-browser.

Open

Step 5

Deploy to Base networks

Use the deployment panel to deploy to Base Sepolia (testnet) or Base mainnet.

Open

Environment setup (sandbox-ready)

Copy the environment template and set the minimum keys required for the builder + API sandbox.

cp .env.example .env.local

# Required (Supabase + AI generation)
NEXT_PUBLIC_SUPABASE_URL_PROD=...
NEXT_PUBLIC_SUPABASE_ANON_KEY_PROD=...
SUPABASE_SERVICE_ROLE_KEY_PROD=...
GEMINI_API_KEY=...

Tip: Use the sandbox Supabase keys if you want to test without affecting production data.

Local dev commands

Run the dev server and validate lint + type checks before deploying.

npm install
npm run dev
npm run lint
npm run type-check

Choose your network

Base Sepolia (testnet)

Best for demos, simulations, and sandbox flows. Use this to validate contract logic and integration paths.

Base mainnet

Use once you have completed compliance checks, funding, and operational readiness. Ensure your wallet is funded and policies are reviewed before deploying.

Accelerate with templates

Start from a template to get a pre-wired architecture, KPIs, and deployment checklist.

Next steps

Continue with the Getting Started guide for a deeper checklist, or jump straight to the API Reference if you are integrating programmatically.