Skip to main content

Indexers & explorers

This page complements the Secure Lock reference by focusing on indexer design and data consistency.

Data sources​

On-chain​

  • Secure Lock (CheeseLock) contract reads
  • Contract events (lock creation, updates, vesting/unlock)

Off-chain (optional)​

  • Project metadata (branding, descriptions, links)
  • Audit token reports and status

Indexing strategy​

Event-driven indexing​

  • Subscribe to contract events.
  • Store normalized records keyed by lock id and chain.

State reconciliation​

  • Periodically reconcile stored state with on-chain reads to handle reorgs or missed events.

UI consistency requirements​

  • Always link to the source transaction and token/LP address.
  • Display lock schedule clearly (single unlock vs vesting).
  • Show “remaining” vs “unlocked” amounts.

Security notes​

  • Use official contract addresses only.
  • Validate token addresses and beware of impersonation patterns.

Indexing launchpad activity​

This page covers Secure Lock. To index pools, MicroSales, Melt Pools, and vaults, see events and data, which lists every event, struct, and view the launchpad exposes.