TransWikia.com

Is the set of available RPC calls dependant on the connected node?

Tezos Asked on August 19, 2021

When I am connected to rpcalpha.tzbeta.net through tezos-client -l -A rpcalpha.tzbeta.net -S -P 443 config update I can succesfully call tezos-client activate account alice with <path_to_downloaded_json>.

But when I connect to my own node an run the same command, I get:

% tezos-client activate account alice with <path_to_downloaded_json>                                                                                                                     ~ tezos-node
Error:
  Unrecognized command.
  Try using the man command to get more information.

Usage:

My ‘~/.tezos-client/config’ content when connected to my own node is

{
    "base_dir": "/home/troels/.tezos-client",
    "node_addr": "127.0.0.1",
    "node_port": 9999
}

One Answer

Yes, a subset of the RPCs exposed by the node is provided by the protocol. Thus, depending on the node that you connect to and the protocol that it is running, some RPCs will be available or not. The documentation gives a note on this:

Beware that the commands available on the client depend on the specific protocol run by the node. For instance, get timestamp isn’t available when the node runs the genesis protocol, which may happen for a few minutes when launching a node for the first time.

Here it talks about tezos-client commands, but these are often just wrappers around calls to the node RPCs, a subset of which are defined by the protocol.

Correct answer by arvidj on August 19, 2021

Add your own answers!

Ask a Question

Get help from others!

© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP