Skip to main content

Authentication

This page defines authentication expectations for developers integrating with CheesePad.

Wallet-based identity (common)​

Many product flows use wallet connections as the primary user identity layer.

API access (when applicable)​

If CheesePad exposes APIs for partners or internal tooling, access may require:

  • API keys
  • Signed messages (wallet signatures)
  • IP allowlists or rate limits

Best practices​

  • Never request or store user seed phrases.
  • Use signed messages for identity verification rather than raw private keys.
  • Store secrets securely and rotate keys regularly.

Support​

If you need access to partner APIs, contact CheesePad through official support channels.