# Testnet VS Mainnet Before you touch real funds or real users, you can run everything in a **testnet environment**. A testnet workspace works just like your mainnet TMS, but all contracts live on a **test network** and use **test tokens**. It’s the safest way to get comfortable with TMS and validate your token operations before launch. *** ### What is a testnet environment? A testnet environment is a **separate TMS workspace** deployed on a test network that mirrors your mainnet setup: * Same TMS admin app * Same modules (vesting, locks, staking, tokenomics view) * Same roles (Admin / Manager) * Different network: **no real value at risk** You can: * Create vesting strategies * Add allocations * Lock test tokens * Create and interact with staking pools — exactly like you would on mainnet, but using testnet ETH/gas and test tokens. *** ### Why use a testnet TMS? We strongly recommend using testnet before going live on mainnet to: * **Validate your tokenomics in practice**\ Make sure your vesting schedules, cliffs, and TGE settings behave exactly as intended. * **Dry-run operational flows**\ Let your team practice creating strategies, locks, and staking pools without fear of making an irreversible mistake. * **Check UX end-to-end**\ Walk through the full flow as if you were an investor or community member: connect wallet, view dashboard, claim tokens, stake, etc. * **Align stakeholders**\ Share the testnet portal with co-founders, advisors, or partners so everyone can sign off on the structure before it’s locked on mainnet. The testnet environment is your **rehearsal stage**; mainnet is the live performance. *** ### What’s included in a testnet workspace? A testnet workspace includes: * A dedicated **testnet TMS instance** on a supported EVM test network. * **Admin and Manager roles** for your team, just like on mainnet. * Full access to: * Vesting strategies & allocations * Token & LP locks * Staking pools (standard, compounding, LP) * Tokenomics & analytics (with test data) * A **testnet URL** for your portal (white-label can be configured if needed). The only difference: everything is wired to a **testnet token** instead of your real mainnet asset. *** ### How to request a testnet environment You can ask for a testnet setup at any of these points: * When you fill in the **onboarding form** * When you speak with our team before signing the agreement * After mainnet onboarding, if you later want a safe sandbox for experiments Just tell us: * Which **network** you’d like to use for testnet (matching your planned mainnet chain if possible). * Whether your **testnet token** is already deployed, or if you need help deploying a test version. We’ll then: 1. Deploy a **testnet TMS workspace**. 2. Send you a **testnet onboarding link** similar to the mainnet one. 3. Share instructions for getting **testnet gas** (if needed). *** ### Typical testnet workflow Most teams use testnet like this: 1. **Configure everything on testnet first** * Create vesting strategies that mirror your planned mainnet schedules. * Add sample or real allocations (using testnet wallet addresses). * Create locks and staking pools that match your intended design. 2. **Run an internal dry run** * Have your team connect with testnet wallets. * Walk through claiming, staking, and viewing tokenomics. * Check that all labels, categories, and timelines make sense. 3. **Iterate until everyone is confident** * Adjust strategies, locks, and pools as needed. * Fix naming, labels, and any confusing UX points. 4. **Sign off and move to mainnet** * Once you’re happy with the structure, you replicate the configuration in your mainnet workspace. * Our team can help mirror your testnet setup into a production-ready mainnet instance. 5. **Keep testnet as a sandbox** * Use it later to test new staking campaigns, vesting templates, or dashboard changes before applying them on mainnet. *** ### Limitations & notes A few things to keep in mind: * **Separate from mainnet**\ Data and balances on testnet are completely separate from mainnet. Actions on testnet do not affect your real token or users. * **Test tokens only**\ You’ll need testnet tokens (and any testnet equivalents of your asset) to interact. We can point you to faucets or help you set this up. * **Not for production**\ Testnet URLs and contracts are for **internal testing and demos** only. Don’t share them as official investor or community links for mainnet behavior. *** ### Should you use testnet? Our default recommendation: * **Launching a new token?**\ Yes — always run at least one full dry run on testnet before mainnet. * **Already live and migrating to TMS?**\ Yes — especially if you’re moving large allocations or complex schedules into TMS for the first time. * **Small, low-risk experiment?**\ You might go straight to mainnet, but a testnet run is still the safest path. If you’re not sure, tell us your situation and we’ll recommend whether a testnet workspace makes sense for you. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://tms-finance.gitbook.io/tms.finance/getting-started/testnet-vs-mainnet.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.