Verify Your Token on Basescan
Verify your token contract source code to build trust and transparency. This allows anyone to view and audit your contract code.
⚠️ Important Prerequisites
1. Etherscan Account Required: You need an Etherscan account to get your API key for verification.
- Go to etherscan.io and create a free account
- Go to your account dashboard → API Keys
- Create a new API key (name it "BaseScan Verification" or similar)
- Copy your API key - you'll need it for Remix verification
2. Why needed? BaseScan uses Etherscan's universal EVM API, so one API key works for all EVM networks including Base.
🎯 For Token Creators: Use the Remix IDE guide below to verify your token contract. No downloads, no Node.js, no complex setup required!
Step-by-Step Remix Verification Guide
Open Remix IDE
Open Remix IDE in your browser
Install Contract Verification Plugin
Open Plugin Manager (right-hand side wall socket icon) and search:
Maintained by Remix
Verify contract code on Sourcify, Etherscan and Blockscout at the same time"
Activate Contract Verification plugin by clicking the small on/off button after the plugin name
🔑 API Key Setup: In the plugin settings, enter your Etherscan API key (from step 1 above)
Create Contract File
Create new file, name it UnRugableToken.sol
Copy Contract Source Code
Copy the UnRugable Token Contract Source Code and paste it to the UnRugableToken.sol file.
Configure Compiler
Solidity Compiler tab:
- open Advanced Configurations
- ✅ Check "Use configuration file"
- Compiler will auto-set to 0.8.32
Click "Update config remix.config.json"
Copy and paste this to the remix.config.json file, click "Compile remix.config.json":
• Click "Compile UnRugableToken.sol"
Constructor Arguments:
0x7A1255992a4597083CF9E8468D17a60D73d8F6D40x4eaf3fe591898895102dfbc7487f45bab4454deb0x036CbD53842c5426634e7929541Ec2318f3dCf7EImportant Warning
_creator, _devFeeRecipient, and _usdc addresses cannot be changed because the token is renounced at launch. Any modification to these 3 field values will fail token verification.
In Remix Contract Verification Plugin:
- Network: Base Mainnet
- Contract Address: Use the address above
- Copy the constructor arguments above to the plugin
Click "Verify on BaseScan" - Done! 🎉
Troubleshooting
Error: "Constructor arguments invalid"
Try leaving constructor arguments blank. Basescan can usually auto-detect them from the deployment transaction.
Error: "Bytecode does not match"
Make sure you're using compiler version v0.8.31+commit.fd3a2265 and the JSON file matches exactly:Compiler: v0.8.31+commit.fd3a2265
License: BUSL-1.1
Optimizer: Enabled, Runs: 200
viaIR: Enabled
Contract Name: UnRugableToken
Error: "Cannot find module @openzeppelin" or "File import callback not supported"
This happens when using "Single file" method with npm imports. Solution:
• Use "Standard JSON Input" method instead (the contract source is already flattened)
Still having issues?
Make sure you're on the correct network. You can also try using Hardhat's verification plugin for automated verification.
After Verification
Once verified, your contract will show:
- ✅ Green checkmark indicating verified contract
- 📄 Full source code visible to everyone
- 🔍 Ability to read and interact with contract functions
- 📊 Better trust and transparency for users
⚠️ Important Note About Ownership
UnRugable tokens have renounced ownership for maximum security. This means:
- You cannot update contract metadata or add images on BaseScan after verification
- The contract information is permanently locked for security
- This prevents any future modifications and builds maximum trust
- Users know the contract will never change after deployment