BaseScan Ticket Follow-Up

GCA BaseScan Follow-Up

Use this page after the owner has already submitted one clean BaseScan token profile request from support@gcagochina.com and there is no reply in the same ticket. It centralizes the status-check template, reviewer evidence links, and boundaries for avoiding duplicate token-profile submissions.

This page does not submit BaseScan forms, send email, upload files, sign wallet messages, transfer tokens, approve swaps, or touch contracts. The owner must manually review and send any reply from the official project-domain mailbox.

BaseScan Handoff Resubmission Preflight Email Evidence Reviewer Map Tim Chen Profile Reply Templates

Official Mailbox support@gcagochina.com

Profile Status Returned; ready for owner resubmission

Contract 0x3197c42f4a06f7be32a9a742ac2a766f0ff682c6

Follow-Up Mode Existing ticket only

Use Conditions

Clean request already sentThe latest owner-controlled BaseScan request must already have been submitted from support@gcagochina.com.

Inbox checkedCheck the official inbox, spam folder, and BaseScan account notifications before sending a no-reply status check.

Public status currentDaily status must show the latest public snapshot and readyForBaseScanResubmission as true.

No duplicate ticketsreply inside the existing ticket/thread whenever possible. Do not open multiple token-profile submissions for the same correction cycle.

Latest Public Evidence

2026-06-15 Status Refresh

The latest public daily status snapshot was generated at 2026-06-18T08:31:47Z. It shows the public website check passing, the public registration API check passing, and the BaseScan preflight still marked readyForBaseScanResubmission with support@gcagochina.com as the current public project email.

Daily statusdaily-status.html; machine-readable status remains available for platform checks.

BaseScan preflightready-for-owner-resubmission; no tracked public files publish the old Outlook email or the personal Gmail.

Owner actionUse one existing-ticket follow-up from support@gcagochina.com only if the clean request was already submitted and there is still no BaseScan reply.

Project and Team

Use Team, Tim Chen Profile, About, and Whitepaper for project and founder transparency.

BaseScan Package

Use BaseScan Handoff, BaseScan Preflight, and Project Profile reviewer map for one clean owner-controlled submission path.

Domain Email

Use Domain Email, the DNS snapshot, and Email Evidence Checklist. Keep private mailbox screenshots off the public site unless a reviewer asks inside the ticket.

Contract and Supply

Use Technical Report, On-chain Proofs, Token Safety, Supply, and Reserve Statement.

Market Route

Use Markets and Liquidity for the Base Mainnet GCA/USDT pool. Current market depth is still starter-depth only.

Review Boundaries

Use External Reviews, Reviewer Kit, Trust Center, and Release Gates to avoid overclaiming audit, profile approval, or custody status.

No-Reply Status Check

Use this only after confirming the current clean request was already submitted from support@gcagochina.com and no reply is visible in the official mailbox, spam folder, or BaseScan account notifications.

Subject: Follow-up: GCA Token Profile Update - Base Mainnet Contract 0x3197c42f4a06f7be32a9a742ac2a766f0ff682c6

Hello BaseScan team,

I am following up on the GCA token profile update request for Base Mainnet.

Network: Base Mainnet / chainId 8453
Contract: 0x3197c42f4a06f7be32a9a742ac2a766f0ff682c6
Official website: https://gcagochina.com/
Official project email: support@gcagochina.com
BaseScan Handoff: https://gcagochina.com/basescan-handoff.html
Project profile reviewer map: https://gcagochina.com/project-profile.html#basescanMapTitle
Tim Chen professional profile: https://gcagochina.com/tim-chen.html
Domain email evidence: https://gcagochina.com/domain-email-evidence.html
Daily public status: https://gcagochina.com/daily-status.html
English follow-up page: https://gcagochina.com/basescan-followup.html
Chinese follow-up page: https://gcagochina.com/zh-basescan-followup.html

The current public materials address the prior information-insufficient return reasons: official HTTPS website, project-domain email, founder/team profile, whitepaper, brand kit, support page, domain email evidence, GitHub repository, Telegram, X, official GCA/USDT market route, and clear public claim boundaries.

The latest daily public status snapshot was refreshed at 2026-06-18T08:31:47Z and reports readyForBaseScanResubmission as true. Could you please confirm whether the request is still in the review queue, or whether any additional field correction or owner-wallet signature is required?

We will avoid duplicate token-profile submissions while this request is under review.

Thank you.

Before Sending

Confirm the latest clean BaseScan request came from support@gcagochina.com.
Confirm inbox, spam, and BaseScan account notifications have no reviewer reply.
Confirm daily-status.html opens and the current public snapshot is fresh.
Confirm basescan-handoff.html opens and still shows the current copy package.
Reply once inside the existing ticket and wait.

Do Not Claim

BaseScan approvalDo not claim token-profile approval until the BaseScan contract page publicly displays the submitted profile.

Third-party auditNo independent third-party audit has been completed.

Reserve or LP lockDo not describe reserves, LP, or custody as locked, vested, or multisig-controlled unless the on-chain custody path changes.

Market qualityDo not claim deep liquidity, price support, or ranking acceptance.

Wallet or contract actionBaseScan profile follow-up does not require approve, swap, transfer, wallet signature, or contract interaction unless BaseScan explicitly asks for ownership verification.