mirror of
https://github.com/Cuprate/cuprate.git
synced 2024-12-22 11:39:26 +00:00
request strictness
This commit is contained in:
parent
34dde9f1b7
commit
3554c9c1d5
1 changed files with 11 additions and 0 deletions
|
@ -11,3 +11,14 @@ RPC stuff that needs to be written in the architecture book:
|
|||
- https://github.com/Cuprate/cuprate/issues/278
|
||||
- binary strings -> full JSON: `get_transaction_pool_backlog`, `get_output_distribution`
|
||||
- not in `monerod` yet: `get_tx_ids_loose`
|
||||
|
||||
## Differences with monerod (Request strictness)
|
||||
Some of `monerod`'s RPC request types contain fields not for users to provide,
|
||||
but for internal usage within the RPC handlers and `monerod` itself, some examples:
|
||||
- <LINK_TO_INTERNAL_FIELDS_IN_REQUEST_TYPE>
|
||||
|
||||
Unless one of these actually allows something unintentionally bad to happen, this is mostly an unimportant detail.
|
||||
<CHECK_THAT_ONE_OF_THESE_FIELDS_ISNT_A_SECURITY_FLAW>
|
||||
|
||||
Practically, it means users can provide these fields and `monerod` will deserialize them
|
||||
and accept them fine, while `cuprated` will not because they are not part of the type.
|
||||
|
|
Loading…
Reference in a new issue