Published by bachase over 6 years ago
The rippled
0.90.0 release introduces several features and enhancements that improve the reliability, scalability and security of the XRP Ledger.
Highlights of this release include:
DepositAuth
amendment, which lets an account strictly reject any incoming money from transactions sent by other accounts.Checks
amendment, which allows users to create deferred payments that can be cancelled or cashed by their intended recipients.rippled
servers to distribute historical ledger data if they agree to dedicate storage for segments of ledger history.New and Updated Features
account_tx
to work around SQLite query planner (#2312)Journal
to be copied/moved (#2292)[server]
settings (#2305)rippled-example.cfg
(#2307)account_objects
RPC to filter by “check” (#2356)sign_for
returns a correct hash (#2333)beast::currentTimeMillis()
(#2345)Bug Fixes
Published by mDuo13 over 6 years ago
The rippled
0.80.1 release provides several enhancements in support of published validator lists and corrects several bugs.
New and Updated Features
Bug Fixes
Published by seelabs almost 7 years ago
The rippled
0.80.2 release introduces changes that improve the scalability of the XRP Ledger.
New and Updated Features
This release has no new features.
Bug Fixes
Published by bachase almost 7 years ago
The rippled
0.80.1 release provides several enhancements in support of published validator lists and corrects several bugs.
New and Updated Features
Bug Fixes
Published by mDuo13 about 7 years ago
The rippled
0.70.2 release corrects an emergent behavior which causes large numbers of transactions to get stuck in different nodes' open ledgers without being passed on to validators, resulting in a spike in the open ledger fee on those nodes.
New and Updated Features
This release has no new features.
Bug Fixes
Published by mDuo13 about 7 years ago
The rippled
0.70.1 release corrects a technical flaw in the newly refactored consensus code that could cause a node to get stuck in consensus due to stale votes from a
peer, and allows compiling rippled
under the 1.1.x releases of OpenSSL.
New and Updated Features
This release has no new features.
Bug Fixes
Published by mDuo13 about 7 years ago
The rippled
0.70.0 release introduces several enhancements that improve the reliability, scalability and security of the network.
Highlights of this release include:
FlowCross
amendment, which streamlines offer crossing and autobridging logic by leveraging the new “Flow” payment engine.EnforceInvariants
amendment, which can safeguard the integrity of the XRP Ledger by introducing code that executes after every transaction and ensures that the execution did not violate key protocol rules.fix1373
, which addresses an issue that would cause payments with certain path specifications to not be properly parsed.New and Updated Features
Config
init extensible via lambda (#1993)feature
RPC test (#1988)Bug Fixes
asfRequireAuth
flag not always obeyed (#2092)Published by mDuo13 about 7 years ago
The rippled
0.60.3 release helps to increase the stability of the network under heavy load.
New and Updated Features
This release has no new features.
Bug Fixes
Server overlay improvements (#2110)
Published by mDuo13 about 7 years ago
The rippled
0.60.2 release further strengthens handling of cases associated with a previously patched exploit, in which NoRipple flags were being bypassed by using offers.
New and Updated Features
This release has no new features.
Bug Fixes
Prevent the ability to bypass the NoRipple
flag using offers (#7cd4d78)
Published by nbougalis about 7 years ago
The rippled
0.80.0 release introduces several enhancements that improve the reliability, scalability and security of the XRP Ledger.
Highlights of this release include:
SortedDirectories
amendment, which allows the entries stored within a page to be sorted, and corrects a technical flaw that could, in some edge cases, prevent an empty intermediate page from being deleted.New and Updated Features
Bug Fixes
Published by mDuo13 over 7 years ago
The rippled
team has released rippled
version 0.60.1, which corrects a technical flaw that resulted from using 32-bit space identifiers instead of the protocol-defined 16-bit values for Escrow and Payment Channel ledger entries. rippled
version 0.60.1 also fixes a problem where the WebSocket timeout timer would not be canceled when certain errors occurred during subscription streams. Ripple requires upgrading to rippled version 0.60.1 immediately.
Fix a flaw that resulted from using 32-bit space identifiers instead of the protocol-defined 16-bit values (#2071)
Fix a problem where the WebSocket timeout timer would not be cancelled when certain errors occurred during subscription streams (#2067)
Published by nbougalis over 7 years ago
Escrow
rippled
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.
Payment Channels
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.
The rippled
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.
fix1368 Amendment
rippled
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).
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.
Escrow
support (#2039)](https://github.com/ripple/rippled/pull/2039)SecretKey
comparison operator (#2004)
LEDGER_MIN_CONSENSUS
(#2013)
libsecp256k1
and Beast B30
(#1983)
Config
extensible via lambda (#1993)
lookupLedger
(#1989)
get_counts
RPC method (#2011)
transaction_entry
request (#2017)
sign
(#2010)
wss
work the same as wss2
(#2033)
Published by mDuo13 over 7 years ago
The rippled
0.50.0 release includes TickSize, which allows gateways to set a "tick size" for assets they issue to to help promote faster price discovery and deeper liquidity, as well as reduce transaction spam and ledger churn on RCL. Ripple expects TickSize to be enabled via an Amendment called TickSize on Tuesday, 2017-02-21. This feature underlines Ripple’s continued support to improving RCL and making it even better suited for settlement of global payments.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.
New and Updated Features
Problem & Solution
Currently, offers on RCL can differ by as little as one part in a quadrillion. This means that there is essentially no value to placing an offer early, as an offer placed later at a microscopically better price gets priority over it. The TickSize Amendment solves this problem by introducing a minimum tick size that a price must move for an offer to be considered to be at a better price. The tick size is controlled by the issuers of the assets involved.
When you place a buy offer, the amount of currency you will buy is respected. When you place a sell offer, the amount of currency you will sell is respected. If a tick size is in force, the other side of the offer will be rounded (in your favor) such that the ratio is rounded to the tick size before the offer is placed on the books.
TickSize does not affect the size of an offer. A trader can still trade microscopic amounts of an asset. It just affects the prices (ratio of in to out) at which offers can be placed on the books. For asset pairs with XRP, the tick size imposed, if any, is the tick size of the issuer of the non-XRP asset. For asset pairs without XRP, the tick size imposed, if any, is the smaller of the two issuer's configured tick sizes.
The tick size is imposed by rounding the offer quality down to the nearest tick and recomputing the non-critical side of the offer. For a buy, the amount offered is rounded down. For a sell, the amount charged is rounded up.
Effects of TickSize Change
This change lets issuers quantize the exchange rates of offers to use a specified number of significant digits. Gateways must enable a TickSize on their account for this feature to benefit them. A single AccountSet transaction may set a "TickSize" parameter. Legal values are 0 and 3-15 inclusive. Zero removes the setting. 3-15 allow that many decimal digits of precision in the pricing of offers for assets issued by this account. It will still be possible to place an offer to buy or sell any amount of an asset and the offer will still keep that amount as exactly as it does now. If an offer involves two assets that each have a tick size, the smaller number of significant figures (larger ticks) controls.
Benefits of TickSize Change
The primary expected benefits of the TickSize amendment is the reduction of bots fighting over the tip of the order book, which means:
We also expect larger tick sizes to benefit market makers in the following ways:
Hardened TLS configuration
This release updates the default TLS configuration for rippled
. The new release supports only 2048-bit DH parameters and defines a new default set of modern ciphers to use, removing support for ciphers and hash functions that are no longer considered secure.
Server administrators who wish to have different settings can configure custom global and per-port cipher suites in the configuration file using the ssl_ciphers directive.
Bug Fixes
Published by mDuo13 over 7 years ago
Ripple has released rippled
version 0.33.0-hf1, which fixes a JSON parsing issue in all rippled
servers. Ripple recommends upgrading to 0.33.0-hf1 only if server operators are experiencing a jsonInvalid
error response to client requests.
There are no new or updated features in the 0.33.0-hf1 release.
Bug Fixes
Published by mDuo13 over 7 years ago
The rippled
team has released version 0.40.1, which increases SQLite database limits in all rippled
full-history servers. Ripple recommends upgrading to 0.40.1 only if server operators are running rippled
servers with full-history of the ledger.
There are no new or updated features in the 0.40.1 release.
Bug Fixes
Published by mDuo13 over 7 years ago
The rippled
0.40.0 release includes Suspended Payments, a new transaction type on the Ripple network that functions similar to an escrow service, which permits users to lock XRP until a cryptographic condition is met or it expires. Ripple expects Suspended Payments to be enabled via an Amendment named “SusPay” on Tuesday, 2017-01-17 a later date.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.
New and Updated Features
Previously, Ripple announced the introduction of Payment Channels during the release of rippled version 0.33.0, which permit scalable, off-ledger checkpoints of high volume, low value payments flowing in a single direction. This was the first step in a multi-phase effort to make RCL more scalable and to support Interledger Protocol (ILP). Ripple expects Payment Channels to be enabled via an Amendment called PayChan on a future date to be determined.
In the second phase towards making RCL more scalable and compatible with ILP, Ripple is introducing Suspended Payments, a new transaction type on the Ripple network that functions similar to an escrow service, which permits users to cryptographically escrow XRP on RCL with an expiration date. Ripple expects Suspended Payments to be enabled via an Amendment named “SusPay” on Tuesday, 2017-01-17 a later date.
A Suspended Payment can be created, which deducts the funds from the sending account. It can then be either fulfilled or canceled. It can only be fulfilled if the fulfillment transaction makes it into a ledger with a CloseTime lower than the expiry date of the transaction. It can be canceled with a transaction that makes it into a ledger with a CloseTime greater than the expiry date of the transaction.
In the third phase towards making RCL more scalable and compatible with ILP, Ripple plans to introduce additional library support for crypto-conditions, which are distributable event descriptions written in a standard format that describe how to recognize a fulfillment message without saying exactly what the fulfillment is. Fulfillments are cryptographically verifiable messages that prove an event occurred. If you transmit a fulfillment, then everyone who has the condition can agree that the condition has been met. Fulfillment requires the submission of a signature that matches the condition (message hash and public key). This format supports multiple algorithms, including different hash functions and cryptographic signing schemes. Crypto-conditions can be nested in multiple levels, with each level possibly having multiple signatures.
Lastly, 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. This will require brief scheduled allowable downtime while the changes to the hash tree structure are propagated by the network. We will keep the community updated as we progress towards this date (TBA).
Bug Fixes
Published by mDuo13 about 8 years ago
The rippled
0.33.0 release includes an improved version of the payment code, which we expect to be activated via Amendment on Wednesday, 2016-10-20 with the name Flow. We are also introducing XRP Payment Channels, a new structure in the ledger designed to support Interledger Protocol trust lines as balances get substantial, which we expect to be activated via Amendment on a future date (TBA) with the name PayChan. Lastly, we will be introducing changes to the hash tree structure that rippled uses to represent a ledger, which we expect to be available via Amendment on a future date (TBA) with the name SHAMapV2.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.
New and Updated Features
A fixed version of the new payment processing engine, which we initially announced on Friday, 2016-07-29, is expected to be available via Amendment on Wednesday, 2016-10-20 with the name Flow. The new payments code adds no new features, but improves efficiency and robustness in payment handling.
The Flow code may occasionally produce slightly different results than the old payment processing engine due to the effects of floating point rounding.
We will be introducing changes to the hash tree structure that rippled uses to represent a ledger, which we expect to be activated via Amendment on a future date (TBA) with the name SHAMapV2. The new structure is more compact and efficient than the previous version. This affects how ledger hashes are calculated, but has no other user-facing consequences. The activation of the SHAMapV2 amendment will require brief scheduled allowable downtime, while the changes to the hash tree structure are propagated by the network. We will keep the community updated as we progress towards this date (TBA).
In an effort to make RCL more scalable and to support Interledger Protocol (ILP) trust lines as balances get more substantial, we’re introducing XRP Payment Channels, a new structure in the ledger, which we expect to be available via Amendment on a future date (TBA) with the name PayChan.
XRP Payment Channels permit scalable, intermittent, off-ledger settlement of ILP trust lines for high volume payments flowing in a single direction. For bidirectional channels, an XRP Payment Channel can be used in each direction. The recipient can claim any unpaid balance at any time. The owner can top off the channel as needed. The owner 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.
The initial concept behind payment channels was discussed as early as 2011 and the first implementation was done by Mike Hearn in bitcoinj. Recent work being done by Lightning Network has showcased examples of the many use cases for payment channels. The introduction of XRP Payment Channels allows for a more efficient integration between RCL and ILP to further support enterprise use cases for high volume payments.
Added getInfoRippled.sh
support script to gather health check for rippled servers [RIPD-1284]
The account_info
command can now return information about queued transactions - [RIPD-1205]
Automatically-provided sequence numbers now consider the transaction queue - [RIPD-1206]
The server_info
and server_state
commands now include the queue-related escalated fee factor in the load_factor field of the response - [RIPD-1207]
A transaction with a high transaction cost can now cause transactions from the same sender queued in front of it to get into the open ledger if the transaction costs are high enough on average across all such transactions. - [RIPD-1246]
Reorganization: Move LoadFeeTrack
to app/tx and clean up functions - [RIPD-956]
Reorganization: unit test source files - [RIPD-1132]
Reorganization: NuDB stand-alone repository - [RIPD-1163]
Reorganization: Add BEAST_EXPECT
to Beast - [RIPD-1243]
Reorganization: Beast 64-bit CMake/Bjam target on Windows - [RIPD-1262]
Bug Fixes
PaymentSandbox::balanceHook
can return the wrong issuer, which could cause the transfer fee to be incorrectly by-passed in rare circumstances. [RIPD-1274, #1827]
Prevent concurrent write operations in websockets [#1806]
Add HTTP status page for new websocket implementation [#1855]
Published by mDuo13 about 8 years ago
The rippled
0.32.1 release includes an improved version of the payment code, which we expect to be available via Amendment on Wednesday, 2016-08-24 with the name FlowV2, and a completely new implementation of the WebSocket protocol for serving clients.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.
New and Updated Features
An improved version of the payment processing engine with the name “FlowV2”. The new payments code adds no new features, but improves efficiency and robustness in payment handling. (Update: During the voting process, a critical bug was found in FlowV2, and trusted validators vetoed the amendment. The amendment will be replaced in the next version of rippled
.)
The FlowV2 code may occasionally produce slightly different results than the old payment processing engine due to the effects of floating point rounding.
Beast WebSocket
A completely new implementation of the WebSocket protocol for serving clients is available as a configurable option for rippled
administrators. To enable this new implementation, change the “protocol” field in rippled.cfg
from “ws” to “ws2” (or from “wss” to “wss2” for Secure WebSockets), as illustrated in this example:
[port_ws_public]
port = 5006
ip = 0.0.0.0
protocol = wss2
The new implementation paves the way for increased reliability and future performance when submitting commands over WebSocket. The behavior and syntax of commands should be identical to the previous implementation. Please report any issues to [email protected]. A future version of rippled
will remove the old WebSocket implementation, and use only the new one.
Bug fixes
x-queue-okay
parameter will use the user’s maximum fee if the open ledger fee is higher, improving queue position, and giving the tx more chance to succeed. (RIPD-1194)Published by mDuo13 about 8 years ago
The rippled
0.32.1 release includes an improved version of the payment code, which we expect to be available via Amendment on Wednesday, 2016-08-24 with the name FlowV2, and a completely new implementation of the WebSocket protocol for serving clients.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.
New and Updated Features
An improved version of the payment processing engine, which we expect to be available via Amendment on Wednesday, 2016-08-24 with the name “FlowV2”. The new payments code adds no new features, but improves efficiency and robustness in payment handling.
The FlowV2 code may occasionally produce slightly different results than the old payment processing engine due to the effects of floating point rounding. Once FlowV2 is enabled on the network then old servers without the FlowV2 amendment will lose sync more frequently because of these differences.
Beast WebSocket
A completely new implementation of the WebSocket protocol for serving clients is available as a configurable option for rippled
administrators. To enable this new implementation, change the “protocol” field in rippled.cfg
from “ws” to “ws2” (or from “wss” to “wss2” for Secure WebSockets), as illustrated in this example:
[port_ws_public]
port = 5006
ip = 0.0.0.0
protocol = wss2
The new implementation paves the way for increased reliability and future performance when submitting commands over WebSocket. The behavior and syntax of commands should be identical to the previous implementation. Please report any issues to [email protected]. A future version of rippled will remove the old WebSocket implementation, and use only the new one.
Bug fixes
Fix a non-exploitable, intermittent crash in some client pathfinding requests (RIPD-1219)
Fix a non-exploitable crash caused by a race condition in the HTTP server. (RIPD-1251)
Fix bug that could cause a previously fee queued transaction to not be relayed after being in the open ledger for an extended time without being included in a validated ledger. Fix bug that would allow an account to have more than the allowed limit of transactions in the fee queue. Fix bug that could crash debug builds in rare cases when replacing a dropped transaction. (RIPD-1200)
Remove incompatible OS X switches in Test.py (RIPD-1250)
Autofilling a transaction fee (sign / submit) with the experimental x-queue-okay
parameter will use the user’s maximum fee if the open ledger fee is higher, improving queue position, and giving the tx more chance to succeed. (RIPD-1194)
Published by mDuo13 over 8 years ago
The rippled
0.32.0 release improves transaction queue which now supports batching and can hold up to 10 transactions per account, allowing users to queue multiple transactions for processing when the network load is high. Additionally, the server_info
and server_state
commands now include information on transaction cost multipliers and the fee command is available to unprivileged users. We advise rippled operators to upgrade immediately.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.
New and Updated Features
telCAN_NOT_QUEUE
.[port_wss_admin]
and [port_ws_public]
stanzas: [port_wss_admin]
port = 51237
ip = 127.0.0.1
admin = 127.0.0.1
protocol = wss2
[port_ws_public]
port = 51233
ip = 0.0.0.0
protocol = wss2, ws2
Bug fixes
Deprecated features