Documentation

Type equality error

Stacks equality error

Error that happens when type cannot be used in the corresponding scope. Argument of this constructor carries type which violates the restriction, e.g. big_map in UNPACK, and a concrete reason why the type is unsuported.

Arithmetic operation is applied to types, at least one of which is not numeric (e.g. timestamp and timestamp passed to MUL instruction).

Error that happens when actual types are different from the type that instruction expects. The param is an non-empty list of all expected stack types that the instruction would accept. Each expected stack types is represented as non-empty list as well.

Error that happens when the caller expected one top-level type, but the contract has another type specified.

Some instruction is invalid or used in an invalid way. For example, PAIR 0 or PAIR 1, or a SELF instruction was used in a LAMBDA.

The Text argument is a user-readable explanation of why this instruction is invalid.

Since this makes sense only for primitive instructions, we keep U.InstrAbstract with () type argument.

Error that happens when a Value is never a valid source for this type (e.g. timestamp cannot be obtained from a ValueTrue)

There are not enough items on stack to perform a certain instruction.

Invalid entrypoint name provided

Contract with given address is not originated.

Given entrypoint is not present.

Incorrect parameter declaration (with respect to entrypoints feature).

Natural numbers cannot be negative

Exceeds the maximal mutez value

Address couldn't be parsed from its textual representation

KeyHash couldn't be parsed from its textual representation

BLS12-381 primitive couldn't be parsed

Timestamp is not RFC339 compliant

Code always fails, but shouldn't, like in ITER body. This is actually more general, any instruction that allows no continuation (like NEVER) cannot appear as part of another instruction's body.

Empty block of code, like ITER body.

Generic error when instruction does not match something sensible.

A big_map with the given ID was not found.

We found a big_map with the given big_map ID, but its key and/or value types are not the same as the requested types.