How to Buy GCAT on Aerodrome
A safety-first walkthrough for verifying the official GCAT route, reviewing a quote, and signing an Aerodrome swap on Base.
Published · Updated · 9 min read
Maintained by the GloveCat project team.
What changed on September 2, 2026
Added no-transaction practice steps and explicit stop conditions for route, quote, approval, and wallet review.
1. Prepare Base ETH and a compatible wallet
A swap on Base requires a compatible self-custody wallet and enough ETH on Base for the swap and future transactions. Verify that assets are on Base mainnet rather than another network with a similar token name.
Bridging introduces a separate protocol and risk surface. Complete and verify any bridge operation independently before opening a swap.
2. Verify GCAT and the official pair
Compare the GCAT contract address and the registered WETH/GCAT pair with the official site, documentation, and Basescan. Do not select a token only by symbol or logo.
3. Review the complete quote
The GCAT token buy fee is 0%, but DEX fees, price impact, slippage, and network gas remain. A quote can change before execution.
- Input token and amount
- Output token contract and estimated amount
- Minimum received after slippage
- Pool and router used by the route
- Price impact, DEX fee, and estimated Base gas
4. Practice the verification path without transacting
You can inspect most of the route before connecting a wallet. Open Aerodrome from an independently verified domain, select Base, paste the official GCAT address, choose a small hypothetical input, and inspect the route, pair, price impact, fee information, and minimum received calculation. Do not connect or sign merely to prove the page works.
Next, open the GCAT token and official pair on Basescan in separate tabs. Compare both token addresses and the pair address with the route. If the interface uses another pool or multi-hop route, identify every hop and decide whether it matches your intent. This rehearsal makes it easier to recognize an unexpected change when a real wallet request appears.
5. Use clear stop conditions
Stop before signing if the wallet is not on Base, the GCAT address differs by even one character, the route uses an unexplained token or pool, the spender is not the reviewed router, the approval is broader than intended, the minimum received value is unacceptable, the price impact is not understood, or the transaction simulation shows an unexpected transfer. Close the page and restart from a bookmarked official source rather than editing the suspicious request in place.
Also stop if urgency is the main reason to continue. A countdown, direct message, support impersonator, or claim that verification will make an opportunity disappear is not technical evidence. Market conditions can change, but skipping contract and wallet checks converts an avoidable verification problem into an irreversible transaction risk.
6. Approve and sign deliberately
If an ERC-20 input token requires approval, verify the spender and allowance before approving. ETH as the native input normally does not need an ERC-20 approval. Then compare the swap transaction with the reviewed quote and reject any unexpected destination or asset.
7. Verify the result on-chain
After confirmation, open the transaction hash on Basescan and verify the transferred assets, route, and received amount against the pre-signing quote. Add GCAT to the wallet by its official contract address if it is not displayed automatically, and keep the receipt as the final record of what executed.
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.