Errors/Chain errors
ContractTrapped
A chain-side invariant failed; nothing to fix client-side — report it if it persists
The contract aborted with a WASM trap, e.g. a panic, unreachable instruction, or memory violation, instead of returning normally. Dry-run the call with debug messages enabled and check the input data against the contract's expectations.
Declared by the Contracts pallet; it classifies to the semantic code internal.
Remediation
A chain-side invariant failed; nothing to fix client-side — report it if it persists
The same explanation is available in the terminal: btcli explain ContractTrapped.