Skip to content
Documentation
AI-Powered

Smart Contracts

Six deployable contract templates built on OpenZeppelin v5 and Solidity ^0.8.20, compiled and deployed from plain English descriptions.

How It Works

Describe your contract in natural language. Create selects the matching template, fills in your parameters, compiles server-side with solc-js, and presents a wallet transaction for you to sign and deploy.

Describe in English
Tell the AI what you need. It maps your request to one of six contract templates and fills in the placeholders.
Server-Side Compilation
Compiled with solc-js on the server. Optimizer enabled with 200 runs, EVM version "paris". No local toolchain required.
You Sign, You Own
The server prepares the transaction, your wallet pops up to sign. The server never has your private keys. After confirmation the contract is verified on the block explorer.

6 Deployable Contract Templates

All contracts use OpenZeppelin v5 with Solidity ^0.8.20. Each template has specific placeholders that the AI fills from your description.

ERC-20Fungible Token

Standard fungible token with owner-controlled features:

  • Mint, burn, and pause functions
  • Airdrop to multiple addresses
  • Configurable max supply and decimals
Placeholders: TOKEN_NAME, TOKEN_SYMBOL, INITIAL_SUPPLY, DECIMALS, MAX_SUPPLY, OWNER_ADDRESS
ERC-721NFT Collection

NFT contract with public minting and on-chain royalties (ERC-2981):

  • ownerMint — free, only the contract owner
  • publicMint — payable, any user, max 10 per transaction
  • Configurable mint price, max supply, and base URI
  • Royalties set in basis points (e.g. 500 = 5%)
Placeholders: COLLECTION_NAME, COLLECTION_SYMBOL, MAX_SUPPLY, MINT_PRICE, BASE_URI, ROYALTY_BPS, OWNER_ADDRESS
ERC20VotesGovernance Token

ERC-20 token extended with voting power and ERC20Permit for gasless approvals:

  • Built-in vote delegation and checkpointing
  • Compatible with Governor and Timelock contracts
  • ERC20Permit for off-chain approval signatures
Placeholders: TOKEN_NAME, TOKEN_SYMBOL, INITIAL_SUPPLY, OWNER_ADDRESS
TimelockDAO Timelock

TimelockController with a configurable execution delay for DAO operations:

  • Minimum delay in seconds (default 3600 = 1 hour)
  • Queues proposals before execution
  • Part of the DAO stack: deploy before the Governor
Placeholders: MIN_DELAY, OWNER_ADDRESS
GovernorDAO Governor

Full on-chain governance: proposals, voting, and execution via Timelock:

  • Configurable voting delay, voting period, and proposal threshold
  • Quorum percentage based on total supply
  • Deploy order: GovernanceToken → Timelock → Governor → setup roles
Placeholders: GOVERNOR_NAME, TOKEN_ADDRESS, TIMELOCK_ADDRESS, VOTING_DELAY, VOTING_PERIOD, PROPOSAL_THRESHOLD, QUORUM_PERCENTAGE
StakingStaking Vault

ERC-20 staking with time-based reward distribution (Synthetix pattern):

  • stake, withdraw, claimReward, and exit functions
  • Owner calls notifyRewardAmount to fund reward periods
  • Separate staking and reward token addresses
Placeholders: STAKING_TOKEN, REWARD_TOKEN, REWARD_DURATION, OWNER_ADDRESS

Supported Chains

Deploy to L2 networks and their testnets. Ethereum L1 is not supported.

Base

Chain 8453

Arbitrum

Chain 42161

Optimism

Chain 10

Polygon

Chain 137

Writing Effective Contract Prompts

The AI maps your description to one of the six templates above. Be specific about which features you need.

ERC-20 Token

Bad — too vague:

Create a token

Good — uses real template features:

Create an ERC-20 token called MYTOKEN with 1M supply, 18 decimals, owner can mint and pause
NFT Collection

Bad — requests unsupported features:

NFT with whitelist, reveal mechanic, and Dutch auction

Good — matches the template:

Create an NFT collection with 5000 max supply, 0.05 ETH mint price, 5% royalties
DAO Setup

Bad — single vague request:

Make me a DAO

Good — specifies governance parameters:

Set up a DAO with governance token, 1-day voting delay, 1-week voting period, 4% quorum

Security & Deployment

All contracts inherit OpenZeppelin v5 audited implementations. The deploy flow keeps your keys under your control at all times.

OpenZeppelin v5
Every template inherits battle-tested OpenZeppelin contracts: Ownable, Pausable, ReentrancyGuard, ERC2981, and more.
No Private Keys on Server
The server compiles and prepares the transaction. Your wallet signs it. The server never touches your private keys.
Solc-js Compilation
Compiled server-side with optimizer enabled (200 runs) and EVM version "paris". ABI and bytecode returned to the client.
Block Explorer Verification
After deployment confirmation, the contract source is automatically verified on the chain's block explorer.

Deploy Flow

From description to on-chain contract in four steps.

1

Compile

The server compiles your contract with solc-js (optimizer 200 runs, EVM "paris") and returns the ABI + bytecode.

2

Prepare Transaction

The client calls prepareTransaction to build the deployment transaction with your constructor arguments.

3

Wallet Confirmation

Your wallet pops up. You review the gas estimate and confirm the transaction. The server never has your keys.

4

Receipt & Verification

waitForReceipt confirms the deploy. The contract source is then verified on the block explorer automatically.

What Is Not Supported

Create uses fixed templates, not arbitrary Solidity generation. The following are outside the current scope:

  • Ethereum L1 deployment
  • ERC-1155 multi-token contracts
  • Upgradeable proxy patterns (UUPS, Transparent)
  • Arbitrary Solidity code — only the six templates above are available
  • Transfer taxes, vesting schedules, liquidity pool logic
  • Whitelist/allowlist minting, reveal mechanics, Dutch auctions

Ready to deploy a contract?

Describe what you need and Create handles compilation, deployment, and verification.

Deploy Contract