An opaque type representing Plutus Core ByteStrings.

Concatenates two ByteStrings.

Adds a byte to the front of a ByteString.

Returns the substring of a ByteString from index start of length n.

Returns the length of a ByteString.

Returns the byte of a ByteString at index.

An empty ByteString.

Check if two ByteStrings are equal.

Check if one ByteString is less than another.

Check if one ByteString is less than or equal to another.

Check if one ByteString is greater than another.

Check if one ByteString is greater than another.

The SHA2-256 hash of a ByteString

The SHA3-256 hash of a ByteString

The BLAKE2B-224 hash of a ByteString

The BLAKE2B-256 hash of a ByteString

The KECCAK-256 hash of a ByteString

The RIPEMD-160 hash of a ByteString

Ed25519 signature verification. Verify that the signature is a signature of the message by the public key. This will fail if key or the signature are not of the expected length.

Given an ECDSA SECP256k1 verification key, an ECDSA SECP256k1 signature, and an ECDSA SECP256k1 message hash (all as BuiltinByteStrings), verify the hash with that key and signature.

Note

There are additional well-formation requirements for the arguments beyond their length:

• The first byte of the public key must correspond to the sign of the y coordinate: this is 0x02 if y is even, and 0x03 otherwise.
• The remaining bytes of the public key must correspond to the x coordinate, as a big-endian integer.
• The first 32 bytes of the signature must correspond to the big-endian integer representation of _r_.
• The last 32 bytes of the signature must correspond to the big-endian integer representation of _s_.

While this primitive accepts a hash, any caller should only pass it hashes that they computed themselves: specifically, they should receive the message from a sender and hash it, rather than receiving the hash from said sender. Failure to do so can be dangerous. Other than length, we make no requirements of what hash gets used.

See also

• secp256k1_ec_pubkey_serialize; this implements the format for the verification key that we accept, given a length argument of 33 and the SECP256K1_EC_COMPRESSED flag.
• secp256k1_ecdsa_serialize_compact; this implements the format for the signature that we accept.

Given a Schnorr SECP256k1 verification key, a Schnorr SECP256k1 signature, and a message (all as BuiltinByteStrings), verify the message with that key and signature.

Note

There are additional well-formation requirements for the arguments beyond their length. Throughout, we refer to co-ordinates of the point R.

• The bytes of the public key must correspond to the x coordinate, as a big-endian integer, as specified in BIP-340.
• The first 32 bytes of the signature must correspond to the x coordinate, as a big-endian integer, as specified in BIP-340.
• The last 32 bytes of the signature must correspond to the bytes of s, as a big-endian integer, as specified in BIP-340.

See also

• BIP-340
• secp256k1_xonly_pubkey_serialize; this implements the format for the verification key that we accept.
• secp256k1_schnorrsig_sign; this implements the signing logic for signatures this builtin can verify.

Converts a ByteString to a String.

Arbitrary precision integers. In contrast with fixed-size integral types such as Int, the Integer type represents the entire infinite range of integers.

Integers are stored in a kind of sign-magnitude form, hence do not expect two's complement form when using bit operations.

If the value is small (fit into an Int), IS constructor is used. Otherwise Integer and IN constructors are used to store a BigNat representing respectively the positive or the negative value magnitude.

Invariant: Integer and IN are used iff value doesn't fit in IS

Add two Integers.

Subtract two Integers.

Multiply two Integers.

Divide two integers.

Integer modulo operation.

Quotient of two integers.

Take the remainder of dividing two Integers.

Check whether one Integer is greater than another.

Check whether one Integer is greater than or equal to another.

Check whether one Integer is less than another.

Check whether one Integer is less than or equal to another.

Check if two Integers are equal.

FIXME

See also

• Operation description

Aborts evaluation with an error.

A type corresponding to the Plutus Core builtin equivalent of Data.

The point of this type is to be an opaque equivalent of Data, so as to ensure that it is only used in ways that the compiler can handle.

As such, you should use this type in your on-chain code, and in any data structures that you want to be representable on-chain.

For off-chain usage, there are conversion functions builtinDataToData and dataToBuiltinData, but note that these will not work on-chain.

Given five values for the five different constructors of BuiltinData, selects one depending on which corresponds to the actual constructor of the given value.

Given a BuiltinData value and matching functions for the five constructors, applies the appropriate matcher to the arguments of the constructor and returns the result.

Given a BuiltinData value and matching functions for the five constructors, applies the appropriate matcher to the arguments of the constructor and returns the result.

Check if two BuiltinDatas are equal.

Convert a String into a ByteString.

Constructs a BuiltinData value with the Constr constructor.

Constructs a BuiltinData value with the Map constructor.

Constructs a BuiltinData value with the List constructor.

