Build
Deploy a Contract
LaunchKit ships self-contained Solidity templates that compile with no external imports, so a deploy is fast and predictable. Pick one, fill in its constructor, and your wallet sends it.
Built-in templates
| Contract | Category | What it is |
|---|---|---|
| SimpleERC20 | Token | A fungible token with a fixed initial supply minted to an owner. |
| SimpleERC721 | NFT | An NFT collection with a base metadata URI. |
| SoulboundNFT | NFT | A non-transferable NFT bound to the wallet it is minted to. |
| SimpleStaking | DeFi | Stake a token and earn rewards at a rate per block. |
| MultiSigWallet | Governance | An m-of-n wallet: transactions need a set number of owners. |
| TimelockController | Governance | Queue calls and execute them after a minimum delay. |
| PaymentSplitter | Utility | Split incoming funds between payees by share. |
| MembershipPass | Utility | A time-limited membership NFT with a set duration. |
| ReputationRegistry | Utility | Record and read reputation scores for addresses. |
| QieIdGatedAllowlist | Utility | Claims limited to wallets that hold a QIE ID. |
Every built-in template is also listed in the Marketplace as an official listing, next to templates other builders sell. Two official templates, Stablecoin Invoices and Token Vesting, are paid listings: their files unlock when you buy them.
The deploy flow
- 1Select a template
Open Deploy and search or browse the templates for the selected network.
- 2Configure it
The form is generated from the constructor. Addresses, numbers and arrays are validated as you type, and the right column shows what will be deployed and to which network.
- 3Deploy
DevStation compiles the source in a browser worker, encodes the arguments, and asks your wallet to sign. It then waits for the transaction to confirm and records the deployment in the ProjectRegistry.
After a deploy
- The contract address, transaction hash and block, each linked to the explorer.
- A downloadable
.envwith the address and network, ready for a front end. - One click to decode the transaction in Routebook.
- Source verification on the network explorer.
- An automatic label in the Label Registry, if that is switched on in Settings.
Where your deployments show up
On your dashboard, grouped by network, and in My Projects. A deploy made in another browser appears too, because the list is read from the registry rather than from local storage. A deployment that was not recorded, for example because the registry transaction was rejected, can be registered later from My Projects.
Tip