Member Benefit Transfer Runbook / 2026-07-27

GCA Member Benefit Transfer Runbook

This page defines the manual operator controls for the one-time 10,000 GCA member benefit transfer after support review, 30-day holding-period verification, and member ledger approval.

The transfer is not automatic. If approved, it must come from the published reserve wallet on Base Mainnet; the GCA token contract has no mint function. After the operator sends it, the production Worker verifies the receipt and stores append-only evidence.

Member Benefit Rules Member Ledger Schema Operations Runbook Reserve Disclosure Technical Evidence

Amount 10,000 GCA

Source Owner reserve

Transfer mode Manual only

Evidence API /gca/member-benefit-transfers

Transfer Policy

NetworkBase Mainnet / chainId 8453

Token0x3197c42f4a06f7be32a9a742ac2a766f0ff682c6

Source wallet0x5e8F84748612B913aAcC937492AC25dc5630E246

RecipientApproved verified member wallet only

Repeat ruleOne transfer per approved registered user

Before Transfer

Packet versiongca_member_preregistration_v2

Member statusactive with verified holding evidence

Tx hash checkevidenceTxHashFormatOk = true

Holding periodAt least 30 days verified

Fresh balance checkRead-only balanceOf

Manual Transfer Steps

1. Confirm Review Record

Confirm registrationId, walletAddress, holdingStartDate, evidenceTxHash, evidenceTxHashFormatOk, holdingPeriodDaysVerified, and eligible status.

2. Verify Current Balance

Run a fresh read-only Base Mainnet ERC-20 balanceOf check for the verified wallet before preparing a transfer.

3. Prepare Reserve Wallet

Use the project or owner-held reserve wallet on Base Mainnet. Do not request user secrets, custody, or fund transfers.

4. Send 10,000 GCA

Send exactly 10,000 GCA to the approved verified Base wallet. Confirm token contract and recipient before signing.

5. Verify and Record Evidence

After confirmation, run tools/record_cloudflare_member_benefit_transfer.py. The protected Worker checks the successful receipt, Base safe block, official reserve sender, GCA contract, approved recipient, and exact amount.

6. Close Review

The verified D1 write sets memberBenefitClaimStatus to transferred. Do not close a record from a screenshot or statement alone.

Required Ledger Fields

memberLedgerIdApproved member record

transferRecordIdAppend-only D1 evidence record

transactionHashPublic Base transaction hash

safeSnapshotBlockNumberBase safe-block snapshot

amountGcaExactly 10,000 GCA

verificationStatusverified

Do Not Collect

Private key or seed phrase.
Exchange API secret or withdrawal permission.
One-time code or recovery phrase.
Custody request or fund-transfer request.

Member Transfer References

Use the readable runbook, reserve disclosures, and support pages first. Transfer execution remains manual; production evidence verification is live and token-protected.

Live member account/gca/member-access

Member benefit pagemember-benefit.html

Member ledger pagemember-ledger.html

Operations pageoperations.html

Production evidence packetgca_member_benefit_transfer_v1

Verification ruleSuccessful safe receipt + one exact Transfer log

Supply and reserve pagessupply.html / reserve-statement.html

Public Claim Boundaries

Safe to say: GCA has a manual transfer runbook and a production evidence-verification route for the one-time 10,000 GCA member benefit.
Safe to say: evidence is stored only after the Worker verifies a successful transaction at or below the Base safe block from the official reserve to the approved member wallet.
Do not say the 10,000 GCA member benefit is self-service claimable today.
Do not say holding 1,000,000 GCA automatically triggers a transfer.
Do not say the evidence route signs, authorizes, or broadcasts the transfer.
Do not describe the member benefit as newly minted, cash, income, reimbursement, trading permission, voting control, lifetime access, price support, or risk-control bypass.