Files
rippled/include/xrpl/protocol
Bronek Kozicki 4425f84c1f Remove directory size limit (#5935)
This change introduces the `fixDirectoryLimit` amendment to remove the directory pages limit. We found that the directory size limit is easier to hit than originally assumed, and there is no good reason to keep this limit, since the object reserve provides the necessary incentive to avoid creating unnecessary objects on the ledger.
2025-10-31 14:26:44 +00:00
..
2025-08-22 10:02:56 -04:00
2024-06-20 13:57:14 -05:00
2025-07-10 18:15:42 +00:00
2024-06-20 13:57:16 -05:00
2025-06-02 09:52:10 -04:00
2025-07-10 18:15:42 +00:00
2024-06-20 13:57:16 -05:00
2024-06-20 13:57:14 -05:00
2024-06-20 13:57:16 -05:00
2025-01-09 11:22:11 -05:00
2024-06-20 13:57:16 -05:00
2024-06-20 13:57:16 -05:00
2025-10-31 14:26:44 +00:00
2024-06-20 13:57:16 -05:00
2024-06-20 13:57:16 -05:00
2024-06-20 13:57:16 -05:00
2025-06-02 09:52:10 -04:00
2024-06-20 13:57:14 -05:00
2024-06-20 13:57:16 -05:00
2025-09-26 20:13:15 +00:00
2025-07-10 18:15:42 +00:00
2025-07-10 18:15:42 +00:00
2025-07-10 18:15:42 +00:00
2025-09-26 20:13:15 +00:00
2025-09-26 20:13:15 +00:00
2025-05-23 19:53:53 +00:00
2024-06-20 13:57:16 -05:00
2025-09-30 18:49:53 +00:00
2025-05-23 19:53:53 +00:00

protocol

Classes and functions for handling data and values associated with the XRP Ledger protocol.

Serialized Objects

Objects transmitted over the network must be serialized into a canonical format. The prefix "ST" refers to classes that deal with the serialized format.

The term "Tx" or "tx" is an abbreviation for "Transaction", a commonly occurring object type.

Optional Fields

Our serialized fields have some "type magic" to make optional fields easier to read:

  • The operation x[sfFoo] means "return the value of 'Foo' if it exists, or the default value if it doesn't."
  • The operation x[~sfFoo] means "return the value of 'Foo' if it exists, or nothing if it doesn't." This usage of the tilde/bitwise NOT operator is not standard outside of the rippled codebase.
    • As a consequence of this, x[~sfFoo] = y[~sfFoo] assigns the value of Foo from y to x, including omitting Foo from x if it doesn't exist in y.

Typically, for things that are guaranteed to exist, you use x[sfFoo] and avoid having to deal with a container that may or may not hold a value. For things not guaranteed to exist, you use x[~sfFoo] because you want such a container. It avoids having to look something up twice, once just to see if it exists and a second time to get/set its value. (Real example)

The source of this "type magic" is in SField.h.