GCA Reserve Address Statement

This public statement explains the disclosed GCA owner-held reserve wallet, the on-chain transfer proofs, and the exact custody boundary for reviewers. It does not claim LP locking or reserve locking.

Holder Distribution Custody Roadmap Technical Report Supply Disclosure On-chain Proofs BaseScan Contract Technical Evidence

Reserve Wallet 0x5e8F84748612B913aAcC937492AC25dc5630E246

Reserve Amount 600,000,000 GCA

Reserve Percent 60%

Custody Status Owner-controlled, not locked

Allocation Disclosure

GCA has a disclosed 40/60 target allocation. The owner-held reserve is separated from the deployer wallet for public tracking, but it remains a normal owner-controlled wallet.

Total supply1,000,000,000 GCA

Target public / ecosystem / liquidity allocation400,000,000 GCA / 40%

Owner-held reserve600,000,000 GCA / 60%

Reserve wallet0x5e8F84748612B913aAcC937492AC25dc5630E246

Custody Boundary

The reserve is public and traceable, but not locked, not vested, and not controlled by a published multisig. This disclosure reduces ambiguity; it does not remove concentration risk by itself. The Custody Roadmap records what evidence would be required before a future lock, vesting, multisig, or LP-lock claim.

Reserve lockedNo

Vesting contractNo

MultisigNo

LP lock claimedNo

On-chain Reserve Transfer Proofs

First 300,000,000 GCA transfer0x4c342e1f4c969d0a73018637b778d5a76bd05f54749ff1fd2d19327fd5c01c67

First transfer block45,739,653

Second 300,000,000 GCA transfer0xfffb674448abdbd3af45bb0a30c48e5fbb0e675542b971f031381254b5dc5317

Second transfer block45,779,081

Reserve References

Use these readable reserve, holder distribution, custody roadmap, supply disclosure, and on-chain proof pages for public reserve review.

Holder Distribution Custody Roadmap Supply Disclosure On-chain Proofs

Reviewer Notes

This page is intended to answer holder-concentration and reserve-disclosure questions.
The reserve is disclosed as a normal owner-controlled wallet, not hidden circulation.
No LP lock is currently claimed. If a future LP lock is executed, it should be documented with exact platform, lock address, transaction hash, unlock date, and custody details.
Do not describe the reserve as locked, vested, multisig-controlled, burned, or externally audited unless that later becomes verifiable on-chain or through an independent report.