GCA Member Ledger Schema

Public data contract for the live GCA AI Quant Access account layer: wallet verification, redacted device-key status, one-time 100 GCA AI Quant Access credits, GCA Member status, observed 30-day holding evidence, and verified evidence for already-completed manual 10,000 GCA reserve transfers.

Pre-Registration Member Benefit Review Utility Thesis Risk Verify GCA Technical Evidence

Status Workers + D1 live

Holder Bonus 10,000 GCA

Credit Ledger 100 credits / 180 days

GCA Member 1,000,000 GCA / 30-day hold

Member Activation Token-protected manual review live

Benefit Evidence Protected production verification live

Live HTTPS Paths

The public account page uses the Workers + D1 backend for member access intake, read-only wallet verification, eligible credit writes, queued member evidence, redacted device-key status refresh, credential-only device-key rotation, and registered-email lost-key recovery. Protected full ledger reads and member decisions remain operator-only.

Member access page/gca/member-access

Redacted account statusPOST /gca/account-status

Device key rotationPOST /gca/account-status/rotate

Lost-key recoveryPOST /gca/account-status/recovery-requests + /recover

Pre-registration intake/gca/pre-registrations

Wallet verification/gca/wallet-verifications

100 credits ledger/gca/credit-ledger

GCA Member ledger/gca/member-ledger

Production member review/gca/member-reviews

Holding verification evidence/gca/holding-verifications

Member benefit transfer evidence/gca/member-benefit-transfers

Local support review/gca/member-review

Public member benefit rulesmember-benefit.html

Member benefit transfer runbookmember-benefit-transfer.html

Member packet versiongca_member_preregistration_v2

Account status versiongca_account_status_v1

Token Verification

NetworkBase Mainnet / 8453

Contract0x3197c42f4a06f7be32a9a742ac2a766f0ff682c6

MethodERC-20 balanceOf read

Wallet ruleOne verified wallet per registered user

Support overrideNo manual balance override

Redacted Account Status

gca_member_access_v2 creates a random browser device key and D1 stores only its SHA-256. gca_account_status_v1 returns account, verification, credits, member-review, and benefit state without email, full wallet, the key, administrator data, or operator notes. gca_account_status_rotation_v1 changes only that hashed credential and gives the old key a 15-minute same-rotation retry window. Lost-key recovery requires registered-email review and a single-use credential, then invalidates the old key without modifying the account or ledgers.

Pre-Registration Record

Fields: registrationId, createdAt, email, Telegram, walletAddress, declaredGcaBalance, programIntent, memberBenefitReviewEvidence, termsAccepted, securityBoundaryAccepted, and source.

Wallet Verification Record

Fields: walletAddress, chainId, contractAddress, checkedAt, gcaBalance, holderBonusEligible, gcaMemberEligible, holdingPeriodDaysVerified, verificationProvider, and status.

Member Benefit Evidence Record

Fields: holdingStartDate, daysSinceHoldingStartPreview, holdingPeriodPreviewEligible, evidenceTxHash, evidenceTxHashFormatOk, evidenceNote, final review flag, and no-ledger-write flag.

Support Review Record

Fields: reviewId, registrationId, status, updatedAt, publicEvidenceReference, and supportNote. Statuses: received, wallet_pending, eligible, needs_more_information, rejected, and ledger_recorded.

Production Member Review Record

The gca_member_review_v1 record stores an append-only operator decision, reason, reviewer, current read-only balance, submitted evidence preview, linked holding verification, observed minimum balance, and before/after member status. The route is admin-token protected and never sends GCA.

Holding Verification Record

The gca_holding_verification_v1 record stores the safe Base snapshot block, 30-day window, current/start/minimum balances, event counts, provider, history completeness, and reconstruction consistency. It is written only during successful approval and is observed chain-history evidence, not a third-party audit or future guarantee.

Member Benefit Transfer Evidence

The gca_member_benefit_transfer_v1 record stores the public transaction hash, official reserve and approved recipient, exact 10,000 GCA amount, receipt block, Base safe-block snapshot, Transfer log index, verification status, and reviewer reason. It verifies an existing manual transfer and never signs or broadcasts one.

100 Credit Ledger

Minimum holding10,000 GCA

Credit typeGCA AI Quant Access credits

Credit amount100

Use window after activation180 days

Allowed statusesqueued / ledger_recorded / used / expired

GCA Member Ledger

Minimum holding1,000,000 GCA

Minimum holding period30 consecutive days

Activation ruleManual review + complete observed 30-day chain history

Member benefit10,000 GCA after approval

Evidence tx hashevidenceTxHash with 0x format check

Evidence statusmemberBenefitReviewEvidenceStatus

Holding evidencelatestHoldingVerificationId + observed minimum balance

Benefit transfermemberBenefitTransferTx after approval

Transfer evidencememberBenefitTransferRecordId + verified status

Tier nameGCA Member

Balance refresh cadence30 days

Allowed statusesqueued / active / review_rejected / needs_refresh / paused

ScopeService access only

Member Ledger References

Use the readable member pages first. The primary user workflow is the live account page, support review, and ledger status pages.

Live member account/gca/member-access

Program rules pagemembers.html

Member benefit pagemember-benefit.html

Benefit transfer pagemember-benefit-transfer.html

Access API pageaccess-api.html

Review queue pagereview-queue.html

Public Claim Boundaries

Safe to say: GCA has a live public data contract for wallet verification, credit ledger, and member ledger records.
Safe to say: the controlled HTTPS integration verifies GCA balance with an ERC-20 balanceOf read before writing eligible ledger records.
Safe to say: eligible 10,000 GCA holders can create one account-level 100 GCA AI Quant Access credits ledger record.
Safe to say: eligible 1,000,000 GCA / 30-day holders can create a GCA Member review ledger record.
Safe to say: GCA Member activation requires a token-protected operator review plus a complete observed 30-day transfer-history reconstruction whose minimum balance is at least 1,000,000 GCA.
Safe to say: successful approval stores append-only gca_holding_verification_v1 evidence without requesting a wallet signature or transaction.
Safe to say: after a manual transfer, the protected production API verifies a successful safe-block receipt from the official reserve to the approved member wallet for exactly 10,000 GCA.
Do not say the public form automatically proves 30 consecutive days of holding or activates GCA Member status.
Do not describe observed holding-history reconstruction as a third-party audit, permanent guarantee, or proof that public index data can never be delayed.
Do not describe credits or membership as cash, income, reimbursement, voting control, live trading permission, leverage, custody, withdrawals, or risk-control bypass.
Do not say the 10,000 GCA member benefit is automatic or self-service transferred before holding-period verification, support approval, and manual reserve-wallet processing.
Do not say the transfer-evidence route initiates, signs, authorizes, or broadcasts a token transfer.
Do not say membership guarantees lifetime access, listings, price support, liquidity, or third-party audit completion.