Overview
Token pages on Blockscout can display extra information beyond what’s on-chain. This can include project description, website, social links, and a verified icon. To add or update this information, you submit a request that goes through a QA review. What you’ll need (minimum information required):Two ways to submit
Your submission path depends on whether the wallet you’re submitting from can be automatically tied to the token.Path 1: Submission using the deployer address
If you control the wallet that deployed the token, verification is fast. Automated checks confirm the wallet information and you can go directly to token info submission. Steps:- Log in to Blockscout using the same address used to deploy the token (you should also have an email address associated with this log in, add if you haven’t done so already).

- Go to the token contract. You can access this in several ways.
- Paste the token contract into search, then click the 3 dots to access Add Token Info

- Access from the Verified addrs item in your account dashboard.


- Access from the Verified addrs item in your account dashboard.
- Enter your token details and Send request.


Path 2: You can’t submit from your wallet on the Blockscout UI

- Send an email to submissions@blockscout.com with your wallet, token information, and an explanation of your relationship to the project.
- You will receive a reply with a link to provide additional specific information to the Blockscout team.
- The team will review the proof and confirms the provided information manually before moving forward.
Expedited Payment Process
- Ethereum, Optimism, Base: 0x242ba6d68FfEb4a098B591B32d370F973FF882B7
- Robinhood: 0xF3e177A4034cF6e57cCBe80108cAe6f3729C6649
- Path 1: you will be contacted during the review process if you would like to pay for expedited review.
- Path 2: you will have the option to pay as a part of the during the manual submission.
Review Process: what happens after you submit
Wallet verification
Path 2 submissions are reviewed manually against the proof you provide.
Duplicate and impersonation check
Optional website and social review
Wallet connection review
Final decision
Possible outcomes
Approved — your token info is confirmed and published shortly after. More information requested — this typically means we couldn’t confirm wallet ownership, or something in your submission was incomplete or inconsistent. You’ll get a follow-up describing what’s needed. Rejected — a rejected submission must restart the full process, including a new fee if you want expedited processing.Common reasons for rejection
- Payment issues. The transaction can’t be confirmed on-chain, the amount is incorrect, or the transaction hash was already used on another submission.
- Wallet doesn’t qualify. You couldn’t provide sufficient proof of ownership for the token.
- Token impersonation. The token exactly copies the name, symbol, and branding of an established token.
- Phishing behavior. A linked website contains phishing content or redirects to a suspicious domain.
- Suspicious wallet permissions. A linked website’s wallet-connect feature requests unlimited spending approvals, unexpected token approvals, or access to unrelated assets.
- Requests for private keys or seed phrases. Anywhere in the website or submission flow.
- Misleading or misrepresented information. Submitted details are inaccurate or intentionally misleading. Token name, logo, designs, symbol, and other information are fraudulent, infringe copyright, or misrepresent public entities.
FAQ
Is the fee for expedited review refundable?
Is the fee for expedited review refundable?
Which networks can I pay from?
Which networks can I pay from?
How long does review take?
How long does review take?
What if I no longer control the deployer or first-buyer wallet?
What if I no longer control the deployer or first-buyer wallet?
Can I submit more than one request for the same token while I wait?
Can I submit more than one request for the same token while I wait?
Can I edit my submission after sending it?
Can I edit my submission after sending it?
What happens if my token is a duplicate of an existing one?
What happens if my token is a duplicate of an existing one?