Constructs a BuiltinData value with the I constructor.

Constructs a BuiltinData value with the B constructor.

Deconstructs a BuiltinData as a Constr, or fails if it is not one.

Deconstructs a BuiltinData as a Map, or fails if it is not one.

Deconstructs a BuiltinData as a List, or fails if it is not one.

Deconstructs a BuiltinData as an I, or fails if it is not one.

Deconstructs a BuiltinData as a B, or fails if it is not one.

Convert a BuiltinData into a Data. Only works off-chain.

Convert a Data into a BuiltinData. Only works off-chain.

Append two Strings.

An empty String.

Check if two strings are equal

Convert a String into a ByteString.

Turn a builtin pair into a normal pair, useful in patterns.

The empty list of elements of the given type that gets spotted by the plugin (grep for mkNilOpaque in the plugin code) and replaced by the actual empty list constant for types that are supported (a subset of built-in types).

Like matchList but evaluates nilCase strictly.

Uncons a builtin list, failing if the list is empty, useful in patterns.

Uncons a builtin list, failing if the list is empty, useful in patterns.

Emit the given string as a trace message before evaluating the argument.

Byte ordering.

Convert a BuiltinInteger into a BuiltinByteString, as described in CIP-121. The first argument indicates the endianness of the conversion and the third argument is the integer to be converted, which must be non-negative. The second argument must also be non-negative and it indicates the required width of the output. If the width is zero then the output is the smallest bytestring which can contain the converted input (and in this case, the integer 0 encodes to the empty bytestring). If the width is nonzero then the output bytestring will be padded to the required width with 0x00 bytes (on the left for big-endian conversions and on the right for little-endian conversions); if the input integer is too big to fit into a bytestring of the specified width then the conversion will fail. Conversion will also fail if the specified width is greater than 8192 or the input integer is too big to fit into a bytestring of length 8192.

Convert a BuiltinByteString to a BuiltinInteger, as described in CIP-121. The first argument indicates the endianness of the conversion and the second is the bytestring to be converted. There is no limitation on the size of the bytestring. The empty bytestring is converted to the integer 0.

Perform logical AND on two BuiltinByteString arguments, as described in CIP-122.

The first argument indicates whether padding semantics should be used or not; if False, truncation semantics will be used instead.

See also

• Padding and truncation semantics
• Bit indexing scheme

Perform logical OR on two BuiltinByteString arguments, as described here.

The first argument indicates whether padding semantics should be used or not; if False, truncation semantics will be used instead.

See also

• Padding and truncation semantics
• Bit indexing scheme

Perform logical XOR on two BuiltinByteString arguments, as described here.

The first argument indicates whether padding semantics should be used or not; if False, truncation semantics will be used instead.

See also

• Padding and truncation semantics
• Bit indexing scheme

Perform logical complement on a BuiltinByteString, as described here.

See also

• Bit indexing scheme

Read a bit at the _bit_ index given by the Integer argument in the BuiltinByteString argument. The result will be True if the corresponding bit is set, and False if it is clear. Will error if given an out-of-bounds index argument; that is, if the index is either negative, or equal to or greater than the total number of bits in the BuiltinByteString argument.

See also

• Bit indexing scheme
• Operation description

Given a BuiltinByteString, a list of indexes to change, and a list of values to change those indexes to, set the bit at each of the specified index as follows:

• If the corresponding entry in the list of values is True, set that bit;
• Otherwise, clear that bit.

Will error if any of the indexes are out-of-bounds: that is, if the index is either negative, or equal to or greater than the total number of bits in the BuiltinByteString argument.

If the two list arguments have mismatched lengths, the longer argument will be truncated to match the length of the shorter one:

• writeBits bs [0, 1, 4] [True] is the same as writeBits bs [0] [True]
• writeBits bs [0] [True, False, True] is the same as writeBits bs [0] [True]

Note

This differs slightly from the description of the corresponding operation in CIP-122; instead of a single changelist argument comprised of pairs, we instead pass two lists, one for indexes to change, and one for the values to change those indexes to. Effectively, we are passing the changelist argument 'unzipped'.

See also

• Bit indexing scheme
• Operation description

Given a length (first argument) and a byte (second argument), produce a BuiltinByteString of that length, with that byte in every position. Will error if given a negative length, or a second argument that isn't a byte (less than 0, greater than 255).

See also

• Operation description

Shift a BuiltinByteString, as per CIP-123.

Rotate a BuiltinByteString, as per CIP-123.

Count the set bits in a BuiltinByteString, as per CIP-123.

Find the lowest index of a set bit in a BuiltinByteString, as per CIP-123.

If given a BuiltinByteString which consists only of zero bytes (including the empty BuiltinByteString, this returns -1.