Description
We currently use a lot of auxiliary types to interact with IPC RPC API because the response given by the Lotus API doesn't use tuple serialization like the one from the actors, so we can't directly use the type definition from IPC actors here to deserialize the responses: https://github.com/consensus-shipyard/ipc-agent/blob/2362b6b9b67ebe909d46d3e4d4491ea6ab2e7275/src/lotus/message/ipc.rs#L36-L62
However, we are already implemented serialized versions of the RPC methods for some of them (like those involving checkpoints), to avoid requiring this intermediate representation and so we can directly use the tuple serializable versions of the objects defined in the actors. We should consider doing this for all calls and removing the intermediate representations: https://github.com/consensus-shipyard/ipc-agent/blob/2362b6b9b67ebe909d46d3e4d4491ea6ab2e7275/src/lotus/client.rs#L326-L327