the handbook
How CodePad works.
Ten short truths about blocks, vaults, receipts and locked rules. Read once, launch forever.
01 The idea in one breath
A coin on CodePad carries a small program made of blocks. You describe the program in a sentence, Bolt translates it into those blocks, and once you launch, the coin executes them forever — paid from the fees it earns itself.
02 Where the money sits
Every coin has its own vault on-chain. Fees that buyers pay land in that vault — nothing is pooled with other coins and nothing is held by you or by us personally.
03 How a run works
The program wakes on its triggers — a trade, a passing price level, the clock. It walks its blocks top to bottom, moves only what its rules allow from the vault, then writes a receipt anyone can check.
04 Limits keep coins honest
A coin can only spend what it has earned. Vaults start empty, and spending is capped by earnings — a hot launch does not create solvency, it only fills the jar faster.
05 Receipts, not promises
Each run leaves an on-chain receipt: what the rule saw, what it did, what it cost. You never have to trust a dashboard — you can verify the chain itself.
06 Frozen after launch
Rules are fingerprinted at launch and locked. You can launch a new coin with new rules, but a live coin cannot be edited by anyone, including us.
07 Plain english first
Every block set is readable as a normal sentence, so holders always know what a coin does without reading bytecode.
08 If the rails ever nap
Block execution depends on the automation rails; if they pause, runs pause and resume later — vaults stay untouched on-chain and nothing is lost.
09 What launching costs
A small flat launch fee per coin plus the network's own costs. Fees from launches feed the CodePad program: buybacks, burns, and the AI agents that keep coins running.
10 AI credit
Blocks that think (names, words, decisions) consume a small AI credit per run so a chatty coin can't drain its own vault.
Enough reading — one sentence and Bolt does the rest.
Open the builder