14:04:21 m​oneromooo: in JSON-RPC responses that have binary fields like `get_txpool_backlog`, do you know what type of binary it is? Epee? Bitcasted struct? asking because you wrote the line that does it: https://github.com/monero-project/monero/blame/cc73fe71162d564ffda8e549b79a350bca53c454/src/rpc/core_rpc_server_commands_defs.h#L1660 14:05:40 in that case, it's `std::vector`, how does the container get serialized? is it length + bytes? 14:06:54 KV_SERIALIZE is epee. _AS_BLOB is verbatim bitstream, plus probably type and length (likely varint). 14:08:01 Now, that is probanly broken, since one of the fields in that struct is a std::string, so as blob ought to write the internals of the string, which allocates for long strings... 14:08:33 Oh nvm, there are two structs with the same name in two different scopes. Seems OK. 14:28:44 what about _CONTAINER_POD_AS_BLOB? is it `[type, total_length, ]`? 14:31:23 unless that is what you meant by _AS_BLOB, although there's a separate macro for values and not containers 15:18:16 That just serializes a string in the epee format. The length of the container is implied from the length of the string: container_len = string_len / bytes_per_element 15:29:46 Do people who translate monero stuff get money from community? 15:30:58 no. take that question to -community or #monero, though. 15:31:24 okay. sorry for being disturbing 18:49:50 jeffro256: thanks, so the `backlog` field in `get_txpool_backlog` is just epee? 18:51:39 Sorry that was if you're serializing in epee. In both epee format and JSON, _CONTAINER_POD_AS_BLOB simply serializes a string 18:52:47 it makes the same string (packed binary blobs) which gets serialized depending on which format you use 18:53:45 jeffro256 PM when you can, thanks! 19:05:19 No changes are done for format afaik. The caller is required to do convert bin to hex before giving it to the serialization system. This was something that I changed in my serialization patch - types that were blobs called a `binary(...)` function that did on the fly hex conversion when needed 19:10:40 Wouldn't that make new payloads not compatible? 20:07:11 Im not sure what you mean. New payloads don't need to do the manual conversion anymore, just mark as binary.