Skip to content

Commit abeb01b

Browse files
committed
Clarify endianess of integers in xUDT
1 parent 24b7a6f commit abeb01b

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

rfcs/0052-extensible-udt/0052-extensible-udt.md

+5-4
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,9 @@ type:
3232
lock:
3333
<user_defined>
3434
```
35-
36-
The added `xUDT args` and `xUDT data` parts provide all the new functions needed
37-
by xUDT, the detailed structure is explained below.
35+
The `amount` is a 128-bit unsigned integer in little endian format. The added `xUDT
36+
args` and `xUDT data` parts provide all the new functions needed by xUDT, the
37+
detailed structure is explained below.
3838

3939
### **xUDT Args**
4040

@@ -44,7 +44,8 @@ xUDT args has the following structure:
4444
<4-byte xUDT flags> <Variable length bytes, extension data>
4545
```
4646

47-
Depending on the content of `flags`, different extension data might be attached:
47+
Depending on the content of `flags`, which is represented as a 32-bit unsigned
48+
integer in little-endian format, different extension data might be attached:
4849

4950
• If `flags & 0x1FFFFFFF` is 0, no extension data is required. Note a
5051
backward-compatible way of viewing things, which is that a plain sUDT cell also

0 commit comments

Comments
 (0)