When should a Silverscript covenant use Transition mode instead of Verification mode?

Use Transition mode when the new state cannot be inferred from the existing transaction state alone — for example, when a script must decrement an issuance allowance by a mint amount that the caller supplies at call time. In Verification mode, Silverscript reads state automatically via introspection opcodes, but it cannot perform computations that depend on arguments passed in at runtime. Transition mode fills this gap by giving the covenant script explicit control over computing new states and letting it accept extra call arguments. Understanding the distinction helps Kaspa developers pick the simplest mode that still meets their contract's requirements.