How GloveCat NFTs and Boosts Work
A guide to GloveCat NFT tiers, activation delays, transfer resets, stacking, boost snapshots, and the final staking multiplier cap.
Published · Updated · 9 min read
Maintained by the GloveCat project team.
What changed on September 2, 2026
Added an end-to-end NFT state example and a pre-lock audit for activation, stacking, transfer resets, and snapshots.
1. Four default NFT tiers
GloveCatNFT defines four default tiers with different staking multipliers. These values apply only when the NFT benefit is eligible and active at the time a new lock snapshot is created.
- Common1.2x
- Rare1.5x
- Epic1.8x
- Legendary2.5x
2. Activation follows a holding delay
Receiving an NFT does not make its staking benefit active immediately. A token movement starts the current one-day holding period. After that period, the holder must activate the benefit on-chain before it can be considered for a future staking lock.
Always inspect the active-benefit state and the wallet transaction before relying on a displayed tier.
3. Different tiers stack; duplicates do not
One active NFT from each different tier can stack additively up to the final 4.0x staking multiplier cap. Multiple active NFTs from the same tier do not add repeated boost. For example, two Common NFTs still contribute the Common-tier amount once.
4. Locks use a creation-time snapshot
When a new staking lock is created, the eligible NFT boost is snapshotted into that position. Moving the NFT later does not retroactively change the existing lock. The sender loses its use for future locks, and the recipient must wait and activate before using it for a new lock.
Transfer resets the prior active benefit for that NFT. This prevents an already-transferred token from continuing to grant future-lock benefits to the former holder.
5. Follow one NFT through its state changes
Suppose a wallet receives a Rare GloveCat NFT. The transfer begins the holding delay; the tier is visible, but the staking benefit is not yet active. After the one-day period, the holder sends the activation transaction and verifies the resulting active-benefit state. If the holder then creates a new staking position, the eligible multiplier is captured in that position's creation-time data.
If the Rare NFT is transferred later, the already-created staking position keeps its stored snapshot. The former holder cannot use that NFT for a new position, and the recipient starts a new holding-delay and activation process. If either wallet also holds another Rare NFT, the duplicate tier does not add a second Rare contribution. A different active tier can contribute, subject to the final 4.0x cap.
This sequence explains why collection ownership, active-benefit state, and a staking position's stored multiplier are different facts. A marketplace ownership view proves only the current NFT holder. It does not prove activation or rewrite the terms of an earlier staking lock.
6. Audit the boost before creating a lock
Before staking, list the wallet's official collection token IDs, tier for each token, latest transfer time, activation status, and which distinct tiers should count. Compare the interface's proposed multiplier with the contract's active-benefit reads, then verify the multiplier stored in the mined staking position. Save the staking receipt and position identifier.
Do not buy or transfer an NFT solely because an interface previews a boost. The holding delay, activation transaction, duplicate-tier rule, final cap, staking readiness, and finite reward pool all affect whether the intended benefit is usable. NFT price and royalty behavior are separate from the staking calculation.
7. Minting and royalties are separate controls
NFT minting is restricted to the configured Safe or approved minters. GamificationCore must be approved before season reward claims can mint. The default royalty percentage is 3%, but marketplace royalty handling and staking benefits are separate mechanisms.
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.