Public Reviewer Checklist

GCA Domain Email Evidence Checklist

This public page mirrors the owner evidence checklist for the active support@gcagochina.com mailbox before the next clean BaseScan token profile resubmission. It does not publish private mailbox screenshots and does not claim BaseScan token profile approval.

Status Evidence Collected
Current Public Email support@gcagochina.com
Target Domain Email support@gcagochina.com
Private Evidence Directory launch/domain_email_evidence

Current Boundary

The active public contact is support@gcagochina.com. DNS, inbound, outbound, and public-site alignment evidence is retained privately for reviewer follow-up.

Mailbox statusActive and aligned to support@gcagochina.com.
BaseScan statusReady for one owner resubmission; token profile approval is still pending BaseScan review.
Private evidenceMailbox screenshots, DNS proof files, and message screenshots must stay local and git-ignored.

Reviewer Use

A reviewer can use this page to see the exact evidence gates GCA is collecting, without requiring private mailbox screenshots to be posted on the public website.

Official plandomain-email.html
BaseScan remediationbasescan-remediation.html
Founder evidencetim-chen.html

Required Evidence Files

Five Files To Save Privately Before Resubmission

Provider statusdomain-email-provider-active.png: mail provider dashboard shows support@gcagochina.com as verified or active.
DNS proofdomain-email-dns-mx-spf-dkim-dmarc.txt: MX, SPF, DKIM, and DMARC lookup proof is saved after propagation.
Inbound proofdomain-email-inbound-test.png: inbound test from Gmail or Outlook to support@gcagochina.com is received.
Outbound proofdomain-email-outbound-test.png: outbound reply from support@gcagochina.com shows the visible domain sender.
Website proofsupport-page-domain-email.png: updated support page shows the same domain email used in the BaseScan form.

Execution Order

Do These In Order

  1. Choose a full mailbox provider that can receive and send as support@gcagochina.com.
  2. Initialize the local evidence directory with the evidence packet tool.
  3. Save provider proof showing support@gcagochina.com active or verified.
  4. Add provider MX, SPF, DKIM, and DMARC DNS records exactly as supplied by the provider.
  5. Save DNS proof after the read-only DNS checker reports readyForBaseScanEmailEvidence true.
  6. Send an inbound test from Gmail or Outlook to support@gcagochina.com and save the received-message proof.
  7. Reply from support@gcagochina.com back to Gmail or Outlook and save visible-sender proof.
  8. Switch public support/BaseScan email values only after DNS and mail-flow evidence are complete.
  9. Save support-page-domain-email.png showing the same domain email used in the BaseScan form.
  10. Build launch/domain_email_evidence_packet.json and run the BaseScan resubmission preflight.

Operator Commands

Read-Only And Local Evidence Commands

Initialize evidence directorypython3 tools/build_domain_email_evidence_packet.py --init-evidence-dir --evidence-dir launch/domain_email_evidence
Check DNSpython3 tools/check_domain_email_dns.py --domain gcagochina.com --mailbox support --dkim-selector <provider-selector> --json
Build evidence packetpython3 tools/build_domain_email_evidence_packet.py --dkim-selector <provider-selector> --evidence-dir launch/domain_email_evidence --website-email-updated --output-json launch/domain_email_evidence_packet.json --output-md launch/domain_email_evidence_packet.md --json
Final preflightpython3 tools/check_basescan_resubmission_readiness.py --json --require-ready

Stop Conditions

Do Not Submit BaseScan If Any Condition Is True

Boundaries

What This Checklist Does Not Do

No DNS Writes

The checklist does not write DNS records. The owner must enter provider records in the DNS host.

No Email Sending

The checklist does not send email or test mailbox flow automatically.

No BaseScan Submission

The checklist does not submit BaseScan requests or claim BaseScan approval.

No Wallet Actions

The checklist does not touch wallets, contracts, liquidity, private keys, or token transfers.

No Secret Storage

The checklist does not store mailbox passwords, API keys, DNS tokens, or private evidence in public files.

No Private Screenshot Publishing

Private mailbox screenshots and proof files must remain in the git-ignored evidence directory.