Build a Dapp on StarkNet from Scratch

Turn any idea into a working dapp on StarkNet. Describe what you want to build. A tipping app for streamers, a loyalty rewards program, a mobile game with in-app tokens. And Chipi's MCP scaffold prompt maps it to the right features, generates the project structure, and wires everything together. Best starting point for new builders.

Start with a fresh project for your platform:

bash# Next.js (recommended)
npx create-next-app@latest my-dapp --typescript --tailwind --app --src-dir
cd my-dapp
npm install @chipi-stack/nextjs@latest

# React (Vite)
npm create vite@latest my-dapp -- --template react-ts
cd my-dapp
npm install @chipi-stack/chipi-react@latest

# Expo (Mobile)
npx create-expo-app@latest my-dapp --template tabs
cd my-dapp
npx expo install @chipi-stack/chipi-expo@latest

Before writing code, map your idea to Chipi capabilities:

• - Wallet creation. Almost always needed. Users get a self-custody wallet with passkey auth
• - USDC payments / transfers. For e-commerce, tipping, invoicing, subscriptions
• - Session keys. For frequent interactions without re-auth (games, social, trading)
• - VESU staking. For yield, savings, or DeFi features
• - SKU marketplace. For digital services like airtime, gift cards (Mexico only)
• - Custom contract calls. For any on-chain logic not covered above (NFTs, governance, tokens)

Start with the simplest MVP that delivers value. What's the one core flow?

Every Chipi wallet is tied to an authenticated user. Set up auth first:

1. Choose Clerk (fastest), Firebase, Supabase, or Better Auth
2. Get the provider wrapper via get_component_code("chipi-providers")
3. Set up environment variables via get_env_template()
4. Wrap your app root in ChipiProvider

No auth = no wallet. This is the foundation.

Add only what your idea needs:

• - Wallets: get_component_code("create-wallet-dialog") + get_component_code("wallet-summary")
• - Payments: get_component_code("pay-with-crypto-button") + webhook endpoint
• - Session keys: get_sdk_reference(category: "session") for the hooks
• - Staking: useStakeVesuUsdc and useWithdrawVesuUsdc
• - Custom contracts: useCallAnyContract for arbitrary on-chain calls
• - Digital services: get_component_code("list-skus") + get_component_code("buy-sku")

Build the core UI pages, test the flow, and ship the MVP. Don't over-build. Iterate later.