Determinism

A combat replay is determined by the engine version, both fighter configurations, the seed, and the ability decision function. Saving just a seed is insufficient when stats or abilities have changed.

seeded randomness

The engine uses Mulberry32 generators for ability choice, initiative, accuracy, critical hits, and damage variation. Ability choice mixes in the round and fighter ID; round resolution uses a separate round seed.

combat versus record metadata

Combat does not read the clock or network. Match IDs and record timestamps are metadata outside that deterministic state. Comparing entire ledger records byte-for-byte can therefore differ even when the combat replay matches.

what verification proves

Replaying combat can establish that a result follows the supplied inputs. It does not establish that the inputs were agreed to, that a seed was chosen fairly, that a profile is owned by a wallet, or that money was sent. Those require separate authenticated records and chain evidence.

The treasury panel verifies finalized wallet balances and successful transfers. Each displayed transfer must have a successful transaction and matching source, destination, and positive SOL amount.