Files
xahaud/src/ripple/protocol
seelabs 1b4e0f5f48 Tidying & Selectively forward manifests to peers:
* Do not forward manifests to peers that already know that manifest
* Do not forward historical manifests to peers
* Save/Load ValidatorManifests from a database
* Python test for setting ephmeral keys
* Cleanup manifest interface
2015-05-28 08:16:56 -07:00
..
2015-05-22 11:09:50 -07:00
2015-05-22 11:09:50 -07:00
2015-05-22 11:09:50 -07:00
2015-05-20 13:23:59 -07:00
2015-05-22 11:09:50 -07:00
2015-05-22 11:09:50 -07:00
2015-05-22 11:09:50 -07:00
2015-05-22 11:09:50 -07:00
2015-05-28 07:21:08 -07:00
2015-05-20 13:23:59 -07:00
2015-05-22 11:09:50 -07:00
2015-05-22 11:09:50 -07:00
2015-05-22 11:09:50 -07:00
2015-05-22 11:09:50 -07:00
2015-05-20 13:23:59 -07:00
2015-05-06 13:11:24 -07:00
2015-05-22 11:09:50 -07:00
2015-05-22 11:09:50 -07:00
2015-05-22 11:09:50 -07: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.