rlp: add int8, int16, int32 and int64

[mhw0]

No description provided.

[foonsun]

great job!

[mhw0]

I’m not sure if we actually need this.

[foonsun]

Yes, Ethereum's smart contract ABI (Application Binary Interface) requires support for data types such as int8 and int16. This is because these data types are built-in to Solidity contracts. If your contract uses these data types, you will need to use the corresponding data types in the ABI interface. However, it's worth noting that not all programming languages require support for these specific data types, so whether or not you need to implement them will depend on the specific language you are using. mhw0 ***@***.***> 于2023年5月30日周二 10:27写道：

…

I’m not sure if we actually need this. — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABRSHVGYJ6CCA6VQJV5FY63XIVLI7ANCNFSM6AAAAAAXTZDBY4> . You are receiving this because you commented.Message ID: ***@***.***>

[mhw0]

If we look at the documentation, we can see that we already have functions for encoding/decoding ABI int8, int16, int32 and int64.

These might be useful when the RLP functions are used in different context (when serializing and deserializing some "non ethereum data?")

[foonsun]

when

yes. we can sign the message for the cross-chain validation. The message can be in any types.

[mhw0]

Closing the issue. I don't think we need these.