Configuration

Web3 Configuration

Feature flags, API keys, and environment variables that control which blockchain capabilities are included in a Create project.

Minimal Inclusion Principle

Create only includes the Web3 modules the user explicitly asks for. A landing page gets no blockchain code. An NFT minting app gets only the flags it needs.

How It Works

Each project starts with zero flags activated. The AI analyzes the user's request and enables only the specific feature flags required. Cascade rules automatically activate dependencies, but nothing extra is ever included.

17 Feature Flags

Each flag controls a specific blockchain capability. Flags are grouped by ecosystem: Solana, EVM, or both.

SolanaSolana Ecosystem Flags

solana

Wallet connection, token balances, NFT display

nft

NFT gallery and collection browsing

perps

Perpetual futures trading via Drift

orderbook

Central limit order book DEX via OpenBook V2

events

Prediction markets via dFlow

EVMEVM Ecosystem Flags

evm

Wallet connection via thirdweb

evm-nft

NFT gallery powered by Alchemy

evm-marketplace

NFT marketplace via Reservoir

mint

Public mint page for ERC-721 collections

deploy

Contract deployment (EVM + Solana)

dao

Governance via OpenZeppelin Governor

base

Base-specific features: Basename resolution, gas estimation

BothCross-Ecosystem Flags

swap

Token exchange via Jupiter, Uniswap, 0x, or CoW Protocol

analytics

Prices, OHLCV charts, trending tokens via Birdeye and CoinGecko

oracle

On-chain price feeds via Chainlink, Pyth, and Switchboard

nft-metadata

Upload NFT metadata and images to SeaweedFS

token-gate

Restrict access based on token ownership

Cascade Rules

Some flags automatically activate their dependencies. These cascades ensure the required infrastructure is always present.

deployauto-activates evm

daoauto-activates evm + deploy

evm-marketplaceauto-activates evm

evm-nftauto-activates evm

mintauto-activates evm

swap alone does not activate any chain. It requires evm or solana to be explicitly set.

Required API Keys

API keys are added as environment variables. Only the keys needed for your activated flags are required.

Mandatory Keys

Required for any project that activates Solana or EVM flags.

SolanaHelius

HELIUS_API_KEYNEXT_PUBLIC_HELIUS_API_KEY

Required for all Solana operations: RPC, DAS API, webhooks

EVMthirdweb

NEXT_PUBLIC_THIRDWEB_CLIENT_ID

Required for all EVM wallet connections and contract interactions

Optional Keys

Only needed when the corresponding feature flag is activated.

ALCHEMY_API_KEY

EVM NFT gallery (evm-nft)

RESERVOIR_API_KEY

EVM NFT marketplace (evm-marketplace)

BIRDEYE_API_KEY

Solana analytics (analytics)

COINGECKO_API_KEY

Multi-chain price data (analytics)

ZEROX_API_KEY

EVM DEX aggregator (swap)

TENSOR_API_KEY

Solana NFT marketplace (nft)

BASESCAN_API_KEY,ARBISCAN_API_KEY, etc.

Contract verification on block explorers (deploy)

No API Key Required

These protocols and services work without any API key configuration.

JupiterUniswap V3ChainlinkPythCoW ProtocolOpenBookDrift

Flag Activation Examples

These examples show how user requests map to feature flags. The AI determines the minimal set of flags needed.

"Landing page for my crypto project"

Flags:none

No blockchain features needed for a landing page.

"App to view my Solana NFTs and swap tokens"

Flags:solananftswap

"Dashboard to deploy an ERC-20 on Base"

Flags:evmdeploy

"DAO governance dashboard"

Flags:evmdeploydao

dao cascades to activate evm + deploy automatically.

Ready to configure your Web3 project?

Describe what you want to build and Create activates exactly the flags you need.

Start Building