Start with the wallet view your members see
Wallet asset support helps your token’s information make sense at a specific destination. We check the details and logo materials you share. We clarify the request, then help prepare the agreed submission or follow-up.
Picture a studio about to open a closed beta. Its campaign has ended, but nobody wrote down what happened or which wallet details need attention. We’d begin by asking the team to show us the current wallet view. Then we’d ask it to name the exact change it wants. We’d record the visible issue and assemble the details needed for review.
That small first step matters because wallet display, a token-list entry and a verification request are not interchangeable. Your asset might already appear by contract address while its logo or other details need review. Or the team may need to gather public references before making a request. We identify which situation you’re facing before preparing anything.
If the issue belongs to a broader directory rather than a wallet, we can help compare the right route. See other crypto tracker listings. The listings and verification overview can also help separate wallet work from tracker submissions. Our first check is simple: where does the problem appear, and what should users see instead?
How do you choose between Trust Wallet and Jupiter requests?
Trust Wallet asset work and Jupiter verification are separate requests. We prepare them as distinct tasks, even if both use some of the same project details.
For a Trust Wallet request, we organize the approved token information and logo materials. Then we check that the public references you provide point to the same asset. For Jupiter, we review project information relevant to that verification request. We help organize its supporting material. We don’t treat one request as proof that another destination has changed.
Say your token is already visible in a wallet, but its logo looks out of date. We’d compare that view with the logo and details your team has approved. Then we’d identify whether you need a wallet request or a profile correction. If you also need a separate directory listing, our Jupiter listing support is not a substitute for wallet work. We’ll clarify which destination each request concerns.
Before starting, write down the specific result you want checked: a logo, searchable asset details, a verification request, or a particular token-list entry. That one-line goal gives your team and ours a shared way to review progress.
Bring these five pieces of information
A wallet request is easier to prepare when one approved set of project details is ready to check. Gather the following items and choose one team contact who can confirm them.
- Chain and contract address: the public reference for the token.
- Token details: the approved name, ticker and short description.
- Logo files: the version your team wants users to see.
- Project links: the official website, social accounts and relevant public documentation.
- Current issue: the wallet name, visible problem and a screenshot or clear description.
We compare these materials for mismatches. We check for different tickers across project pages, an address that doesn’t match the request, old links or an unapproved logo. If the project has changed its name or contract, explain the old and current details together. Our contract migration and rebranding support can help keep that history understandable.
For example, suppose a token has a current logo but an older project page still shows the previous one. We’d flag both references for your approval before preparing the request. Please don’t send private keys or recovery phrases; they aren’t needed. If public token details also need correction, consider an explorer token information update alongside the wallet task.
A simple record makes wallet tracking easier
We make wallet tracking useful by recording the exact destination, the information used and the status your team can see. That gives you a practical reference when you check the asset again or plan a separate update.
| Checkpoint | What we look at | What you can keep |
|---|---|---|
| Current view | The wallet, asset and visible issue you identify | A note of where and how you saw it |
| Approved details | The contract reference, token details, logo and official links | The version your team confirmed |
| Request activity | The destination and materials used for the agreed request | A record of what was submitted |
| Follow-up | Any response or change visible to your team | A note of the next action, if needed |
We keep one record per destination. That way, Trust Wallet details don’t get confused with Jupiter or another token list. When an existing profile is the real issue, our profile update support may fit better. If your team is also preparing for tracker discovery, we can point you to CoinGecko listing support or CoinMarketCap listing support.
After a change, your team can compare the current wallet view with the approved details. That check helps you see whether the specific issue has changed. It doesn’t assume that another wallet has made the same update.
From your first note to a clear handoff
We move from a clear request to prepared materials and a useful record. One project contact confirms the details. The working schedule follows the destination, your starting materials and any needed follow-up.
- Name the destination. Tell us whether you’re asking about Trust Wallet, Jupiter, another wallet list or several separate destinations. Describe what looks wrong or what you want reviewed.
- Share public references. Send the contract reference, official project links, approved token details, logo files and a screenshot or description of the current view. Choose one team contact to confirm the information.
- Review and hand off. We check for inconsistencies and return a short list of corrections for approval. Then we prepare the agreed request. We keep a record of what was submitted and any status or response your team can see.
The platform controls its own eligibility decision, review and display updates. We can’t promise approval, timing or that another wallet list will show the same information. We can commit to the agreed preparation, submission support and record of visible progress.
If another request comes into view, we’ll name it separately before the work changes. To start, send Brand Community the wallet or platform name, public contract reference, official links and the current view through our contact page. We’ll review those materials and confirm the next actions with you.
How it works
- Name the destinationTell us whether the request concerns Trust Wallet, Jupiter, another wallet list or separate destinations. Describe what you want reviewed.
- Share public referencesProvide the contract reference, approved token details, official links and logo files. Choose one team contact to confirm them.
- Check the asset detailsWe compare the materials and return a short list of missing items or mismatches for your approval.
- Prepare the requestOnce your team confirms the details, we organize the materials and support the agreed submission.
- Keep a clear recordWe share what was submitted, any status your team can see and the next action, if one is needed.
Frequently asked questions
Will one wallet logo update change how every wallet shows my token?
No. A logo request concerns its named destination; it doesn’t establish that other wallets or token lists have updated their information. We record the wallet or list involved, so your team can check the specific view afterward. If you want to address another destination, we’ll define that as a separate request.
What should I send before we review my token?
Send the public contract reference and chain, approved token name and ticker, logo files, and official project links. Also include a screenshot or description of the issue. Please also choose one person who can confirm details for your team. That gives us a clear starting point without asking for private keys or recovery phrases.
Can you help when the token appears but its details look old?
Yes. Share the wallet view and the current details your team approves. We’ll check whether the issue concerns a wallet request or a separate profile correction. Then we’ll organize the relevant follow-up. A screenshot and one approved source for the new details make the review clearer.
Is Jupiter verification the same request as Trust Wallet asset inclusion?
No. They have separate destinations, so we prepare and track them independently. The same approved token details may help with both, but completing one request doesn’t tell you whether the other has been reviewed. We’ll list each requested destination in your work record.
How long will a wallet request take?
We agree on the working schedule after checking the destination and your materials. Our part starts with a consistency review, then preparation and any agreed follow-up. The platform sets its own review and display timing. We’ll share the status visible to your team rather than give an unsupported completion date.
Can you promise that Trust Wallet or Jupiter will approve the request?
No. Trust Wallet or Jupiter decides eligibility, review outcomes and when a display changes. We can commit to the agreed preparation and submission support. We’ll also check your materials for consistency and provide a record of what your team can see. We’ll keep the request tied to its named destination.
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…