Specifications of network protocols and implementations of components running these protocols which support a family of Ouroboros Consesus protocols; the diffusion layer of the Cardano Node.
However, once a user has defined the node socket path, the other two seem totally redundant, because the node we are connecting to already knows these values and the client can't make the node change them.
The proposed solution is that the client should only need to specify the node socket path, connect to it, and then be able to query the node for anything else it needs.
Related to https://github.com/input-output-hk/cardano-node/issues/4402
In order for a
cardano-api
user to connect to a local node socket, the user currently has to fill this struct (defined in the API):However, once a user has defined the node socket path, the other two seem totally redundant, because the
node
we are connecting to already knows these values and the client can't make thenode
change them.The proposed solution is that the client should only need to specify the node socket path, connect to it, and then be able to query the
node
for anything else it needs.