How to Update a Token Logo and Info on Robinhood Chain Blockscout
To update a token logo or project information on Robinhood Chain Blockscout, open the token page, choose Update token info, verify ownership of the contract, and send the metadata form for moderator review. The contract must exist on Robinhood Chain and its source code must already be verified. The ownership step uses a signed message from the contract creator or owner.
This workflow updates information displayed by the explorer. It does not rewrite the token contract, change its onchain name, symbol, decimals, supply, or permissions, and it does not constitute a listing, safety review, or endorsement.
Before You Start
Open https://robinhoodchain.blockscout.com/token/<contract> with your token contract address. Use the address actions menu and select Update token info. Depending on whether Blockscout already has a token-info record, the same action may initially appear as Add token info.
The live Robinhood Chain deployment requires an authenticated account with an email for this flow. You can start from the token page or go directly to My verified addresses. Before claiming the contract, check three things:
- The address is a smart contract on Robinhood Chain, not an externally owned account.
- The contract source code is verified in Blockscout.
- You can sign a message with the contract creator or contract owner address.
Do not share a private key or seed phrase. Blockscout asks for a signature over a generated message. Read that message in your wallet before signing and confirm that the wallet is connected to the expected network.
Verify Ownership
From My verified addresses, click Add address and enter the token contract. Blockscout checks the address before generating the ownership message. The current flow stops if the address does not exist, is an EOA, has unverified source code, or has already been claimed by another account.
- Enter the contract. Paste the exact Robinhood Chain token contract address and continue.
- Check the eligible signer. Blockscout shows the contract creator and, when available, the contract owner.
- Sign the generated message. Use a connected Web3 wallet or copy the message, sign it with another compatible tool, and paste the resulting signature.
- Confirm the claim. The recovered signer must match the creator or owner Blockscout expects.
If Blockscout reports an invalid signer, switch to the displayed creator or owner wallet. If that wallet is controlled through a multisig, factory, proxy administration setup, or another contract-based ownership pattern, do not improvise with a team member's EOA. Use the support contact shown in the explorer when the expected signer cannot complete the normal flow.
Ownership verification is reusable inside the account console. Once the address is verified, you can manage token-information requests without signing a fresh ownership message for every edit.
Submit Token Info
The token name and contract address are read-only in the current form. Prepare the required display metadata before opening it:
| Field | Current requirement | Preparation tip |
|---|---|---|
| Requester | Name and email | Use details the moderator can use to identify the request. |
| Project contact | Official project email | Use a project-controlled mailbox where possible. |
| Website | Official project website | Make the token contract easy to verify on the site. |
| Description | Required, maximum 300 characters | Write neutrally and remove unsupported claims. |
| Icon URL | Direct SVG download URL or direct 48×48 PNG URL | Test the final URL in a private browser window and make sure it returns the image itself. |
The form also supports optional project name and sector, documentation, a support URL or email, GitHub, X, Telegram, Discord and other social profiles, plus CoinMarketCap, CoinGecko, and DefiLlama links. A comment field is available with a 300-character limit. Add only official, working URLs; leaving an optional field empty is better than submitting an outdated profile.
The logo field expects a URL, not a local upload. Avoid a share page that wraps the image in HTML, a temporary signed URL, or a link that requires authentication. For PNG, match the displayed 48×48 requirement. For SVG, provide a direct downloadable file. The current form does not state a guaranteed file-size allowance, background rule, or CDN requirement, so do not invent one.
Review the preview, spelling, contract address, and links, then click Send request. A clean submission is still subject to moderation. Complete fields do not guarantee acceptance.
Track the Request
Return to My verified addresses to monitor the request. The current frontend includes IN_PROCESS, UPDATE_REQUIRED, REJECTED, and approved-state handling. While a request is IN_PROCESS, the form is read-only. If an administrator asks for changes or rejects the request, read the displayed comment before preparing the next submission.
Blockscout's status message says moderator review can take several days. Treat that as interface guidance, not a guaranteed service-level agreement. There is no evidence in this flow that payment, repeated submissions, or a support message can guarantee approval or a deadline.
After approval, open the public token page and check the logo, description, website, and links. Test the page in a signed-out browser session so you are checking the public result rather than account-only state. If the old image remains, rule out browser caching before filing another request.
| Explorer display metadata | Onchain token data |
|---|---|
| Logo, website, description, project links, and market-data links submitted to Blockscout | Name, symbol, decimals, supply behavior, ownership, roles, and contract logic recorded or enforced onchain |
| Reviewed and rendered by the explorer | Changed only through contract-supported transactions or deployment logic |
| Can be corrected through the token-info request flow | Cannot be changed by submitting an explorer metadata form |
Keep a dated copy of the submitted text and image URL so future maintainers know what Blockscout reviewed. For related launch operations, browse the PandaBoost Launch guides; manage the explorer request through Blockscout itself.
Build Visibility After the Update
Accurate explorer metadata helps users identify the project. PandaBoost helps token teams strengthen visibility across DEX screeners, wallets, and trading terminals.
FAQ
The current flow rejects an address that does not exist, is an EOA, has unverified source code, or is already claimed by another account. Verify the contract source and confirm that you entered the exact Robinhood Chain contract address.
The recovered signer must match the contract creator or contract owner shown by Blockscout. You can sign through a connected Web3 wallet or paste a valid manual signature; never share a private key or seed phrase.
In frontend v2.9.4, the icon field requests a direct URL to a downloadable SVG or a direct 48×48 PNG logo. The form does not publish a guaranteed file-size, background, or CDN rule.
The current status message says moderator review can take several days, but that wording is not a guaranteed SLA. A complete request does not guarantee approval or a deadline.
No. The request changes explorer-managed display metadata such as the logo, website, description, and links. It does not rewrite onchain name, symbol, decimals, supply behavior, permissions, or contract logic.
Whatever stage you're at — we're the stack.
Pre-launch? Bundle safe, warm wallets, fund quiet.
Post-launch? Trend on every scanner, chart and feed that matters.
The launch window is short. Don't waste it.