Resources
Matterhorn How‑To Guide
Build secure, multi‑chain dApps from plain English. This guide walks through setup, core workflows, and best practices.
1. Information We Collect
- Create an account and verify your email
- Choose a plan or buy credits
- Install Matterhorn Pro (desktop) or open Matterhorn Lite (web)
- Sign in and complete the first‑run checklist
2. Understand credits and plans
- Credits power AI generation, testing, and deployments
- Packs: 95 credits for $19. 499 credits for $89
- Enterprise ($99/month): team collaboration, custom support, and whitelabel options
- Track usage from the account menu. See Pricing for details
3. Your first project
1. Describe your dApp
- Click New Project and name it
- Pick a starting template or start from scratch
- DAOs and governance: proposals, treasuries, vesting, on‑chain execution.
- Custom tokens and marketplaces: taxes, reflections, auctions, and more.
2. Describe
- In the prompt, specify the app you want to build. Example: “Perp DEX on BNB with an oracle feed, admin multisig, and fee switch”
- Add key constraints: chain family, tokens, access controls, fees, upgradeability
3. Generate
- Matterhorn creates contracts, basic tests, and deploy scripts
- Review the plan preview. Edit specs to refine
4. Iterate
- Use Follow‑ups like “add a circuit breaker”, “support USDC on Base”, “add allowlist”
4. Chain selection and multi‑chain
- Choose a primary chain family: EVM, SVM/Solana, Move, or others supported
- Use Multi‑deploy to target multiple EVM chains in one run
- Provide RPC endpoints or pick auto‑managed ones if available
5. Security and quality checks
- Built‑in static checks flag common issues
- Use the Security checklist to review permissioning, pausing, and upgrade paths
- For production, run extended audits or partner with human auditors as needed
6. Testing the project
1. Unit tests
- Run tests locally from the Test tab. Edit test files to add edge cases
2. Simulations
- Use the Simulator to walk through user flows: mint, swap, stake, withdraw
3. Testnets
- Switch to a testnet RPC and deploy. Verify addresses in your Project Overview
7. Configuration and environment
1. Env variables
- Store keys (wallets, API) in your workspace vault. Do not hard‑code secrets
2. Network config
- Set chain IDs, RPC URLs, gas strategies, explorers
3. Feature flags
- Toggle optional modules like royalties, fee switches, oracles
8. Deployment
1. One‑click deploy
- Choose chain and deploy scripts are executed automatically
2. Advanced deploy
- Customize constructor args, proxy patterns, and ownership
3. Verification
- Auto‑verify contracts on supported explorers when enabled
9. Frontend scaffolding
- Generate a minimal frontend with wallet connect and key flows
- Edit components to match branding and routes
- Optional: enable SSR and a basic analytics hook
10. DePIN hosting and storage
1. Compute
- Connect to decentralized compute providers when supported
2. Storage
- Use IPFS/Filecoin for assets and metadata
3. Indexing
- Connect to indexing providers for querying events and state
11. Domains and hosting
- Link a decentralized domain to your deployed frontend
- Configure DNS or gateway settings as instructed in the Deploy tab
12. Team collaboration (Enterprise)
- Invite teammates to the workspace with role‑based access
- Share environment variables securely
- Use Branches to experiment and request reviews before merging
13. Integrations and partners
- Partners may provide compute, payments, indexing, or AI tooling
- Enable partner integrations from Settings → Integrations
14. Troubleshooting
1. Generation failed
- Reduce prompt ambiguity. Add constraints. Try regenerating specific modules
2. Compile or test errors
- Open the Problems panel for exact file and line. Ask Matterhorn to fix the failing test or refactor
3. Deployment failed
- Check gas, RPC health, chain ID, and constructor args. Re‑try with a fresh nonce
3. Verification failed
- Confirm compiler settings and metadata match the deployed bytecode
15. Best practices
- Start simple. Ship a minimal, secure core and iterate
- Keep admin actions restricted and on a separate multisig
- Track addresses per environment and pin binaries and ABIs
- Document any upgradeability and emergency procedures
16. Frequently asked questions
1. What does one credit cover?
- It depends on task complexity. Generation and large refactors cost more than small edits. Deploys cost per chain
2. Can I export code?
- Yes. You retain rights to your project code. Review third‑party licenses you include
3. Do I need to know Solidity, Rust, or Move?
- No to get started. Knowledge helps with reviews and customizations
17. Policies and compliance
- Follow the Platform Rules. Prohibited content or abuse leads to permanent bans and may be reported to authorities where required
- See Terms of Service and Privacy Policy for legal details
18. Support
- Community support via our channels
- Enterprise: dedicated support and SLAs
- Contact:connect@matterhorn.so
Quick start checklist
Enterprise: dedicated support and SLAs
Buy credits or enable Enterprise
New project → Write a clear prompt
Generate → Review and refine
Test locally → Fix issues
Deploy to testnet → Verify
Configure domain and hosting
Deploy to mainnet → Announce
