How GCAT Staking Works

A practical guide to GCAT lock periods, incentive accrual, readiness checks, NFT boost snapshots, and withdrawal rules.

Published · Updated · 10 min read

Maintained by the GloveCat project team.

What changed on October 3, 2026

Clarified base APR, the 365-day reward calculation, and the absence of automatic compounding using the verified staking source.

Read the editorial and evidence standards

1. Staking creates a lock position

GCAT staking uses separate lock positions rather than a freely withdrawable balance. A user chooses an amount and a fixed duration, grants the staking contract an exact token allowance, and then creates the position. Principal remains locked until that position matures.

The current interface enforces a 1,000 GCAT minimum and supports up to 50 active positions per wallet. Always review the amount, spender, network, and lock period in the wallet confirmation before signing.

The displayed rates are base APR (annual percentage rate), with no automatic compounding. Before any NFT boost, rewards equal staked GCAT multiplied by the APR as a decimal and elapsed seconds, divided by the number of seconds in 365 days. For example, 1,000 GCAT at 2% base APR accrues about 1.64 GCAT over 30 days, subject to reward-pool availability. The 2% is an annual rate, not a 30-day return. Claimed rewards are paid separately and are not automatically added to the staked principal.

  • Minimum position1,000 GCAT
  • 30-day base APR2%
  • 90-day base APR5%
  • 180-day base APR8%

2. Rewards come from a finite pool

The staking contract does not mint new GCAT for rewards. Incentives are paid from GCAT already deposited into the staking incentive pool. The initial bootstrap was funded with 5,000,000 GCAT in two Safe-executed deposits on July 1, 2026.

A historical deposit is not proof that the current pool is healthy. The interface checks the live incentive-pool value and verifies that the staking contract balance can cover locked principal plus the recorded pool. If the evidence is missing, expired, inconsistent, or insufficient, staking remains blocked.

3. Claims and principal withdrawal are different

Accrued incentives can be claimed while a position remains locked, subject to pool accounting and current contract availability. Claiming incentives does not unlock principal or shorten the selected duration.

Principal can be withdrawn only after the position matures. If incentives cannot be fully paid, the contract can carry the unpaid amount as pending incentives rather than creating new tokens. Users should check the resulting on-chain state after every claim or withdrawal.

4. NFT boosts are snapshotted

Eligible activated GloveCat NFTs can increase the multiplier recorded when a new staking lock is created. The snapshot belongs to that lock. Transferring an NFT later does not rewrite the existing lock, but the sender cannot use the transferred NFT for future locks and the recipient must complete the activation delay.

5. Follow the complete position lifecycle

A staking decision is more than a single deposit. Before approval, the wallet should show Base mainnet, the official GCAT token, and the official staking contract as spender. The allowance transaction changes only spending permission; the later staking transaction creates the lock position. Record both transaction hashes because a successful approval does not prove that a position was created.

After the staking transaction is mined, verify the principal, selected duration, creation time, maturity time, and snapshotted multiplier in the position data. During the lock, claims affect incentive accounting but do not shorten maturity. At maturity, principal withdrawal is a separate transaction. Finally, compare the wallet balance and the position's resulting state rather than relying only on a success toast in the interface.

  • Approve only the intended GCAT amount to the official staking address.
  • Confirm the staking receipt created the expected position and did not merely spend gas.
  • Keep claim receipts separate from the final principal-withdrawal receipt.
  • Revoke an unused allowance if the staking action is abandoned.

6. Interpret the live readiness response

The public-status response is designed to be short-lived evidence. Check observedAt, validUntil, blockNumber, chainId, deploymentStatus, and readiness before using any summary flag. The contract relationship checks should agree that the core, staking, NFT, gamification, and Safe addresses match the published deployment. Pool health should compare the staking token balance with locked principal and the recorded incentive pool rather than checking a single balance in isolation.

A response that is expired, for the wrong chain, missing a block reference, or internally inconsistent should be treated as unavailable even if one field says ready. The website applies that fail-closed interpretation before enabling its official staking action. A reader reviewing the endpoint manually should use the same rule and refresh only from the official HTTPS endpoint.

7. Check before staking

A displayed annualized rate is a contract parameter, not a promise of token value or uninterrupted payout availability.

  • Confirm Base mainnet and the official GCAT and staking contract addresses.
  • Confirm the interface reports current, validated readiness rather than a dated snapshot.
  • Approve only the intended amount to the official staking contract.
  • Record the lock duration and expected maturity date before signing.
  • Keep enough ETH on Base for approval, staking, claims, and withdrawal gas.

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.