The RLP implementation of receipt is incorrect

[yangby-cryptape]

Contact Details

No response

Current Behavior

Summary

If "Axon is compatible with Ethereum" as that written in the README.md, the RLP implementation of receipt is incorrect.

Details

Here is the RLP implementation of receipt in Axon:

axon/protocol/src/codec/receipt.rs

Lines 5 to 22 in c7a471b

	impl Encodable for Receipt {
	fn rlp_append(&self, s: &mut RlpStream) {
	s.begin_list(13)
	.append(&self.tx_hash)
	.append(&self.block_number)
	.append(&self.block_hash)
	.append(&self.tx_index)
	.append(&self.state_root)
	.append(&self.used_gas)
	.append(&self.logs_bloom)
	.append_list(&self.logs)
	.append(&self.log_index)
	.append(&self.code_address)
	.append(&self.sender)
	.append(&bincode::serialize(&self.ret).unwrap())
	.append(&self.removed);
	}
	}

Yes, in legacy Ethereu JSON-RPC Specification (a.k.a. Ethereum Execution API Specification now), a receipt will have more that 10 fields.

But when do RLP of a receipt, only 4 fields should be used, that was written in section 4.3.1 of Ethereum Yellow Paper since the day when Ethereum launched.

... ... the status code of the transaction, $R_{z}$, the cumulative gas used in the block containing the transaction receipt as of immediately after the transaction has happened, $R_{u}$, the set of logs created through execution of the transaction, $R_{l}$, and the Bloom filter composed from information in those logs, $R_{b}$:

... ...

The function $L_{R}$ prepares a transaction receipt for being transformed into an RLP-serialised byte array:

$$L_{R}(R) = (R_{z},R_{u},R_{b},R_{l})$$

Also, you could NOT restore a JSON-RPC receipt from a RLP-serialised receipt.

Expected Behavior

None.

OS

Not Associated

Axon version

No response

Kernel

Not Associated

Relevant log output

No response

Anything else?

No response

[KaoImin]

Fix in #1270