From abeb01be8c0b1491ac8a1ab3908416e9ab3cc432 Mon Sep 17 00:00:00 2001 From: xjd Date: Mon, 20 May 2024 13:32:03 +0800 Subject: [PATCH] Clarify endianess of integers in xUDT --- rfcs/0052-extensible-udt/0052-extensible-udt.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/rfcs/0052-extensible-udt/0052-extensible-udt.md b/rfcs/0052-extensible-udt/0052-extensible-udt.md index 251945c9..e2125d22 100644 --- a/rfcs/0052-extensible-udt/0052-extensible-udt.md +++ b/rfcs/0052-extensible-udt/0052-extensible-udt.md @@ -32,9 +32,9 @@ type: lock: ``` - -The added `xUDT args` and `xUDT data` parts provide all the new functions needed -by xUDT, the detailed structure is explained below. +The `amount` is a 128-bit unsigned integer in little endian format. The added `xUDT +args` and `xUDT data` parts provide all the new functions needed by xUDT, the +detailed structure is explained below. ### **xUDT Args** @@ -44,7 +44,8 @@ xUDT args has the following structure: <4-byte xUDT flags> ``` -Depending on the content of `flags`, different extension data might be attached: +Depending on the content of `flags`, which is represented as a 32-bit unsigned +integer in little-endian format, different extension data might be attached: • If `flags & 0x1FFFFFFF` is 0, no extension data is required. Note a backward-compatible way of viewing things, which is that a plain sUDT cell also