cuprate-hinto-janai/rpc/types
2024-07-01 20:53:16 -04:00
..
src rpc: use feature flags in misc types 2024-07-01 20:53:16 -04:00
Cargo.toml rpc: add/doc feature flags 2024-07-01 20:52:57 -04:00
README.md rpc: add/doc feature flags 2024-07-01 20:52:57 -04:00

Monero RPC types.

What

This crate ports the types used in Monero's RPC interface, including:

  • JSON types
  • Binary (epee) types
  • Mixed types
  • Other commonly used RPC types

Modules

This crate's types are split in the following manner:

This crate has 4 modules:

  • The root module; cuprate_rpc_types
  • [json] module; JSON types from the /json_rpc endpoint
  • [bin] module; Binary types from the binary endpoints
  • [other] module; Misc JSON types from other endpoints

Miscellaneous types are found in the root module, e.g. [crate::Status].

Each type in {json,bin,other} come in pairs and have identical names, but are suffixed with either Request or Response. e.g. GetBlockCountRequest & GetBlockCountResponse.

Documentation

The documentation for types within {json,bin,other} are omitted, as they can be found in Monero's RPC documentation.

However, each type will document:

  • Definition: the exact type definition location in monerod
  • Documentation: the Monero RPC documentation link
  • Request/response: the other side of this type, either the request or response

Naming

The naming for types within {json,bin,other} follow the following scheme:

  • Convert the endpoint or method name into UpperCamelCase
  • Remove any suffix extension

For example:

Endpoint/method Crate location and name
get_block_count [json::GetBlockCountRequest] & [json::GetBlockCountResponse]
/get_blocks.bin bin::GetBlocksRequest & bin::GetBlocksResponse
/get_height other::GetHeightRequest & other::GetHeightResponse

TODO: fix doc links when types are ready.

Mixed types

Note that some types within [other] mix JSON & binary together, i.e., the message overall is JSON, however some fields contain binary values inside JSON strings, for example:

{
  "string": "",
  "float": 30.0,
  "integer": 30,
  "binary": "<serialized binary>"
}

binary here is (de)serialized as a normal [String]. In order to be clear on which fields contain binary data, the struct fields that have them will use [crate::BinaryString] instead of [String].

TODO: list the specific types.

Feature flags

List of feature flags for cuprate-rpc-types.

All are enabled by default.

Feature flag Does what
json Enables the [crate::json] module
bin Enables the [crate::bin] module
other Enables the [crate::other] module
serde Implements serde on all types
epee Implements epee_encoding on all types