Files
xahaud/src/ripple/protocol
Josh Juran 0dd6b95ac2 Add Validator Manifests (RIPD-772):
A Validator Manifest allows validators to use a generated ed25519
secret key as a master key for generating new validator public/secret
key pairs. Using this mechanism, rippled instances trust the master
ed25519 public key instead of the now-ephemeral validator public key.

Through a new message and propagation scheme, this lets a validator
change its ephemeral public key without requiring that all rippled
instances on the network restart after maintaining the configuration
file.
2015-05-28 07:22:32 -07:00
..
2015-05-28 07:22:32 -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.