A token page that reflects the project people meet
Picture a two-person game studio in the week its audit report is published. The team notices that its explorer page still has an old logo and links to a former social account. We would gather the current details and prepare a clear request for the right page.
An explorer token update is a request to add or correct public information connected with a token page. Depending on the explorer and the record, that information may include the project name, logo, short description, website and social links. We help bring those details into one consistent set before submission.
That care matters when someone checks the token address and finds a page that does not match the project’s current identity. It can also help after a rebrand or a change to official channels. We start by identifying the chain, address and page you want changed. Then we compare the requested details with the project’s own public materials.
If the task touches a wider directory or another kind of listing, our listings and verification support may be useful too. A contract change or rebrand may also need a separate migration and rebranding update. We’ll help you separate those needs, so the explorer request stays focused.
What should be ready before an explorer request?
A useful submission begins with details that agree with one another. We ask for the network, contract address and current explorer page first. Then we can check which record needs attention and what the team wants changed.
The identity set
Prepare the exact project name and a short description. Include the logo file the team wants associated with the token. We check that the image represents the project and that the name and description match its official materials. The explorer’s current instructions determine any file requirements. We check those rather than assume one format fits every destination.
The links people should reach
Send the official website and social URLs you want shown. We open each link and look for spelling errors or destinations that no longer represent the project. A quick 3-part check covers the address, the project identity and the links. It catches simple mismatches before anyone submits the request.
For example, suppose the website has moved but the project’s public profile still points to the old address. We would flag that difference and ask which destination is official before preparing the request. If the concern is a profile on a trading data service instead, our DEXTools and DEXScreener profile updates cover a different set of pages.
Four moves from token address to public-page check
We keep the work in clear steps, so your team knows what is ready and what still needs input. The chain and explorer guide the route. Your project contact confirms the official details.
- Identify the record. Share the network, contract address and current explorer page. We confirm which page and requested change are in view.
- Gather the project details. Send the preferred name, short description, logo, website and social links. Include any earlier request or note about a rebrand.
- Check and prepare. We compare the materials for consistency and review the relevant explorer’s current instructions. If something is missing, we ask before the submission is prepared.
- Support submission and follow up. We guide the authorized contact through the applicable route. We keep a record of what was sent and compare the public page with the requested update afterward.
The authorized project representative may need to provide evidence or complete an account step. We make that handoff clear. We won’t treat access or approval as something we can do on the team’s behalf. If a wallet-facing logo is also on your list, wallet logo and token list support is a separate task with its own destination.
A clear handoff for your team and the explorer
The handoff gives your team a tidy record of the requested change and the information used to prepare it. It also makes the next check easier: you can compare what was sent with what later appears on the public page.
| Part of the handoff | What it covers |
|---|---|
| Token record | Network, contract address and current explorer page |
| Project details | Preferred name, short description and logo |
| Official destinations | Website and social URLs checked with the team |
| Submission note | What was prepared and which route was followed |
| Page follow-up | Whether the requested details are visible or need another step |
We keep the materials tied to the explorer and address you identified, rather than mixing details from different token pages. If your team is also working through directory listings, see our support for other crypto trackers. It helps keep the tasks clear and separate. An explorer page update is not the same request as a tracker listing or a wallet token list.
Your team prepares the facts; the explorer handles review
The project controls the accuracy of the details it supplies and can respond to requests for more information. The explorer controls whether the request meets its current requirements. It also decides whether or when the public page changes. We prepare the agreed materials and help the authorized contact with the submission, but cannot decide the explorer’s review outcome.
That boundary is worth keeping in view when planning around a logo correction, new links or a changed project name. The work we can confirm is the preparation, submission support and follow-up we agree with you. A public page may still need another action if the explorer asks for clarification.
At Brand Community, we check the supplied address against the page you want updated. Then we review the identity details and links before preparing the request. To get started, send us the network, contract address, current explorer page and a short note about the change. We’ll review what you have, point out any missing material and agree the next step with your project contact.
How it works
- Share the token recordSend the network, contract address and current explorer page. Add a short note explaining what you want changed.
- Gather official detailsProvide the preferred name, description, logo, website and social links. Mention any rebrand or earlier request.
- Check the materialsWe look for mismatches and review the relevant explorer’s current instructions before preparing the request.
- Support the submissionWe guide the authorized project contact through the applicable route and record the information provided.
- Review the public pageWe compare the page with the requested changes and explain any next action visible to the team.
Frequently asked questions
Which explorer pages can this support cover?
We help prepare token information and logo update requests for Etherscan, BscScan, Solscan and Tonviewer. Share the network and contract address first. That lets us identify the relevant page and check which submission route applies to the change you have in mind.
Can one logo file work across all four explorers?
It may be possible to start with the same project logo, but we check each explorer’s current instructions before preparing a submission. The formats or supporting details requested can differ. Send the file you use officially, and we’ll flag any destination-specific requirement we find.
If only the logo is wrong, should we update every field?
Not necessarily. We can prepare a request focused on the logo, while still checking the contract address and confirming the image matches the project’s identity. If other details are outdated, we’ll point that out. Then you can decide whether to include them in the same request.
When might the corrected details appear on the page?
Preparation can begin once we have the address and project materials. After submission, the relevant explorer controls its review and publication timing. We can check the public page afterward and share what is visible, along with any next step shown to your team.
What if the explorer asks the team for more information?
The authorized project contact may need to provide evidence or complete an account action. We can help organize the response and check it against the original request. For instance, if the project name changed, a clear note explaining that change helps keep the follow-up focused.
Does an explorer update also add the token to a wallet list?
No. An explorer update concerns information on that explorer’s token page. A wallet token list or wallet logo process is a separate request with its own destination and instructions. If that is part of your plan, we can discuss it as a separate wallet logo support task.
Tell us about your project
Answer four quick questions and a manager will send you a plan, timing and a price range within the hour. Everything stays confidential.
Loading the form…