Verify a FLIP result

1. 01

   Finalized chain state

   Balances, storage, receipts, logs, code, block hash, and transaction sender are the execution truth.

2. 02

   Accepted immutable manifest

   Defines the release’s chain, addresses, bytecode hashes, roles, rules, Catalogs, PoolKeys, Provider, signers, and risk parameters.

3. 03

   Compiled ABI and Source A

   Defines selectors, events, errors, immutable logic, and reproducible bytecode for the release.

4. 04

   Accepted Evidence B

   Binds the full acceptance run, offchain source artifacts, and service health to the manifest and finalized blocks.

5. 05

   API projection

   Provides fast reads only when its finalized cursor, manifest identity, journal, proof, and RPC replay agree.

6. 06

   Documentation and interface

   Explain the verified rules; they do not override an accepted release or chain state.

• Receipt-derived Bet/Ticket ID and, where applicable, VRF Request ID.
• Player, mode, amount, principal, fee, payout multiplier, reward, rulesVersion, Catalog version/hash, and deadlines frozen in events/storage.
• For Coin: Provider ID, Coordinator path, Request block, verified random word, domain derivation, and outcome.
• For Parity: symbol, target, source/rule hash, stable or FLASH timing, full price cents, raw response hash, report digest, and signer threshold.
• Reserve/JIT/Bond reservation before external request and exact release/slash after terminal state.
• Liability key, JIT quote/venue/min-out/recipient, stock balance delta, or cash fallback claim.

chainId
release
manifestHash
finalizedBlock
finalizedHash
finalizedTimestamp

A V3 user response is usable only when these fields belong to the same release and finalized block. A 503 is an evidence failure, not a zero balance, no reward, or negative eligibility result.