Skip to main content

Trust & safety

CheesePad is designed to make fundraising more transparent. This page explains the trust signals you should review before interacting with any pool.

Trust signals at a glance​

  • Secure Lock: on-chain proof that tokens or LP positions are locked under a defined schedule
  • Audit token: a visible badge that references an audit workflow/report
  • On-chain verification: contract addresses and transaction hashes you can verify independently
  • Official communication: support channels published on the official CheesePad website and docs

Secure Lock​

What Secure Lock proves​

  • The lock exists on-chain
  • The lock has an explicit schedule (single unlock or vesting)
  • Unlock activity is publicly observable

Audit token​

What to confirm​

  • The report references the correct deployed contract address
  • The report is current and the project did not change critical parameters after audit

On-chain verification​

Every token launched through a microsale or Melt Pool on CheesePad is one of two audited contracts: a plain ERC20 or a tax-collecting ERC20. Source for both, plus everything needed to verify a deployed token's bytecode against that source on BscScan, Etherscan, or Blockscout, is published at cheesepad-ai/cheesepad-tokens. You do not need to trust CheesePad's word for what a token does; verify it yourself against the published source.

Leaderboard signals​

Leaderboard ranking can be a useful signal, but it is not a guarantee of safety. Always validate on-chain proof first.

Common scams & red flags​

  • Impersonated social accounts sharing a different contract address
  • “Urgent” pressure to send funds outside the official flow
  • Locks that unlock suspiciously early compared to the announced vesting
  • Missing or inconsistent on-chain links

Reporting an issue​

When reporting suspicious behavior, include:

  • The pool link
  • The contract address(es) involved
  • Transaction hash(es)
  • Screenshots and a short timeline of what happened