What Is GloveCat and GCAT?

An evidence-first introduction to GloveCat, the GCAT token, and the project's active Base deployment.

Published · Updated · 8 min read

Maintained by the GloveCat project team.

What changed on September 2, 2026

Added a reproducible evidence map and clarified which deployment claims can and cannot be verified from public sources.

Read the editorial and evidence standards

1. Separate the project from the token

GloveCat is an independent community project built around GCAT and a set of public smart contracts on Base mainnet. GCAT is the ERC-20 token used across the current project surfaces. The website and documentation explain those contracts; they do not make GCAT a deposit, equity interest, or guaranteed investment.

The safest way to understand the project is to start with verifiable facts: the chain ID, contract addresses, fixed supply, allocation, public lock transactions, official trading pair, and the live readiness checks used before staking actions.

2. Know the active contract surface

The active deployment contains the GCAT token, a lock-position staking contract, a tiered NFT contract, and a gamification contract. Each address should be checked independently on Basescan. A familiar logo or token symbol is not proof that an address is official.

  • GloveCatCore: fixed-supply ERC-20 with a 0% buy fee and fixed 1% ecosystem sell fee.
  • Staking: 30-, 90-, and 180-day lock positions funded from a finite incentive pool.
  • GloveCatNFT: tier NFTs with activation and staking-boost rules.
  • GamificationCore: season-based NFT reward claims; it does not distribute the staking ERC-20 pool.

3. Use public evidence, not promises

The deployment publishes contract verification, Safe-controlled administration, token vesting records, launch liquidity, the project-owned LP lock, and the transaction that opened trading. Mutable conditions such as staking pool health must still be checked live because a dated transaction cannot prove a current balance.

Official pages can help you locate evidence, but the final check should occur on the chain explorer and the current public-status endpoint before you sign a transaction.

4. Read the evidence in the right order

A useful review starts with identity, then history, then current state. Identity evidence answers which chain and contracts belong to this deployment. Historical evidence answers which transactions created, funded, configured, or locked those contracts. Current-state evidence answers what the contracts report now. Mixing these layers produces misleading conclusions: a valid funding transaction does not prove that funds remain available, and a current balance does not explain how it arrived there.

For GCAT, first compare chain ID 8453 and the complete token address across this site, the documentation, and Basescan. Next open the verified source and the named staking, NFT, pair, Safe, and lock addresses. Then review dated transactions such as trading activation, staking-pool funding, and token or LP locks. Finish with fresh contract reads or the public-status response for conditions that can change. This sequence is repeatable and leaves a record another reader can check.

  • Identity: network, exact addresses, verified source, and contract relationships.
  • History: transaction hashes, block timestamps, senders, destinations, and emitted events.
  • Current state: balances, readiness flags, Safe policy, allowances, reserves, and quotes.
  • Interpretation: what the evidence supports, what it does not support, and when it was checked.

5. Know what this site can verify

The site can publish exact identifiers, show how contract relationships are checked, and point to public records. It can also fail closed when a current readiness response is stale or inconsistent. It cannot independently guarantee a future market price, continuous liquidity, third-party availability, wallet security, or the result of a transaction that has not yet been signed and mined.

Treat each guide as a documented inspection path, not a substitute for your own final check. When a claim depends on mutable state, use the linked live source and note its observation time. When a claim depends on a dated event, preserve the transaction hash and block time. This distinction is the core editorial rule used across the Learn library.

6. Understand the risk boundaries

Smart-contract verification does not eliminate token price volatility, liquidity risk, wallet compromise, phishing, transaction mistakes, bridge risk, or third-party DEX risk. A public lock can show custody constraints for a specific asset, but it cannot guarantee market value or future liquidity.

If an address, link, or claim conflicts with the official website and documentation, do not interact. Contact [email protected] through a channel you reached independently.

Sources and evidence

Dated transactions prove historical events; balances, ownership, readiness, and quotes must be checked again when used.

Official support

Questions about published evidence can be sent to [email protected].

Risk disclaimer

GCAT is an experimental meme token with no intrinsic value or expectation of financial return. Public contracts and locks do not guarantee price, liquidity, rewards, or safety. Verify current evidence and make your own risk decision.