Use Connect Cryptik Wallet or MetaMask, then get free test ETH for your deployment wallet. The public RPC is rate-limited; use modest request rates and retry temporary failures. Node administration and debug methods are not public.
02 · DEPLOY
Start with Remix + MetaMask
This path keeps each deployment under your wallet’s confirmation. You do not need to give this website a wallet key.
Choose an example
Download a .sol file below. Open Remix IDE ↗ and import the file into a workspace, or create a file with the same name and paste its contents.
Compile with matching settings
Select Solidity 0.8.37, optimizer enabled, 200 runs, and EVM target Shanghai. Compile the file. Imports pin OpenZeppelin Contracts to 5.6.1. Select the example contract, not an imported dependency.
Select the network and account
In Deploy & Run, select Browser Extension → MetaMask (older Remix versions call this “Injected Provider”). In MetaMask, choose Cryptik Testnet and your test-funded account. Confirm the chain ID is 20260922. Leave deployment Value at 0.
Review and deploy
For CustomTestToken, expand the constructor fields and enter a name, symbol and whole-token supply, such as My Community, MYC, 1000000. MockUSD has no constructor inputs. Click Deploy, then review the network and fee in MetaMask before confirming.
Keep your deployment record
Save the transaction hash, deployed contract address, source, compiler settings and constructor arguments. A submitted transaction can take time to appear in the explorer; check its receipt before submitting another deployment.
The downloadable contracts reject deployment on other chain IDs. They are learning examples, not audited production contracts. See the official Remix deployment guide ↗.
03 · CUSTOMIZE
Two starting points
These contracts deploy directly from your wallet. They do not go through the website’s fixed-supply factory.
Fixed supply · 18 decimals
CustomTestToken
Choose your name, symbol and initial supply. Your deploying wallet receives the whole supply. There is no later minting, administrator role or transfer tax in this example.
Try it: deploy 1,000 tokens, check totalSupply and balanceOf, then transfer one token using 1000000000000000000 base units.
An unbacked test token starting with zero supply. The deploying wallet receives admin and minter roles. Admins can grant or revoke minter roles; minters can issue tokens up to a one-billion-token outstanding supply cap. Holders can burn their own tokens; burning another holder’s tokens requires their allowance.
Try it: call mint(yourAddress, 1000000) to issue 1 test mUSD. Call burn(1000000) from that holder to destroy it. Try minting from a second wallet without the minter role: it must fail.
This example has no reserves, redemption, dollar peg, oracle or collateral system. Burning tokens does not pay out money. An admin controls who can mint; do not present mUSD as real dollars.
Sources use the MIT license and pinned OpenZeppelin ERC-20 building blocks ↗. OpenZeppelin license. Compiler input includes all imported sources for reproducible compilation. Changing source paths, settings or code can change bytecode.
04 · CHECK YOUR WORK
Find it in the explorer
Open the Cryptik Explorer and search your transaction hash. Check success, the deploying wallet, contract address and network fee.
Search the deployed contract address. Confirm token name, symbol, decimals, supply and transfers once indexing catches up. A token’s address identifies it; names and symbols are not unique.
Use Remix’s deployed-contract controls to read balances and roles. Test expected failures as well as successful transfers. Do not assume that a successful deployment means the logic is correct.
Source verification status
Public source-code verification is not enabled in this explorer yet. There is no source-upload or “Verify & Publish” flow. Preserve the downloadable Standard JSON compiler input, compiler version, settings and constructor arguments for a future verification service. Never claim a contract is source-verified because its transaction succeeded.
For these unmodified, non-proxy examples, developers can compare deployed runtime bytecode from eth_getCode with the runtime field in the build output. This is a bytecode comparison, not an explorer verification badge or a security audit.
Where your token appears
You can import ERC-20 contract addresses in the Cryptik Wallet Chrome extension or MetaMask on Cryptik Testnet. Approved registry logos appear automatically in Cryptik Wallet. The website’s factory-token list and Cryptik Wallet build 47 currently support only the approved factory template. These custom contracts will not appear there through “Add test token”; broader custom-token wallet support is a separate feature.
DESIGN BEFORE LAUNCH
A stablecoin needs more than a name
Use MockUSD to learn issuance and permissions. A real stablecoin project also needs a defined backing and redemption model, minting authority, reserve or collateral accounting, failure handling, independent security review and jurisdiction-specific legal review. Some designs additionally need price feeds and liquidations. No template guarantees a stable price.
Cryptik Testnet is a place to test that design with valueless assets. It is not a real-money stablecoin launch platform.