mirror of
https://github.com/XRPLF/rippled.git
synced 2026-09-27 23:38:08 +00:00
The two byte-order conventions are the part worth writing down: a parameter answers little-endian integers, a data read answers the canonical big-endian serialization, and the TER an emit produces is four little-endian bytes in an output region rather than the call's result. Adds the four marshalling shapes the contract functions bring to the e2e table, and the fixtures that stand a contract host up.