botwir3 Mechanic
Spec Hash
A SHA-256 fingerprint of the strategy configuration — if any parameter changes, the hash breaks and the bot halts.
The spec hash is a tamper seal. When the strategy is compiled in the builder, every field — module selections, band configuration, growth target, tolerance, Kelly multiplier — is serialized and hashed using SHA-256. The resulting hash is stored in the compiled config file.
Every execution cycle, the runtime recomputes the hash from the current config and compares it to the stored value. If they match, the config has not been modified and execution proceeds. If they differ, the bot enters HALT with a MANDATE_INTEGRITY_VIOLATION code.
The hash does not prevent modification. Anyone with access to the config file can edit it. The hash detects modification after the fact and stops execution rather than continue under a changed mandate. This is integrity detection, not access control.