If you want more content like this, please visit ripple.com.
Ripple has released
rippled version 0.60.0, which introduces several enhancements that improve the reliability and scalability of the Ripple Consensus Ledger (RCL), including Interledger Protocol compatibility for ledger interoperability. Ripple recommends that all server operators upgrade to version 0.60.0 by Thursday, 2017-03-30, for service continuity.
Highlights of this release include:
Escrow (previously called SusPay), which permits users to cryptographically escrow XRP on RCL with an expiration date using a hashlock crypto-condition.
Dynamic UNL Lite, which allows
rippledto automatically adjust which validators it trusts based on recommended lists from trusted publishers.
Ripple expects Escrow, the previously announced Payment Channels, and the new fix1368 amendment to be enabled via Amendments called Escrow, PayChan, and
fix1368, respectively, on Thursday, 2017-03-30.
If you operate a
rippled server, then you should upgrade to version 0.60.0 by Thursday, 2017-03-30, for service continuity.
Impact of Not Upgrading
If you operate a
rippled server but don’t upgrade to version 0.60.0 by Thursday, 2017-03-30, when Escrow and PayChan are expected to be activated via Amendment, then your server will become amendment blocked, meaning that your server:
- Cannot determine the validity of a ledger
- Cannot submit or process transactions
- Does not participate in the consensus process
- Does not vote on future amendments
- Could rely on potentially invalid data
If the Escrow and PayChan amendments do not get approved, then your server will not become amendment blocked and should continue to operate.
For instructions on updating
rippled on supported platforms, see Updating
rippled on supported platforms.
The sha256 for the rpm is: 4d2acb2a40e2d18ba1737098efdca54caa823a403ce9562c83e2dd2c9e959588
The sha256 for the source rpm is: 3437a0202e762801869f31bf798417ebdb3717e16c4381dc0e9b02fe75d23024
For other platforms, please compile version 0.60.0 from source.
The first log entry should be the change setting the version:
commit 0df1b09a731ba0feaa5d60046e1c7dd415f5f7ed Author: Nik Bougalis <email@example.com> Date: Thu Mar 16 13:33:29 2017 -0700 Set version to 0.60.0
The Ripple operations team plans to deploy version 0.60.0 to all
rippled servers under its operational control, including private clusters, starting at 7:00 PM PST on Thursday, 2017-03-16. The deployment is expected to complete within 4 hours. The network should continue to operate during deployment and no outage is expected.
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.
Full Release Notes
The rippled version 0.60.0 release includes Escrow, (previously called SusPay), which introduces a new ledger node type and several new transaction types to the Ripple network. Escrow permits users to cryptographically escrow XRP on RCL with an expiration date using a crypto-condition called preimage-sha-256, commonly referred to as a hashlock. An XRP Escrow transaction on RCL can be used together with Interledger, to allow a payment to be routed without having to trust third-party intermediaries. We believe this will open a range of possibilities and use cases for XRP, particularly when sending high value, low volume payments cross-border.
The amendment for Payment Channels was originally introduced in version 0.33.0, but is now ready for Payment Channels to be enabled on the production Ripple Consensus Ledger. XRP Payment Channels are intended for high volume, low value payments. They provide a method for scalable, intermittent, off-ledger settlement flowing in a single direction. For bidirectional payment channels, an XRP Payment Channel can be used in each direction. The recipient can claim any unpaid balance at any time before the channel closes. The owner can top off the channel as needed and must wait out a delay to close the channel to give the recipient a chance to supply any claims. The total amount paid increases monotonically as newer claims are issued.
Dynamic UNL Lite
At the core of RCL is the consensus process. Through the consensus process, validating nodes agree on a specific subset of the candidate transactions to be considered for the next ledger. Consensus is an iterative process in which nodes relay proposals, or sets of candidate transactions. Nodes communicate and update proposals until a supermajority of peers agree on the same set of candidate transactions.
During consensus, each node evaluates proposals from a specific set of peers, called chosen validators. Chosen validators represent a subset of the network which, when taken collectively, is “trusted” not to collude in an attempt to defraud the node evaluating the proposals. This definition of “trust” does not require that each individual chosen validator is trusted. Rather, validators are chosen based on the expectation they will not collude in a coordinated effort to falsify data relayed to the network.
rippled version 0.60.0 release introduces new Dynamic UNL configuration options, which allow
rippled to update its set of trusted validators without reconfiguring and restarting. Instead of specifying a static list of trusted validators in the config or validators file, you can configure a trusted publisher key and a URI where the publisher serves signed lists of validators.
rippled will regularly query the configured URIs for the latest recommended list of validators from the trusted publishers. Configuring the validation quorum is no longer required, as
rippled will automatically update its quorum based on its current trusted validator set.
Dynamic UNL Lite is a progressive step towards fully automated dynamic UNLs, to which each client of the Ripple network determines its UNL through policies, rather than trusting a pre-provided list of validators.
Version 0.60.0 also introduces the fix1368 Amendment to fix a minor bug in transaction processing that causes some payments to fail when they should be valid. Specifically, during payment processing, some payment steps that are expected to produce a certain amount of currency may produce a microscopically different amount, due to a loss of precision related to floating-point number representation. When this occurs, those payments fail because they cannot deliver the exact amount intended. The fix1368 amendment corrects transaction processing so payments can no longer fail in this manner.
These features underline Ripple’s continued support to improving RCL by making it more stable, distributed and scalable for settlement of global payments.
We do not have an update on the previously announced changes to the hash tree structure that
rippled uses to represent a ledger, called SHAMapV2. At the time of activation, this amendment will require brief scheduled allowable unavailability while the changes to the hash tree structure are computed by the network. We will keep the community updated as we progress towards this date (TBA).
0.60.0 Change Log
- Add Escrow support (#2039)
- Dynamize trusted validator list and quorum (#1842)
- Simplify fee handling during transaction submission (#1992)
- Publish server stream when fee changes (#2016)
- Replace manifest with validator token (#1975)
- Add validator key revocations (#2019)
- Add SecretKey comparison operator (#2004)
- Reduce LEDGER_MIN_CONSENSUS (#2013)
- Update libsecp256k1 and Beast B30 (#1983)
- Make Config extensible via lambda (#1993)
- WebSocket permessage-deflate integration (#1995)
- Do not close socket on a foreign thread (#2014)
- Update build scripts to support latest boost and ubuntu distros (#1997)
- Handle protoc targets in scons ninja build (#2022)
- Specify syntax version for ripple.proto file (#2007)
- Eliminate protocol header dependency (#1962)
- Use gnu gold or clang lld linkers if available (#2031)
- Add tests for lookupLedger (#1989)
- Add unit test for get_counts RPC method (#2011)
- Add test for transaction_entry request (#2017)
- Unit tests of RPC “sign” (#2010)
- Add failure only unit test reporter (#2018)
- Enforce rippling constraints during payments (#2049)
- Fix limiting step re-execute bug (#1936)
- Make “wss” work the same as “wss2” (#2033)
- Check for malformed public key on payment channel (#2027)
- Config test uses unique directories for each test (#1984)
- Send a websocket ping before timing out in server (#2035)
Please visit ripple.com for more information.