hinto-janai
hinto-janai
## What This is a proposal to deprecate binary string usage in `monerod`'s daemon RPC interface. Binary strings are JSON strings that appear in `monerod`'s daemon RPC output that contain...
### What Adds the `{function, request, response}` signatures needed by `cuprated`'s RPC system to the `{blockchain, txpool, p2p, blockchain_context}` APIs. Described in https://github.com/Cuprate/cuprate/issues/279. This covers the signatures needed for all...
### What Adds types that allow easier JSON representations of a block, transaction, and other common types. ### Why These JSON representations are used in RPC/ZMQ. https://github.com/Cuprate/cuprate/issues/199#issuecomment-2373982398 ### Where `cuprate-types`.
### What Temporary PR holding code for `cuprated`'s `cuprate_rpc_interface::RpcHandler` implementation.
## What This is a discussion for [daemon RPC calls](https://www.getmonero.org/resources/developer-guides/daemon-rpc.html) in `cuprated` that will behave differently than `monerod` or not be supported. The RPC calls considered are the publically available...
## What This is a discussion for what data is required for `cuprated`'s RPC system. Notably, this is: - Blockchain data - Transaction pool data - P2P data - General...
## What Which port numbers will `cuprated` use by default? ## The standard `monerod` uses the following ports as convention/defaults: | Port | Purpose | |-------|---------| | [18080](https://github.com/monero-project/monero/blob/a1dc85c5373a30f14aaf7dcfdd95f5a7375d3623/src/cryptonote_config.h#L226) | P2P...
### What Fixes incorrect documentation for daemon RPC calls; requires review into `monerod`. ### Fixes Table of fixes in this PR, originally tracked here: https://github.com/Cuprate/cuprate/issues/159. | Route/endpoint | Link |...
## What Adds documentation for undocumented request/response fields within daemon RPC calls; requires review into `monerod`. Some of these are lacking descriptions as I'm not sure what the behavior is...