cuprate-hinto-janai/rpc/types
hinto.janai 5cf2c875d7
Some checks are pending
Audit / audit (push) Waiting to run
Deny / audit (push) Waiting to run
specify commit in macro, add () type aliases
2024-06-16 16:45:10 -04:00
..
src specify commit in macro, add () type aliases 2024-06-16 16:45:10 -04:00
Cargo.toml monero-rpc-types -> cuprate-rpc-types 2024-06-16 15:59:25 -04:00
README.md fix modules 2024-06-16 16:23:32 -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, for example:

{
  "string": "",
  "float": 30.0,
  "integer": 30,
  "binary": /* serialized binary */
}

TODO: list the specific types.