Files
rippled/src/ripple/protocol
Vinnie Falco a5583de6e6 Use features instead of ApplyFlags:
tapENABLE_TESTING is removed from checks, and feature enablement
is the sole method for activating features. Unit tests are updated
to enable required features in the construction of the Env.

Tickets are put on a feature switch instead of a build macro.
2015-12-29 12:38:22 -05:00
..
2015-12-29 12:38:22 -05:00
2015-12-18 16:39:29 -08:00
2015-07-13 16:37:04 -07:00
2015-10-06 16:03:38 -07:00
2015-10-13 17:15:45 -07:00
2015-12-29 12:38:22 -05:00
2015-10-13 17:15:45 -07:00
2015-10-13 17:15:45 -07:00
2015-12-18 22:33:57 -08:00
2015-07-31 17:39:03 -07:00
2015-10-13 17:15:45 -07:00
2015-12-01 11:02:27 -08:00
2015-10-13 17:15:45 -07:00
2015-10-13 17:15:45 -07:00
2015-10-20 11:35:24 -04:00
2015-07-13 16:37:04 -07:00
2015-10-13 17:15:45 -07:00
2015-07-31 17:31:18 -07:00
2015-10-20 11:35:24 -04:00
2015-07-29 11:56:05 -04:00
2015-07-31 17:39:03 -07:00
2015-05-06 13:11:24 -07:00
2015-09-03 13:10:50 -07:00
2015-12-18 16:39:29 -08:00
2015-07-31 17:39:03 -07:00
2015-07-31 17:39:03 -07:00
2015-06-25 09:05:06 -07:00
2015-06-02 12:49:30 -07:00
2015-06-25 09:05:06 -07:00
2015-10-20 11:35:24 -04:00

protocol

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

Serialized Objects

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

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