Next-Step Operating Plan

GCA Action Plan

This page turns the current GCA status into a practical order of work: verification follow-up, market quality, public content, member-access buildout, and optional trust upgrades.

It is not financial advice, a buy or sell recommendation, or a claim that any external platform has approved GCA unless that approval is already listed on the status pages.

Network Base Mainnet / chainId 8453
Contract 0x3197c42f4a06f7be32a9a742ac2a766f0ff682c6
Official Pool GCA/USDT 0xfe6a598bf738d7eec9640897064ca3a490128d3d447ced96077aef8e9dd1c1d0 / Base USDT 0xfde4C96c8593536E31F229EA8f37b2ADa2699bb2
Profile Status BaseScan returned 2026-05-23; owner package ready

Highest Priority

What To Do Next

Use this order when deciding what to work on first. The goal is stronger public trust and clearer user access, not artificial trading activity.

1. Submit One Clean BaseScan Update

BaseScan returned the token profile update again as information-insufficient on 2026-05-23. Tim Chen professional profile evidence, the Project Profile BaseScan reviewer map, the domain email setup plan, public evidence checklist, activation evidence packet, BaseScan Handoff copy blocks, Chinese owner flow, and support@gcagochina.com evidence are ready; the 2026-05-30 DNS snapshot shows MX, SPF, DKIM, and DMARC present. The next step is one owner-controlled BaseScan resubmission from the official domain mailbox, then wait for BaseScan review without duplicate follow-ups.

2. Improve Market Quality Legitimately

Use clear official routes, user education, organic content, support responses, and optional deeper liquidity. Do not create fake or coordinated trading activity.

3. Make Member Access Real

Public account intake, read-only wallet checks, and eligible ledger records are live. The next product step is stronger status review, support workflow, and service delivery around the ledger path.

4. Publish Consistent Content

Keep the Go China narrative active with project updates, risk education, and member utility previews. Content must not promise price results.

5. Choose Trust Upgrades When Needed

Third-party audit, LP lock, Safe multisig, or reserve vesting can reduce reviewer concerns, but they require outside vendors or on-chain actions.

6. Keep Boundaries Public

GCA should be described as concept-stage product buildout with a live fixed-supply token, not a finished trading platform or externally audited asset.

Current Daily Queue

BaseScan Action Queue From Latest Daily Status

The public daily status page turns the latest safe ops snapshot into a reviewer-readable queue. This action plan mirrors the current blocker order without exposing private evidence, user records, or admin data.

Daily status sourcedaily-status.html
1. Maintain domain mailboxKeep support@gcagochina.com working for inbound and outbound reviewer mail.
2. Retain email evidenceKeep provider, MX, SPF, DKIM, DMARC, inbound, outbound, DNS, and website evidence archived privately.
3. Keep public email alignedTracked public files now use support@gcagochina.com in one controlled pass.
Old-email switch queueCurrent daily status reports filesStillUsingOldEmail as 0 tracked files across site/support.html, site/support.json, site/project.json, and BaseScan launch materials.
4. Confirm project profile mapUse Project Profile Map so the return-reason evidence chain is visible before final preflight.
5. Final BaseScan preflightRun tools/check_basescan_resubmission_readiness.py --json --require-ready before sending the one clean BaseScan submission.
6. Copy owner submission packageUse BaseScan Handoff and 中文 BaseScan 提交流程; no wallet transaction, approve, swap, or contract operation is needed.

Do Now

Submit BaseScan update onceUse Project Profile Map, 中文 BaseScan 提交流程, and BaseScan Handoff from the owner browser session with support@gcagochina.com.
Maintain domain email gateKeep support@gcagochina.com, MX/SPF/DMARC/DKIM, the public evidence checklist, readyForBaseScanEmailEvidence, and the private evidence packet ready for reviewer follow-up.
Current DNS status2026-05-30 snapshot: MX present, SPF present, DKIM present, DMARC present; MX/SPF/DKIM/DMARC present.
Use the readable site mapsite-map.html
Share verification before links to DEX pagesverify.html
Route support through the official intake pagesupport.html
Publish safe campaign content manuallypublishing-desk.html
Keep official pool identity consistentGCA/USDT on Base

Do Later

Commission third-party auditOptional until budget and need are clear
Move reserve to Safe multisig or vestingRequires owner on-chain action
Lock LP or publish LP custody proofRequires custody decision
Tracked listing outreachWait for stronger market quality and public activity
Duplicate BaseScan follow-upsWait for BaseScan reviewer response after one clean owner submission
Public account pathLive for intake, wallet verification, and eligible ledger records

Public Claim Boundaries

What Not To Say

These limits protect the project from misleading users and from creating avoidable review problems with wallets, explorers, and listing platforms.

Readable Reference Path

Use These Pages First

Normal users and community moderators should start from the readable verification, trust, status, technical, reserve, and support pages.