How to Research a Base Token Contract

A contract report is a screening aid, not a full audit. Start from the exact Base token address, identify what the provider checked, and follow up on material flags where possible. Preserve uncertainty; one reassuring field does not prove safety.

Verify the exact contract

Names and symbols are not unique. Compare the full Base contract address in the report and explorer before reading findings. Confirm both refer to the same asset.

Check whether published source corresponds to the deployed contract. Verified source improves inspectability, but does not prove code is harmless or configuration and privileged roles cannot affect behavior.

  • Use the full address, not a ticker or search result label, to identify the token.
  • Record the scan time and source of each contract finding.
  • Treat source availability as a transparency signal, not an audit verdict.

Read flags as questions to investigate

QuickApe's contract component uses GoPlus reports of source availability and supported flags, including potential honeypots, hidden owners, recoverable ownership, balance changes, transfer pauses, and account-specific slippage. A flag is a provider finding to investigate, with meaning dependent on contract details and detection coverage.

Inspect relevant functions, roles, and configuration in source and available on-chain state. Complex code may require technical review. Absence of a flag does not prove risky behavior is absent.

Keep score and direct observations distinct

The QAPE Signal assigns 30 points to contract inputs, 30 to liquidity, 25 to holder concentration, and 15 to market activity. GoPlus supplies contract and holder inputs; DexScreener supplies liquidity and activity. Missing inputs are excluded rather than treated as safe or zero, and coverage is displayed. The result is a deterministic summary of available provider-reported inputs, not a direct on-chain safety audit.

QuickApe also presents supported, read-only Base checks separately. A direct observation can clarify a supported property, but it does not automatically validate every provider conclusion or cover all contract behavior. LP ownership and locks are not part of the liquidity score, and a pool observation is not proof of locked funds.

Reach a bounded conclusion

Record the address, provider flags, independent checks, and what remains unresolved. Do not assume an unexplained finding is malicious or harmless. Contract state and controls can change, so date the evidence.

Takeaway: verify identity, investigate specific behaviors rather than relying on a summary label, and treat missing information as missing. A clean-looking report, verified source, or high QAPE Signal is not a guarantee, a substitute for a full audit, or a recommendation to trade.

Research tools: Browse Base tokens · How the QAPE Signal works