Skip to content

Enable Public Signing

By default, the signing methods for xrpld are limited to administrative connections. If you want to allow signing methods to be used as public API methods (like with versions of xrpld before v1.1.0), you can enable it with a configuration change.

This enables the following methods to be used on "public" JSON-RPC and WebSocket connections, if your server accepts them:

You do not need to enable public signing to use these methods from an admin connection.

Caution
Ripple does not recommend enabling public signing. Like the wallet_propose method, the signing commands do not perform any actions that would require administrative-level permissions, but restricting them to admin connections protects users from irresponsibly sending or receiving secret keys over unsecured communications, or to servers they do not control.

To enable public signing, perform the following steps:

  1. Edit your xrpld's config file.

    vim /etc/xrpld/xrpld.cfg

    The recommended installation uses the config file /etc/xrpld/xrpld.cfg by default. Other places you can put a config file include $HOME/.config/xrpld/xrpld.cfg (where $HOME is the home directory of the user running rippled), $HOME/.local/xrpld/xrpld.cfg, or the current working directory from where you start rippled.

    The config file was renamed from rippled.cfg to xrpld.cfg. During the transition, if xrpld.cfg is not present the server still reads rippled.cfg from the same locations, so existing config files keep working without being renamed. Updated in: rippled 3.2.0

  2. Add the following stanza to your config file, and save the changes:

    [signing_support]
    true
  3. Restart your xrpld server:

    systemctl restart xrpld

See Also