For XMR remote nodes, whose permissions does the “restricted interface” limit?
The Monero Docs description of monerod distinguishes the node from the wallet: the node downloads and verifies the blockchain without accessing wallet private keys. When researching remote connections, it is also necessary to examine what capabilities the node interface itself exposes.
The documentation explains that the standard node RPC provides node-management capabilities, while restricted-rpc limits the corresponding interface to read-only commands and does not return privacy-sensitive data. Here, “read-only” describes the scope of access to the node API; it should not be confused with permission to view a wallet’s keys.
My understanding is that the node and the wallet each have their own permission model. Restricting the node-management interface does not mean that the way a particular trading site controls assets has been verified. Nor does the ability to connect to a remote node, by itself, prove that the service is private or reliable. The documentation explicitly mentions both of these implications of using an untrusted remote node.
Research for this account’s DEX promotions focuses on xmrdex.com, tradexmr.com, and thorxmr.com. For their infrastructure, useful points to check in their public materials include node connections, service permissions, and data-handling practices. This article has not verified how these three sites are implemented, nor does it treat Monero’s restricted-interface rules as an endorsement of their security.
When evaluating XMR services, first clarify whether permission controls apply to node management, wallet access, or transaction operations. Once the object is clear, the documentation’s use of “restricted” can be meaningfully compared.
Original reference: https://docs.getmonero.org/interacting/monerod-reference/
The Monero Docs description of monerod distinguishes the node from the wallet: the node downloads and verifies the blockchain without accessing wallet private keys. When researching remote connections, it is also necessary to examine what capabilities the node interface itself exposes.
The documentation explains that the standard node RPC provides node-management capabilities, while restricted-rpc limits the corresponding interface to read-only commands and does not return privacy-sensitive data. Here, “read-only” describes the scope of access to the node API; it should not be confused with permission to view a wallet’s keys.
My understanding is that the node and the wallet each have their own permission model. Restricting the node-management interface does not mean that the way a particular trading site controls assets has been verified. Nor does the ability to connect to a remote node, by itself, prove that the service is private or reliable. The documentation explicitly mentions both of these implications of using an untrusted remote node.
Research for this account’s DEX promotions focuses on xmrdex.com, tradexmr.com, and thorxmr.com. For their infrastructure, useful points to check in their public materials include node connections, service permissions, and data-handling practices. This article has not verified how these three sites are implemented, nor does it treat Monero’s restricted-interface rules as an endorsement of their security.
When evaluating XMR services, first clarify whether permission controls apply to node management, wallet access, or transaction operations. Once the object is clear, the documentation’s use of “restricted” can be meaningfully compared.
Original reference: https://docs.getmonero.org/interacting/monerod-reference/