About
Software that ships parachains.
A parachain, in Polkadot terms: an independent chain that lives inside a larger network — Vitreus, in our case. ChainForge handles the parts of building one that only matter on this chain.
Your AI agent types the code. You decide what ships. ChainForge handles the Vitreus-specific work in between — generating the starter project on your machine, validating your code against the conventions, walking you through the deploy on testnet, decoding your live chain once it's producing blocks.
Real files. Real checks. Real testnet. A software product, doing software work.
What it does
Four jobs. All software.
Each one ships milestone by milestone, in the open. None is a template you read — every output is a file written, a check run, or a call against the chain.
Generate the starter.
You describe what you want — a token with quadratic voting, an oracle feed, a DEX. ChainForge writes the Cargo project: pallets wired into the runtime, chain spec defaults, a CLAUDE.md tuned to Vitreus, tests that pass on day one.
Validate against Vitreus.
Paste a file or point at a repo. ChainForge runs Vitreus-specific lint checks: missing weight annotations, unbounded vectors, forgotten storage migrations. Each finding lands with a line, a severity, a reason, and a suggested fix.
Walk the deploy.
Chain spec, parachain registration extrinsic, collator startup, block-production verification. ChainForge sequences each step, validates the one before, and translates failures into Vitreus-specific reasons. Signing happens in your browser wallet.
Decode your live chain.
Once you're producing blocks, ChainForge filters Vitreus to your parachain: extrinsics hitting your pallets, events you defined, dispatch errors translated into plain English. Decoded against your runtime metadata.
How it works
Three actors. One chain.
ChainForge isn't another AI coding agent and it isn't a place you log into to type. It's the chain-specific software that fits between your agent and the chain.
Your AI agent types the code.
Claude Code, Cursor, whatever you use. ChainForge feeds it the chain-specific context it doesn't ship with — pallet conventions, foot-gun patterns, pointers into the real Vitreus source — so the typing stops being guesswork.
ChainForge does the Vitreus work.
Scaffolds the starter, validates against the conventions, walks the deploy, decodes your live chain. Real software running, not a doc site to read.
You decide what ships.
Every commit, every key, every signed transaction. ChainForge sits in the path while you build, and steps out the moment you deploy.
Who it's for
Two audiences. Both served on purpose.
The curious newcomer
Has heard about Vitreus, wants to build something on it, and bounces off the “you should already know Rust” assumption baked into most docs. ChainForge writes the boilerplate and walks the deploy so you can focus on what your chain does.
The experienced Substrate builder
Knows the territory but is tired of re-typing the same pallet wiring, hunting for the right examples, and explaining their chain to every AI agent from scratch. ChainForge does the boring parts so you can spend time on the interesting ones.
Why we built it this way
What you can count on.
Every choice here serves one goal: getting you from idea to a shipped chain without making you regret it.
Real Vitreus, from day one.
You deploy to the actual testnet from your own machine, with your own keys, from day one. Plenty of tools spin up parallel imitations of the chain — friendly for tutorials, terrible when you graduate. ChainForge skips that step. What you ship is what the chain actually accepts.
You own everything you build.
The output of every workflow is a project on your machine, deploying to a chain that's not ours. ChainForge holds no keys, hosts no runtime, and is not in the critical path of your chain once it's live. If we shut down tomorrow, your parachain runs.
Community-shaped from the start.
The gallery, the Q&A, the forkable projects are how the platform stays useful. Patterns surface because real builders use them. Foundation reviews accuracy on the outputs; builders shape what gets built next. You're a co-author, not a customer.
A note on Vitreus
Vitreus is the chain. ChainForge is the software that targets it — sanctioned by the Foundation, but not of them. The scaffolder, the validator, the deploy walker all read from the real Vitreus source as the source of truth, so what you ship is what the chain accepts — not a paraphrase that drifts as the runtime upgrades.
The next step is a five-minute scaffold.
ChainForge is for people who'd rather ship than read about shipping. Start when you're ready.