The CLVM serialization format closely follows the in-memory representation of the program tree.
This in turn, closely resembles the text format of a fully compiled CLVM program.
At the lowest level, there are only three types of Object in the CLVM.
- Cons Cells
- Nil, a subtype of Value
Each CLVM Object is represented by a series of one or more bytes. Each byte belongs to the representation of exactly one CLVM Object. That is, no bits in a byte are shared by multiple CLVM objects.
Each value in the CLVM is an untyped sequence of bytes. In the running virtual machine, values have a property length, containing the number of bytes. The same concept is preserved in the serialization format. However, values must be distinguished from cons boxes in the byte stream, so an escaping scheme is used. This escaping means that serialized values using more than 7 bits have a different representation than the in memory representation.
Nil has a single predefined value which is not shared with any user-defined value.
Values which can be represented in 7 bits are encoded as a single byte with that value. Larger serialized values are represented as a sequence of bytes that encode the size, and then the value bytes.
The encoding scheme for the size prefix is as follows:
The value of the first serialized byte determines the number of size bytes (1 to 6, including the first byte). The size then determines the number of bytes denoting the value (0 to 0x400000000-1 bytes long)
size is the length of the byte array containing the value, as an integer. In the table below, we use s to describe the bytes that make up the encoded size value, s being the least significant byte of size. The size bytes are encoded MSB first.
In the table below, the bits marked x contain the length of the value array, in bytes.
|Size bytes||Min Value Len||Max Value Length||Byte 1||Byte 2||Byte 3||Byte 4||Byte 5|
The decoding scheme is as follows:
c is the first byte of the serialized CLVM object.
size is the number of bytes contained in the value byte array s is the byte array containing the bytes of the two's complement integer size, the number of bytes in the value array. value is the span of bytes describing the CLVM Object itself
c can contain the entire value, or it can be part of the size header. Values below 0x80 do not have size header bytes.
0x00-0x7f: A literal one byte value. c contains the value.
size = 1; value = c
0x80-0xbf: The value starts at the byte c, and size is in the lower 6 bits of c
size = (c & 0x3F); value = c .. c[size]
0xc0-0xdf: The value starts at c; the lower 5 bits of c are the high bits of size
size = (c & 0x1F) .. c; value = c .. c[size+1]
0xe0-0xef: The value starts at c; the lower 4 bits of c are the high bits of size
size = (c & 0x0F) .. c; value = c .. c[size+2]
0xf0-0xf7: The value starts at c; the lower 3 bits of c are the high bits of size
size = (c & 0x07) .. c; value = c .. c[size+3]
0xf7-0xfb: The value starts at c; the lower 2 bits of c are the high bits of size
size = (c & 0x03) .. c; value = c .. c[size+4]
Atoms of size 0x400000000 or greater are disallowed in the serialization format.
As an example:
In the above example, the length of the value is 4, and we only needed the bottom 3 bits of the c byte to encode the length, so the size is completely described by the first serialized byte. The total lenth of the encoded atom is 5 bytes.
Note that for values greater than 0x7F, the bytes of the serialized value representing the length are disjoint with the actual value bytes.
Let us consider some special cases.
0x81.Since c is between
0xC0, we know that there is only one sie byte, c, and the value is contained in the following bytes, starting at c. The total size of the value array is
c & 0x3F =
0x1. So, the full value is contained in the single following byte.
Note that the special byte 0xFF is allowed within the bytes representing a value. 0xFF denotes a cons box when it is the first byte of a decoded CLVM object, but it may also occur within the serialized bytes of a value.
A 2 byte value
Lists are the primary high-level data structure in most LISP implementations. Traditionally, a LISP builds lists from cons boxes, a two-celled data structure that can be thought of as a struct with two fields, left and right, each of which contains either a value, or a (pointer to) another cons cell.
Because the cons cell is the low level data structure that lists are built from, LISP lists are only lists by way of the fact that lists can be implemented from trees. A lisp list built from cons cells in a binary tree.
Serialized cons cells are represented by the byte 0xFF, followed by the objects in its cells, left then right. Values are represented by a variable length byte-aligned encoding scheme, described above. Nil is chosen to be the zero-length object, which is represented by the byte 0x80.
Because lists are represented as a sequence of cons boxes, the byte 0xff occurs frequently in the serialization format.
After the FF introducer byte, the next two values describe what is in the left and right cons boxes, respectively.
The first examples use single byte values for clarity.
The list (1 2 3) will be encoded as:
This can be read as:
(a cons box containing 01 and
a cons box (containing 02 and
a cons box (containing 03 and nil)))
Alternatively, it could be viewed as a binary tree that looks like this:
Or, as a chain of memory cells that look like this:
- (a) means "The contents of the memory cells at position a and a+1 (cons box a)"
- ->b means "a pointer to cons box (b)"
(c)are arbitrary labels for the cons cells, and do not exist in the CLVM
Because the above list contains only one level of nesting, a single
0x80 byte is sufficient to terminate the list. Note the two
0x80 bytes in the example below.
There can be many cons cells in a CLVM program, so 0xFF will be common in the serialized program. There will be one serialized nil (0x80) per properly terminated list. Nil may also occur at other places in the program. There are usually more cons boxes than lists, so 0xFF occurs more frequently than 0x80.