A (de)serializer for RLP encoding in ETH
Cargo.toml
serlp = "0.2.2"
serde = { version = "1.0", features = ['derive'] }
Not Supported Types
- bool
- float numbers
- maps
- enum (only deserialize)
We do not support enum when deserializing because we lost some information (i.e. variant index) about the original value when serializing. However, in some specific cases you can derive Deserialize trait for a enum with the help of RlpProxy, which will be discussed later.
We have to choose this approach because there is no enums in Golang while ETH is written in go. Treating enums as a transparent layer can make our furture implementation compatiable with ETH.
Design principle
Accroding to the ETH Yellow Paper, all supported data structure can be represented with either recursive list of byte arrays or byte arrays
. So we can transform all Rust's compound types, for example, tuple, struct and list, into lists. And then encode them as exactly described in the paper
For example, the structure in example code, can be internally treated as the following form:
[
"This is a tooooooooooooo loooooooooooooooooooong tag",
[
114514,
[191, -9810],
[
[[], [[]], [[], [[]]]]
]
],
"哼.啊啊啊啊啊啊啊啊啊啊啊啊啊啊啊啊啊啊"
]
Features
ZST serialization
In Rust, we can represent 'empty' in many ways, for example:
[], (), "", b"", struct Empty, Variant::Empty, None, PhantomData<T>
In our implementation:
[]and()are considered empty list, thus should be serialized into 0xc0- All other ZSTs are considered empty, thus should be serialized into 0x80
To better understand ZSTs' behavior when serializing, try this code:
RLP Proxy
We have a RlpProxy struct that implemented Deserialize trait, which just stores the original rlp encoded data after deserialization (no matter what type it is). You can gain more control over the deserialization process with it.
Here is an example:
Example code
You can find more examples here
use ;
use ;
use serde_bytes;