Module nash_protocol::types[−][src]

Expand description

Types shared across the client and protocol requests

Re-exports

`pub use blockchain::eth;`
`pub use blockchain::neo;`
`pub use blockchain::AssetOrCrosschain;`
`pub use blockchain::Prefix;`
`pub use blockchain::PublicKey;`
`pub use exchange::AccountTradeSide;`
`pub use exchange::Amount;`
`pub use exchange::Asset;`
`pub use exchange::AssetAmount;`
`pub use exchange::AssetofPrecision;`
`pub use exchange::Blockchain;`
`pub use exchange::BuyOrSell;`
`pub use exchange::Candle;`
`pub use exchange::CandleInterval;`
`pub use exchange::DateTimeRange;`
`pub use exchange::Market;`
`pub use exchange::Nonce;`
`pub use exchange::Order;`
`pub use exchange::OrderCancellationPolicy;`
`pub use exchange::OrderCancellationReason;`
`pub use exchange::OrderRate;`
`pub use exchange::OrderStatus;`
`pub use exchange::OrderType;`
`pub use exchange::OrderbookOrder;`
`pub use exchange::Rate;`
`pub use exchange::Trade;`
`pub use keys::ApiKeys;`

blockchain	Types used across protocol requests for constructing and validating blockchain payload data. Any types specific to an individual protocol request will live in the respective module.
exchange	Types used for protocol request inputs (arguments) and outputs. Types specific to a single protocol request will live within the respetitive module. For example `protocol::place_order`.
keys	This module manages the `ApiKeys` type and its general set of functionality, including parsing keys from a JSON file, signing request payloads, and signing blockchain data with MPC child keys.