Which part of the daemon RPC is restricted?

Question

When running monerod with restricted-rpc which of the rpc methods will not be allowed?

Also, is the daemon RPC documentation on getmonero.org up to date? If not, is there an up to date version somewhere?

Answer 1

When running monerod with restricted-rpc which of the rpc methods will not be allowed?

From the help:

Restrict RPC to view only commands and do not return privacy sensitive data in RPC calls

In the context of the daemon, when running with restricted-rpc, any potentially private information is restricted. One such example is the /get_info command, when in restricted mode, a number of the returned fields are omitted/masked.

Also, is the daemon RPC documentation on getmonero.org up to date?

It's the most up-to-date documentation available beyond reading the code. It had a major refresh not long ago, but there are already minor changes (things like additional fields that may have been added in responses for example). Whilst it may not be fully up-to-date, what is documented will work as documented because we aim to ensure any changes to the RPC are backwards compatible.

Answer 2

When running monerod with restricted-rpc which of the rpc methods will not be allowed?

The following changes occur when Monerod daemon runs in Restricted Mode via restricted-rpc and/or rpc-restricted-bind-port options.

The following RPC methods are not registered:

flush_txpool
generateblocks
get_alternate_chains
get_bans
get_coinbase_tx_sum
get_peer_list
in_peers
mining_status
on_get_connections
on_set_bans
out_peers
relay_tx
save_bc
set_bans
set_limit
set_log_categories
set_log_hash_rate
set_log_level
start_mining
start_save_graph
stop_daemon
stop_mining
stop_save_graph
sync_info
update

Also, is the daemon RPC documentation on getmonero.org up to date? If not, is there an up to date version somewhere?

You can find interesting alternative reference at Monerod Restricted RPC Mode and referenced code at monero-project/monero/rpc.