Skip to content
Documentation
Transparency

Known Limitations

Create is opinionated by design. This page lists what is currently outside scope so you can plan your project with full clarity.

Chains NOT Supported

Create targets EVM Layer 2 networks (Base, Arbitrum, Optimism, Polygon) and Solana. The following chains and ecosystems are not available.

Unsupported Chains
  • Ethereum L1 (mainnet) — Only L2s are supported
  • Bitcoin / Lightning — Different ecosystem
  • Avalanche — No chain config
  • BNB Chain (BSC) — No chain config
  • zkSync, Scroll, Linea — No chain config
  • Cosmos / IBC chains — Different ecosystem
  • Starknet, StarkEx — Different VM (Cairo)
  • Aptos, Sui — Different VM (Move)
  • TON, Tron — Not supported

Contracts NOT Supported

Create uses six fixed Solidity templates. Contract types outside this set cannot be generated or deployed through the platform.

Unsupported Contract Types
  • ERC-1155 (Multi-Token) — No template. thirdweb can interact with existing ones but can't deploy
  • Arbitrary Solidity — Compiler uses template placeholders, doesn't accept custom user code
  • Upgradeable Proxies — No UUPS or TransparentUpgradeable pattern
  • Vesting contracts — No template
  • Multisig (Gnosis Safe) — No integration

Features NOT Available

These features and integrations are not part of Create today. Some are intentional design decisions, others may be added in the future.

Bridges & Interop
No cross-chain bridges (Wormhole, LayerZero, Axelar). Each project targets a single chain.
Fiat On-Ramps
No Stripe, MoonPay, or Transak integration. Users must already hold crypto in their wallet.
KYC / AML / Identity
No identity verification or compliance tooling. Create does not collect or verify user identities.
Account Abstraction (ERC-4337)
No smart accounts, paymaster, or bundler. Users sign transactions directly with their EOA wallet.
Gasless Transactions
No meta-transactions or relayers. Users pay gas fees directly from their wallet.
Decentralized Storage
No IPFS or Arweave storage. Create uses SeaweedFS (S3-compatible) for file storage instead.
ENS Resolution
Only Basename (Base chain) is supported. No generic ENS resolution across other chains.
Indexing & Subgraphs
No The Graph or Goldsky indexing. Only a basic event indexer via RPC polling is available.
Real-Time Feeds
No WebSocket or real-time blockchain event feeds. Data is fetched via HTTP polling only.
Web3 Social
No Lens or Farcaster integration. No social protocol templates are available.
DeFi Lending
No Aave, Compound, or other lending/borrowing protocol integration.
Portfolio Trackers
Only basic balances are available. No PnL tracking or multi-wallet aggregation.
Mobile / React Native
Only web (Next.js) is supported. No native mobile app generation.
Notifications
No email or push notification system. Generated apps do not include notification infrastructure.
Server-Side Signing
Intentionally removed. The server NEVER signs transactions. This is a security design decision, not a missing feature.

What IS Configurable

Within the supported contract templates, these parameters can be customized from your chat description.

ERC-20Fungible Token
name, symbol, initial supply, decimals, max supply, owner
ERC-721NFT Collection
name, symbol, max supply, mint price, base URI, royalty BPS, owner
GovernorDAO Governor
name, token address, timelock address, voting delay/period, threshold, quorum %
StakingStaking Vault
staking token, reward token, reward duration, owner

Focus on what IS supported

Create ships with six battle-tested contract templates, multi-chain L2 deployment, and a full AI-powered generation pipeline. See everything you can build today.

Explore Capabilities