GloveCatCore
GCAT ERC20 token with fixed sell fee and expired launch max-wallet window
This page shows the current deployment registry state.
GCAT ERC20 token with fixed sell fee and expired launch max-wallet window
0x59df0577...e34d9ff4Lock-only staking with 30-, 90-, and 180-day periods and base APRs of 2%, 5%, and 8%, respectively
0x2ab642c7...802162abERC721 tier NFT for staking boost and ERC2981 royalties
0x23d398f0...53919f82Staking-only leaderboard NFT claims
0x96935bde...9401f3f7Production multiSig authority
0xFa5eE6e6...8eeF0803EOA used for the fresh broadcast
0xf04a5fe7...d9c05629Recipient for the 75% launch liquidity allocation
0xa92C88dE...c3F27fdaRecipient for the 20% treasury and staking reserve allocation
0xFa5eE6e6...8eeF0803Recipient for the 5% team allocation
0x5217a803...8Fa5bCfCRecipient for the fixed 1% sell ecosystem fee
0x228EDD1B...c55B054aBasescan ERC20 token page
0x59df0577...e34d9ff4Verified Basescan source code
0x59df0577...e34d9ff4Verified Basescan source code
0x2ab642c7...802162abVerified Basescan source code
0x23d398f0...53919f82Verified Basescan source code
0x96935bde...9401f3f7Safe app view for the configured network
0xFa5eE6e6...8eeF0803Safe public API record for owners and threshold
0xFa5eE6e6...8eeF0803PinkSale / PinkLock V2 target contract on Basescan
0xdD6E31A0...aff8BBdCBasescan transaction that set the PinkSale / PinkLock V2 target
0x6b7cd6ae...9445261dOfficial registered Aerodrome Classic Volatile WETH/GCAT pair and LP token
0x6330Bb18...8AE8dD54Aerodrome addLiquidity execution transaction
0xa4268463...2e0fb7a0PinkSale / PinkLock V2 contract holding the project-owned Aerodrome LP tokens
0xdD6E31A0...aff8BBdCPinkSale / PinkLock V2 transaction that locked the project-owned Aerodrome LP tokens
0xd0afe05c...03e2554bSafe-executed openTrading transaction on GloveCatCore
0x18fb7f5f...8993485eMutable staking readiness, trading-open, and reward-pool status from live Base reads
schema 1.0.0Safe nonce 9, executed 2026-07-01 20:35:53 UTC
0x5996a597...39920076Safe nonce 10, executed 2026-07-01 21:09:43 UTC
0x3d54e7a9...181840d3Basescan lock execution transaction
0x9c0feb49...703b634cBasescan lock execution transaction
0xe2a17dc1...43942d48The current GloveCat deployment status on Base mainnet is active.
The contracts listed above are deployed and Basescan verified. Phase 1 Safe wiring has been executed. The PinkSale / PinkLock V2 target is set, and the team and long-term treasury reserve lock flags are complete on-chain.
Registered-pool setup, liquidity seeding, project-owned LP locking, Safe openTrading() execution, and two staking reward-pool funding transactions have executed. These are durable evidence records; the current trading read, readiness decision, and pool balance remain mutable and are published on Operational Status.
Production status API
Waiting for a validated production status observation. Do not infer current trading, staking, or reward-pool availability from the dated static snapshot.
| Launch gate | Current status |
|---|---|
| Registered trading pair | Aerodrome Classic Volatile WETH/GCAT at 0x6330Bb184d90D78F336270485C3d17AB8AE8dD54 |
| Registered pool | The designated pair is registered in GloveCatCore |
| Liquidity seed | 5.51 WETH and 375,000,000 GCAT were seeded into the registered pool |
| Trading execution | Safe openTrading() executed on 2026-06-29 13:30:07 UTC in tx 0x18fb7f5fef1c3270dbffa50d9bd56d46c816912c00a599b82fe6fb8b8993485e |
| LP lock evidence | Project-owned Aerodrome LP tokens are locked through PinkSale / PinkLock V2 until 2031-06-24 00:00 UTC |
| Staking funding | 1,000,000 GCAT and 4,000,000 GCAT deposits executed on 2026-07-01; transaction links are listed above |
| Dated on-chain snapshot | tradingOpened=true and 5,000,000 GCAT at Base block 48451141 on 2026-07-10 13:53:49 UTC; not a current-readiness or live-value substitute |
The current published Safe configuration is 2-of-3 multisig. This configuration may be strengthened later by adding signers, increasing the threshold, or both. Users should verify the current Safe app and Safe owner/threshold API record before relying on any privileged-control claim.
The team allocation lock, long-term treasury reserve lock, and project-owned LP lock are complete through PinkSale / PinkLock V2. These records are lock evidence only; staking readiness is tracked separately through the production status API and its live Staking.incentivePool() gate. PinkSale / PinkLock V2 is the PinkSale locking product used for these records; the linked Basescan transactions and target contract remain the canonical public evidence.
Actual schedule: 62 elapsed 30-day cycles to the 100% cap. Starts 2026-06-28 02:00 UTC with 0.56% TGE and 1.63% release per cycle.
Actual schedule: 62 elapsed 30-day cycles to the 100% cap. Starts 2026-06-28 02:00 UTC with 0.56% TGE and 1.63% release per cycle.
0xdD6E31A046b828CbBAfb939C2a394629aff8BBdC0x9c0feb497e0d96da551aa3f7d556ee5501ede05718a47bb4c6e38484703b634c0xdD6E31A046b828CbBAfb939C2a394629aff8BBdC0xe2a17dc1cb1300a9c26c6ec77cf036c1f38c3ff6ccb3163a5e77ffed43942d48External PinkSale / PinkLock V2 records are the final schedule evidence. The Basescan links identify the target contract and execution transactions. Both visible PinkSale / PinkLock V2 records use tgeBps=56, cycle=2592000, and cycleBps=163, which correspond to 0.56% TGE and 1.63% every 30 days. The actual schedule reaches the 100% cap after 62 elapsed 30-day cycles. LP lock wording must stay tied to the public lock transaction and lock page evidence.
The Aerodrome LP position is locked through PinkSale / PinkLock V2 as a normal ERC20 token lock because the PinkSale / PinkLock V2 LP-token mode expects a Uniswap V2-style factory path. See Liquidity and LP Lock Evidence.
| Item | Value |
|---|---|
| Network | Base Mainnet |
| Chain ID | 8453 |
| RPC | https://mainnet.base.org |
| Explorer | Basescan |
The active contract surface is:
GloveCatCoreStakingGloveCatNFTGamificationCoreOnly the contracts listed above should be treated as the current GloveCat deployment surface.
ABIs come from the contract repository build outputs after compile. Basescan verification should be checked against the active manifest, not older archived deployment snapshots.