XRP Ledger Apex is back in Amsterdam

Register Now
Blog
/
2018
/
rippled Validator Key Replacement
Last updated

rippled Validator Key Replacement

On Wednesday, January 18, 2018, as described in the 0.81.0 release notes, the current validator keys on all five Ripple-operated rippled validator servers will be replaced. If you have been using the previous recommended default configuration and do not reconfigure your rippled server to the new recommended default configuration before that time, then your rippled server will stop seeing validated ledgers.

Ripple strongly recommends upgrading to rippled version 0.81.0 immediately.

Action Required

If you operate a rippled server, then you should upgrade to 0.81.0 immediately.

Ripple recommends that you:

  • Edit your rippled.cfg to remove the [validators] section, if one is present

  • Add a [validators_file] section if one is not present, and add the name of your validators.txt file.

  • Replace the contents of any existing validators.txt file with the version included with this release. If you are upgrading to rippled version 0.81.0 using the rippled RPM package, then your default validators.txt file may automatically be updated, in which case you will not need to modify the file. The validators.txt file is usually in the same directory as your rippled.cfg file.

  • After starting your rippled server, confirm that it is configured to use the new defaults by executing:

    /opt/ripple/bin/rippled validators

The result should include the following:

"local_static_keys" : [],
"publisher_lists" : [
    {
        "available" : true,
        "expiration" : "2018-Jan-23 00:00:00",
        "list" : [
            "nHB1FqfBpNg7UTpiqEUkKcAiWqC2PFuoGY7FPWtCcXAxSkhpqDkm",
            "nHUpwrafS45zmi6eT72XS5ijpkW5JwfL5mLdPhEibrqUvtRcMAjU",
            "nHUBGitjsiaiMJBWKYsJBHU2shmYt9m29hRqoh8AS5bSAjXoHmdd",
            "nHUXh1ELizQ5QLLqtNaVEbbbfMdq3wMkh14aJo5xi83xzzaatWWP",
            "nHUgoJvpqXZMZwxh8ZoFseFJEVF8ryup9r2mFYchX7ftMdNn3jLT"
            ],
        "pubkey_publisher" : "ED2677ABFFD1B33AC6FBC3062B71F1E8397C1505E1C42C64D11AD1B28FF73F4734",
        "seq" : 2,
        "version" : 1
    }
],

Impact of Not Upgrading

  • If you operate a rippled server, but do not upgrade to rippled version 0.81.0, then your rippled server may periodically drop transactions and fall out of sync with the network.

  • On Wednesday, January 17, 2018, as described in the 0.81.0 release notes, the current validator keys on all five Ripple-operated rippled validator servers will be replaced. **If you have been using the recommended default configuration **and do not reconfigure your rippled server before that time, then your rippled server will stop seeing validated ledgers.

For instructions on updating rippled on supported platforms, see Updating rippled on supported platforms.

The sha256 for the RPM is: 75acdf54e472875bff609fa2d1cc59524e4d8f8e885751b50aaeb85938ab3609

The sha256 for the source RPM is: fbc95f6168d015190b93b81f97c20979886fa2f6663e4dd15157409075db46e9

For other platforms, please compile version 0.81.0 from source.

The first log entry should be the change setting the version:

commit 4e8c8deeaac83d18eb62c95b7425d96e11847a41
Author: Nikolaos D. Bougalis <[email protected]>
Date:   Wed Jan 3 14:43:42 2018 -0800

    Set version to 0.81.0

0.81.0 Change Log

  • New hosted validator configuration

Bug Fixes

  • Optimize queries for account_tx to work around SQLite query planner (#2312)

Network Update

The Ripple technical operations team deployed rippled version 0.81.0 to all rippled validator servers under its operational control, on Tuesday, 2018-01-09.

Learn, ask questions, and discuss

Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.

Other resources: