This document contains the release notes for rippled, the reference server implementation of the XRP Ledger protocol. To learn more about how to build, run or update a rippled server, visit https://xrpl.org/install-rippled.html
Have new ideas? Need help with setting up your node? Please open an issue here.
Version 2.0.0 of rippled, the reference server implementation of the XRP Ledger protocol, is now available. This release adds new features and bug fixes, and introduces these amendments:
DIDXChainBridgefixDisallowIncomingV1fixFillOrKillSign Up for Future Release Announcements
+Four new amendments are now open for voting according to the XRP Ledger's amendment process, which enables protocol changes following two weeks of >80% support from trusted validators.
+If you operate an XRP Ledger server, upgrade to version 2.0.0 by January 22, 2024 to ensure service continuity. The exact time that protocol changes take effect depends on the voting decisions of the decentralized network.
+(These are changes which may impact or be useful to end users. For example, you may be able to update your code/workflow to take advantage of these changes.)
+lsfDisallowIncomingTrustline flag is enabled on their account. #4721flowCross amendment. The tfFillOrKill and tfSell flags are now properly handled to allow offers to cross in certain scenarios. #4694check field is a string. #4630account_tx and noripple_check fields. #4620gateway_balances and channel_authorize requests. #4618DeliverMax alias to Amount and removed Amount. #4733tx_history and ledger_header methods. Also updated RPC::Handler to allow for version-specific methods. #4759rippled and unit tests at v1. #4803ledger_index to return as a number. #4820server_definitions command that returns an SDK-compatible definitions.json file, generated from the rippled instance currently running. #4703rippled-example.cfg file. #4753tecHOOK_ERROR to tecHOOK_REJECTED. #4559(These are behind-the-scenes improvements, such as internal changes to the code, which are not expected to impact end users.)
+TxFormats common fields logic. #4637LedgerHistory::fixIndex. #4574secp256k1 to 0.3.2. #4653commonFields again. #4715applySteps.cpp. When a new transactor is added, only one function needs to be modified now. #4710PeerFinder::Logic with LogicError to better indicate the nature of server crashes. #4562rippled-example.cfg docs to clarify usage of ssl_cert vs ssl_chain. #4667BUILD.md:
+API-CHANGELOG.md:rippled 2.0.0. #4633signer_lists field in the account_info response for API v2. #4724DeliverMax field. #4784RippledRelease.cmake that prevented targets from being created during packaging. #4707.build to .gitignore. #4722uint is not universally defined Windows build error. #4731conan.md. #4740python call to fix the pip upgrade command in Windows CI. #4768pull_request_template.md. #4757FeeEscalation.md. #4729unused-but-set-variable warning. #4677rippled smoke tests run on. #4813bookworm to the distribution matrix during Artifactory uploads, enabling Debian 12 clients to install rippled packages. #4836AMMCreate.h. 4821The public source code repository for rippled is hosted on GitHub at https://github.com/XRPLF/rippled.
We welcome all contributions and invite everyone to join the community of XRP Ledger developers to help build the Internet of Value.
+The following people contributed directly to this release:
+Bug Bounties and Responsible Disclosures:
+We welcome reviews of the rippled code and urge researchers to responsibly disclose any issues they may find.
+To report a bug, please send a detailed report to: bugs@xrpl.org
+Version 1.12.0 of rippled, the reference server implementation of the XRP Ledger protocol, is now available. This release adds new features and bug fixes, and introduces these amendments:
Sign Up for Future Release Announcements
-Three new amendments are now open for voting according to the XRP Ledger's amendment process, which enables protocol changes following two weeks of >80% support from trusted validators.
If you operate an XRP Ledger server, upgrade to version 1.12.0 by September 20, 2023 to ensure service continuity. The exact time that protocol changes take effect depends on the voting decisions of the decentralized network.
-On supported platforms, see the instructions on installing or updating rippled.
The XRPL Foundation publishes portable binaries, which are drop-in replacements for the rippled daemon. See information and downloads for the portable binaries. This will work on most distributions, including Ubuntu 16.04, 18.04, 20.04, and 22.04; CentOS; and others. Please test and open issues on GitHub if there are problems.
(These are changes which may impact or be useful to end users. For example, you may be able to update your code/workflow to take advantage of these changes.)
server_info responses. #4427accepted, seqNum, hash, and totalCoins fields from the ledger method. #4244(These are behind-the-scenes improvements, such as internal changes to the code, which are not expected to impact end users.)
std::from_chars for better maintainability. #4473TypedField move constructor. #4567The public source code repository for rippled is hosted on GitHub at https://github.com/XRPLF/rippled.
We welcome all contributions and invite everyone to join the community of XRP Ledger developers to help build the Internet of Value.
-The following people contributed directly to this release:
Bug Bounties and Responsible Disclosures:
We welcome reviews of the rippled code and urge researchers to responsibly disclose any issues they may find.
To report a bug, please send a detailed report to: bugs@xrpl.org
-Version 1.11.0 of rippled, the reference server implementation of the XRP Ledger protocol, is now available.
This release reduces memory usage, introduces the fixNFTokenRemint amendment, and adds new features and bug fixes. For example, the new NetworkID field in transactions helps to prevent replay attacks with side-chains.
Sign Up for Future Release Announcements
-The fixNFTokenRemint amendment is now open for voting according to the XRP Ledger's amendment process, which enables protocol changes following two weeks of >80% support from trusted validators.
If you operate an XRP Ledger server, upgrade to version 1.11.0 by July 5 to ensure service continuity. The exact time that protocol changes take effect depends on the voting decisions of the decentralized network.
-On supported platforms, see the instructions on installing or updating rippled.
nftoken_id, nftoken_ids and offer_id meta fields into NFT Tx responses by @shawnxie999 in https://github.com/XRPLF/rippled/pull/4447Full Changelog: https://github.com/XRPLF/rippled/compare/1.10.1...1.11.0
-The public source code repository for rippled is hosted on GitHub at https://github.com/XRPLF/rippled.
We welcome all contributions and invite everyone to join the community of XRP Ledger developers to help build the Internet of Value.
-The following people contributed directly to this release:
Bug Bounties and Responsible Disclosures: We welcome reviews of the rippled code and urge researchers to responsibly disclose any issues they may find.
To report a bug, please send a detailed report to:
bugs@xrpl.org -
Version 1.10.1 of rippled, the reference server implementation of the XRP Ledger protocol, is now available. This release restores packages for Ubuntu 18.04.
Compared to version 1.10.0, the only C++ code change fixes an edge case in Reporting Mode.
If you are already running version 1.10.0, then upgrading to version 1.10.1 is generally not required.
Sign Up for Future Release Announcements
-On supported platforms, see the instructions on installing or updating rippled.
da18c86cbf Build packages with Ubuntu 18.04f7b3ddd87b Reporting Mode: Do not attempt to acquire missing data from peer network (#4458)The public source code repository for rippled is hosted on GitHub at https://github.com/XRPLF/rippled.
We welcome all contributions and invite everyone to join the community of XRP Ledger developers to help build the Internet of Value.
-The following people contributed directly to this release:
Bug Bounties and Responsible Disclosures: We welcome reviews of the rippled code and urge researchers to responsibly disclose any issues they may find.
To report a bug, please send a detailed report to:
bugs@xrpl.org -
Version 1.10.0 of rippled, the reference server implementation of the XRP Ledger protocol, is now available. This release introduces six new amendments, detailed below, and cleans up code to improve performance.
Sign Up for Future Release Announcements
-Six new amendments are now open for voting according to the XRP Ledger's amendment process, which enables protocol changes following two weeks of >80% support from trusted validators.
If you operate an XRP Ledger server, upgrade to version 1.10.0 by March 21 to ensure service continuity. The exact time that protocol changes take effect depends on the voting decisions of the decentralized network.
-On supported platforms, see the instructions on installing or updating rippled.
featureImmediateOfferKilled**: Changes the response code of an OfferCreate transaction with the tfImmediateOrCancel flag to return tecKILLED when no funds are moved. The previous return code of tecSUCCESS was unintuitive. #4157fixTrustLinesToSelf**: Trust lines must be between two different accounts, but two exceptions exist because of a bug that briefly existed. This amendment removes those trust lines. 69bb2berippled now uses hex encoding for the Closed-Ledger and Previous-Ledger fields in the Handshake. Also added --newnodeid and --nodeid command line options. 5a15229manifest and validator_info to the rippled CLI usage statement. b88ed5apreclaim function to check for 0 in NFTokenSellOffer and NFTokenBuyOffer before calling Ledger::read. This issue only affected debug builds. #4351shared_ptr copies by accepting a value in SHAMapInnerNode::setChild: #4266The public source code repository for rippled is hosted on GitHub at https://github.com/XRPLF/rippled.
We welcome all contributions and invite everyone to join the community of XRP Ledger developers to help build the Internet of Value.
-The following people contributed directly to this release:
Bug Bounties and Responsible Disclosures: We welcome reviews of the rippled code and urge researchers to responsibly disclose any issues they may find.
To report a bug, please send a detailed report to:
bugs@xrpl.org -
Version 1.9.4 of rippled, the reference implementation of the XRP Ledger protocol is now available. This release introduces an amendment that removes the ability for an NFT issuer to indicate that trust lines should be automatically created for royalty payments from secondary sales of NFTs, in response to a bug report that indicated how this functionality could be abused to mount a denial of service attack against the issuer.
This release introduces a new amendment to the XRP Ledger protocol, **fixRemoveNFTokenAutoTrustLine** to mitigate a potential denial-of-service attack against NFT issuers that minted NFTs and allowed secondary trading of those NFTs to create trust lines for any asset.
This amendment is open for voting according to the XRP Ledger's amendment process, which enables protocol changes following two weeks of >80% support from trusted validators.
If you operate an XRP Ledger server, then you should upgrade to version 1.9.4 within two weeks, to ensure service continuity. The exact time that protocol changes take effect depends on the voting decisions of the decentralized network.
For more information about NFTs on the XRP Ledger, see NFT Conceptual Overview.
-On supported platforms, see the instructions on installing or updating rippled.
The primary change in this release is the following bug fix:
fixRemoveNFTokenAutoTrustLine amendment, which disables the tfTrustLine flag, which a malicious attacker could exploit to mount denial-of-service attacks against NFT issuers that specified the flag on their NFTs. (#4301)The public source code repository for rippled is hosted on GitHub at https://github.com/XRPLF/rippled.
We welcome all contributions and invite everyone to join the community of XRP Ledger developers and help us build the Internet of Value.
-The following people contributed directly to this release:
Version 1.9.3 of rippled, the reference server implementation of the XRP Ledger protocol is now available. This release corrects minor technical flaws with the code that loads configured amendment votes after a startup and the copy constructor of PublicKey.
On supported platforms, see the instructions on installing or updating rippled.
This release contains the following bug fixes:
PublicKey copy assignment operator mishandled the case where a PublicKey would be assigned to itself, and could result in undefined behavior.The public source code repository for rippled is hosted on GitHub at https://github.com/XRPLF/rippled.
We welcome contributions, big and small, and invite everyone to join the community of XRP Ledger developers and help us build the Internet of Value.
-The following people contributed directly to this release:
Version 1.9.2 of rippled, the reference server implementation of the XRP Ledger protocol, is now available. This release includes several fixes and improvements, including a second new fix amendment to correct a bug in Non-Fungible Tokens (NFTs) code, a new API method for order book changes, less noisy logging, and other small fixes.
This release introduces a two new amendments to the XRP Ledger protocol. The first, fixNFTokenNegOffer, fixes a bug in code associated with the NonFungibleTokensV1 amendment, originally introduced in version 1.9.0. The second, NonFungibleTokensV1_1, is a "roll-up" amendment that enables the NonFungibleTokensV1 feature plus the two fix amendments associated with it, fixNFTokenDirV1 and fixNFTokenNegOffer.
If you want to enable NFT code on the XRP Ledger Mainnet, you can vote in favor of only the NonFungibleTokensV1_1 amendment to support enabling the feature and fixes together, without risk that the unfixed NFT code may become enabled first.
These amendments are now open for voting according to the XRP Ledger's amendment process, which enables protocol changes following two weeks of >80% support from trusted validators.
If you operate an XRP Ledger server, then you should upgrade to version 1.9.2 within two weeks, to ensure service continuity. The exact time that protocol changes take effect depends on the voting decisions of the decentralized network.
For more information about NFTs on the XRP Ledger, see NFT Conceptual Overview.
-On supported platforms, see the instructions on installing or updating rippled.
This release contains the following features and improvements.
The public source code repository for rippled is hosted on GitHub at https://github.com/XRPLF/rippled.
We welcome contributions, big and small, and invite everyone to join the community of XRP Ledger developers and help us build the Internet of Value.
-The following people contributed directly to this release:
For a real-time view of all lifetime contributors, including links to the commits made by each, please visit the "Contributors" section of the GitHub repository: https://github.com/XRPLF/rippled/graphs/contributors.
-Version 1.9.1 of rippled, the reference server implementation of the XRP Ledger protocol, is now available. This release includes several important fixes, including a fix for a syncing issue from 1.9.0, a new fix amendment to correct a bug in the new Non-Fungible Tokens (NFTs) code, and a new amendment to allow multi-signing by up to 32 signers.
This release introduces two new amendments to the XRP Ledger protocol. These amendments are now open for voting according to the XRP Ledger's amendment process, which enables protocol changes following two weeks of >80% support from trusted validators.
If you operate an XRP Ledger server, then you should upgrade to version 1.9.1 within two weeks, to ensure service continuity. The exact time that protocol changes take effect depends on the voting decisions of the decentralized network.
The fixNFTokenDirV1 amendment fixes a bug in code associated with the NonFungibleTokensV1 amendment, so the fixNFTokenDirV1 amendment should be enabled first. All validator operators are encouraged to configure amendment voting to oppose the NonFungibleTokensV1 amendment until after the fixNFTokenDirV1 amendment has become enabled. For more information about NFTs on the XRP Ledger, see NFT Conceptual Overview.
The ExpandedSignerList amendment extends the ledger's built-in multi-signing functionality so that each list can contain up to 32 entries instead of the current limit of 8. Additionally, this amendment allows each signer to have an arbitrary 256-bit data field associated with it. This data can be used to identify the signer or provide other metadata that is useful for organizations, smart contracts, or other purposes.
-On supported platforms, see the instructions on installing or updating rippled.
This release contains the following features and improvements.
-NFTokenPage an NFToken object belongs on. It also adjusts the constraints of NFTokenPage invariant checks, so that certain error cases fail with a suitable error code such as tecNO_SUITABLE_TOKEN_PAGE instead of failing with a tecINVARIANT_FAILED error code. (#4155)WalletLocator field containing arbitrary data. (#4097)DatabaseDownloader code and adjusts unit tests so that the code does not return spurious failures, and more data is logged if it does fail. (#4021)The public source code repository for rippled is hosted on GitHub at https://github.com/ripple/rippled.
We welcome contributions, big and small, and invite everyone to join the community of XRP Ledger developers and help us build the Internet of Value.
-The following people contributed directly to this release:
For a real-time view of all lifetime contributors, including links to the commits made by each, please visit the "Contributors" section of the GitHub repository: https://github.com/ripple/rippled/graphs/contributors.
We welcome external contributions and are excited to see the broader XRP Ledger community continue to grow and thrive.
-signer_lists in the root of the account_info response, no longer nested under account_data.This is the 1.9.0 release of rippled, the reference implementation of the XRP Ledger protocol. This release brings several features and improvements.
AcceptedLedger and AcceptedLedgerTx classes, reduces their memory footprint, and reduces unnecessary dynamic memory allocations. 8f5868This release includes name changes in the NFToken API for SFields, RPC return labels, and error codes for clarity and consistency. To refactor your code, migrate the names of these items to the new names as listed below.
-TokenTaxon -> NFTokenTaxonSellOffer -> NFTokenSellOfferOfferNode -> NFTokenOfferNodetokenid -> nft_idindex -> nft_offer_indextemBAD_TRANSFER_FEE -> temBAD_NFTOKEN_TRANSFER_FEEtecOFFER_TYPE_MISMATCH -> tecNFTOKEN_OFFER_TYPE_MISMATCHtecCANT_ACCEPT_OWN_OFFER -> tecCANT_ACCEPT_OWN_NFTOKEN_OFFERThis is the 1.8.5 release of rippled, the reference implementation of the XRP Ledger protocol. This release includes fixes and updates for stability and security, and improvements to build scripts. There are no user-facing API or protocol changes in this release.
This release contains the following bug fixes and under-the-hood improvements:
This is the 1.8.4 release of rippled, the reference implementation of the XRP Ledger protocol.
This release corrects a technical flaw introduced with 1.8.3 that may result in failures if the newly-introduced 'fast loading' is enabled. The release also adjusts default parameters used to configure the pathfinding engine to reduce resource usage.
-walkMapParallel: This commit corrects a technical flaw introduced with commit [7c12f0135897361398917ad2c8cda888249d42ae] that would result in undefined behavior if the server operator configured their server to use the 'fast loading' mechanism introduced with 1.8.3.This is the 1.8.3 release of rippled, the reference implementation of the XRP Ledger protocol.
This release implements changes that improve the syncing performance of peers on the network, adds countermeasures to several routines involving LZ4 to defend against CVE-2021-3520, corrects a minor technical flaw that would result in the server not using a cache for nodestore operations, and adjusts tunable values to optimize disk I/O.
-Recently, servers in the XRP Ledger network have been taking an increasingly long time to sync back to the network after restartiningg. This is one of several releases which will be made to improve on this issue.
-Parallel ledger loader & I/O performance improvements: This commit makes several changes that, together, should decrease the time needed for a server to sync to the network. To make full use of this change, rippled needs to be using storage with high IOPS and operators need to explicitly enable this behavior by adding the following to their config file, under the [node_db] stanza:
SHAMap nodes.Ripple has released version 1.8.2 of rippled, the reference server implementation of the XRP Ledger protocol. This release addresses the full transaction queues and elevated transaction fees issue observed on the XRP ledger, and also provides some optimizations and small fixes to improve the server's performance overall.
-Recently, servers in the XRP Ledger network have had full transaction queues and transactions paying low fees have mostly not been able to be confirmed through the queue. After investigation, it was discovered that a large influx of transactions to the network caused it to raise the transaction costs to be proposed in the next ledger block, and defer transactions paying lower costs to later ledgers. The first part worked as designed, but deferred transactions were not being confirmed as the ledger had capacity to process them.
The root cause was that there were very many low-cost transactions that different servers in the network received in a different order due to incidental differences in timing or network topology, which caused validators to propose different sets of low-cost transactions from the queue. Since none of these transactions had support from a majority of validators, they were removed from the proposed transaction set. Normally, any transactions removed from a proposed transaction set are supposed to be retried in the next ledger, but servers attempted to put these deferred transactions into their transaction queues first, which had filled up. As a result, the deferred transactions were discarded, and the network was only able to confirm transactions that paid high costs.
-Ripple has released version 1.8.0 of rippled, the reference server implementation of the XRP Ledger protocol. This release brings several features and improvements.
-validations stream: The validations subscription stream in the API now reports additional fields that were added to validation messages by the HardenedValidations amendment. These fields make it easier to detect misconfigurations such as multiple servers sharing a validation key pair. (#3865)validations and manifests streams: In the API it is now possible to connect to these streams when connected to a servers running in reporting. Previously, attempting to subscribe to these streams on a reporting server failed with the error reportingUnsupported. (#3905)Slice. The internal buffer is switched from std::vector to Buffer to save a minimum of 8 bytes (plus the buffer slack that is inherent in std::vector) per SHAMapItem instance.std::thread. The immediate benefits are less code, less synchronization, less runtime work, and (subjectively) more readable code. The end goal is to adhere to RAII in our object design, and this is one necessary step on that path.This is the 1.7.3 release of rippled, the reference implementation of the XRP Ledger protocol. This release addresses an OOB memory read identified by Guido Vranken, as well as an unrelated issue identified by the Ripple C++ team that could result in incorrect use of SLEs. Additionally, this version also introduces the NegativeUNL amendment, which corresponds to the feature which was introduced with the 1.6.0 release.
If you operate an XRP Ledger server, then you should upgrade to version 1.7.3 at your earliest convenience to mitigate the issues addressed in this hotfix. If a sufficient majority of servers on the network upgrade, the NegativeUNL amendment may gain a majority, at which point a two week activation countdown will begin. If the NegativeUNL amendment activates, servers running versions of rippled prior to 1.7.3 will become amendment blocked.
NegativeUNL as a supported amendment: Introduces an amendment for the Negative UNL feature introduced in rippled 1.6.0.This the 1.7.2 release of rippled, the reference server implementation of the XRP Ledger protocol. This release protects against the security issue CVE-2021-3499 affecting OpenSSL, adds an amendment to fix an issue with small offers not being properly removed from order books in some cases, and includes various other minor fixes. Version 1.7.2 supersedes version 1.7.1 and adds fixes for more issues that were discovered during the release cycle.
-This release introduces a new amendment to the XRP Ledger protocol: fixRmSmallIncreasedQOffers. This amendments is now open for voting according to the XRP Ledger's amendment process, which enables protocol changes following two weeks of >80% support from trusted validators. If you operate an XRP Ledger server, then you should upgrade to version 1.7.2 within two weeks, to ensure service continuity. The exact time that protocol changes take effect depends on the voting decisions of the decentralized network. If you operate an XRP Ledger validator, please learn more about this amendment so you can make informed decisions about how your validator votes. If you take no action, your validator begins voting in favor of any new amendments as soon as it has been upgraded.
Ripple has released version 1.7.0 of rippled, the reference server implementation of the XRP Ledger protocol. This release significantly improves memory usage, introduces a protocol amendment to allow out-of-order transaction execution with Tickets, and brings several other features and improvements.
If you use the precompiled binaries of rippled that Ripple publishes for supported platforms, please note that Ripple has renewed the GPG key used to sign these packages. If you are upgrading from a previous install, you must download and trust the renewed key. Automatic upgrades will not work until you have re-trusted the key.
-Perform a manual upgrade. When prompted, confirm that the key's fingerprint matches the following example, then press y to accept the updated key:
Download and trust the updated public key, then perform a manual upgrade as follows:
This release introduces several new features including changes to the XRP Ledger's consensus mechanism to make it even more robust in adverse conditions, as well as numerous bug fixes and optimizations.
-ledger_cleaner command to rippled command line help [#3305]The rippled 1.5.0 release introduces several improvements and new features, including support for gRPC API, API versioning, UNL propagation via the peer network, new RPC methods validator_info and manifest, augmented submit method, improved tx method response, improved command line parsing, improved handshake protocol, improved package building and various other minor bug fixes and improvements.
This release also introduces two new amendments: fixQualityUpperBound and RequireFullyCanonicalSig.
Beast code. 172ead8226529d3e6fThe rippled 1.4.0 release introduces several improvements and new features, including support for deleting accounts, improved peer slot management, improved CI integration and package building and support for C++17 and Boost 1.71. Finally, this release removes the code for the SHAMapV2 amendment which failed to gain majority support and has been obsoleted by other improvements.
New and Updated Features
server_state when a server detects a disagreement between itself and the network.channel_authorize command.The rippled 1.3.1 release improves the built-in deadlock detection code, improves logging during process startup, changes the package build pipeline and improves the build documentation.
New and Updated Features
@@ -918,7 +1059,7 @@The rippled 1.3.0 release introduces several new features and overall improvements to the codebase, including the fixMasterKeyAsRegularKey amendment, code to adjust the timing of the consensus process and support for decentralized validator domain verification. The release also includes miscellaneous improvements including in the transaction censorship detection code, transaction validation code, manifest parsing code, configuration file parsing code, log file rotation code, and in the build, continuous integration, testing and package building pipelines.
New and Updated Features
The rippled 1.2.4 release improves the way that shard crawl requests are routed and the robustness of configured validator list retrieval by imposing a 20 second timeout.
New and Updated Features
@@ -940,7 +1081,7 @@The rippled 1.2.3 release corrects a technical flaw which in some circumstances can cause a null pointer dereference that can crash the server.
New and Updated Features
@@ -949,7 +1090,7 @@The rippled 1.2.2 release corrects a technical flaw in the fee escalation engine which could cause some fee metrics to be calculated incorrectly. In some circumstances this can potentially cause the server to crash.
New and Updated Features
@@ -958,7 +1099,7 @@The rippled 1.2.1 release introduces several fixes including a change in the information reported via the enhanced crawl functionality introduced in the 1.2.0 release, a fix for a potential race condition when processing a status change message for a peer, and for a technical flaw that could cause a server to not properly detect that it had lost all its peers.
The release also adds the delivered_amount field to more responses to simplify the handling of payment or check cashing transactions.
delivered_amount to more RPC commands (f2756914)The rippled 1.2.0 release introduces the MultisignReserve Amendment, which reduces the reserve requirement associated with signer lists. This release also includes incremental improvements to the code that handles offers. Furthermore, rippled now also has the ability to automatically detect transaction censorship attempts and issue warnings of increasing severity for transactions that should have been included in a closed ledger after several rounds of consensus.
New and Updated Features
@@ -999,7 +1140,7 @@The rippled 1.1.2 release introduces a fix for an issue that could have prevented cluster peers from successfully bypassing connection limits when connecting to other servers on the same cluster. Additionally, it improves logic used to determine what the preferred ledger is during suboptimal network conditions.
New and Updated Features
@@ -1009,7 +1150,7 @@The rippled 1.1.1 release adds support for redirections when retrieving validator lists and changes the way that validators with an expired list behave. Additionally, informational commands return more useful information to allow server operators to determine the state of their server
New and Updated Features
@@ -1021,7 +1162,7 @@The rippled 1.1.0 release release includes the DepositPreAuth amendment, which combined with the previously released DepositAuth amendment, allows users to pre-authorize incoming transactions to accounts, by whitelisting sender addresses. The 1.1.0 release also includes incremental improvements to several previously released features (fix1515 amendment), deprecates support for the sign and sign_for commands from the rippled API and improves invariant checking for enhanced security.
Ripple recommends that all server operators upgrade to XRP Ledger version 1.1.0 by Thursday, 2018-09-27, to ensure service continuity.
@@ -1057,7 +1198,7 @@The rippled 1.0.0 release includes incremental improvements to several previously released features.
New and Updated Features
@@ -1071,7 +1212,7 @@check, escrow, and pay_chan to ledger_entry (RIPD-1600)The rippled 0.90.1 release includes fixes for issues reported by external security researchers. These issues, when exploited, could cause a rippled instance to restart or, in some circumstances, stop executing. While these issues can result in a denial of service attack, none affect the integrity of the XRP Ledger and no user funds, including XRP, are at risk.
New and Updated Features
@@ -1087,7 +1228,7 @@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:
@@ -1130,7 +1271,7 @@The rippled 0.81.0 release introduces changes that improve the scalability of the XRP Ledger and transitions the recommended validator configuration to a new hosted site, as described in Ripple's Decentralization Strategy Update post.
New and Updated Features
@@ -1141,7 +1282,7 @@The rippled 0.80.2 release introduces changes that improve the scalability of the XRP Ledger.
New and Updated Features
@@ -1152,7 +1293,7 @@The rippled 0.80.1 release provides several enhancements in support of published validator lists and corrects several bugs.
New and Updated Features
@@ -1169,7 +1310,7 @@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:
@@ -1197,7 +1338,7 @@setAmendmentBlocked is only called when processing the EnableAmendment transaction for the amendment (#2137)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
@@ -1206,7 +1347,7 @@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
@@ -1217,7 +1358,7 @@The rippled 0.70.0 release introduces several enhancements that improve the reliability, scalability and security of the network.
Highlights of this release include:
@@ -1253,28 +1394,28 @@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)
-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)
The rippled 0.60.1 release 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 cancelled when certain errors occurred during subscription streams. Ripple requires upgrading to rippled version 0.60.1 immediately.
New and Updated Feature
This release has no new features.
Bug Fixes
Correct calculation of Escrow and Payment Channel indices. Fix WebSocket timeout timer issues.
-The rippled 0.60.0 release introduces several enhancements that improve the reliability and scalability of the Ripple Consensus Ledger (RCL), including features that add ledger interoperability by improving Interledger Protocol compatibility. 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:
@@ -1316,21 +1457,21 @@The rippled 0.50.3 release corrects a reported exploit that would allow a combination of trust lines and order books in a payment path to bypass the blocking effect of the NoRipple flag. Ripple recommends that all server operators immediately upgrade to version 0.50.3.
New and Updated Features
This release has no new features.
Bug Fixes
Correct a reported exploit that would allow a combination of trust lines and order books in a payment path to bypass the blocking effect of the “NoRipple” flag.
-The rippled 0.50.2 release adjusts the default TLS cipher list and corrects a flaw that would not allow an SSL handshake to properly complete if the port was configured using the wss keyword. Ripple recommends upgrading to 0.50.2 only if server operators are running rippled servers that accept client connections over TLS.
New and Updated Features
This release has no new features.
Bug Fixes
Adjust the default cipher list and correct a flaw that would not allow an SSL handshake to properly complete if the port was configured using the wss keyword (#1985)
The rippled 0.50.0 release includes TickSize, which allows gateways to set a "tick size" for assets they issue 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.
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.
@@ -1383,7 +1524,7 @@We expect the previously announced Suspended Payments feature, which introduces new transaction types to the Ripple protocol that will permit users to cryptographically escrow XRP on RCL, to be enabled via the SusPay Amendment on Tuesday, 2017-02-21.
Also, we expect support for crypto-conditions, which are signature-like structures that can be used with suspended payments to support ILP integration, to be included in the next rippled release scheduled for March.
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. 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).
-The rippled 0.40.1 release increases SQLite database limits in all rippled 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.
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.
@@ -1391,7 +1532,7 @@This release has no new features.
Bug Fixes
Increase SQLite database limits to prevent full-history servers from crashing when restarting. (#1961)
-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 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.
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.
@@ -1406,7 +1547,7 @@Correct an issue in payment flow code that did not remove an unfunded offer (#1860)
Sign validator manifests with both ephemeral and master keys (#1865)
Correctly parse multi-buffer JSON messages (#1862)
-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.
@@ -1431,7 +1572,7 @@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]
-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.
@@ -1450,7 +1591,7 @@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)
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.
@@ -1496,7 +1637,7 @@The rippled 0.31.2 release corrects issues with the fee escalation algorithm. 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.
@@ -1507,7 +1648,7 @@The rippled 0.31.1 release contains one important bug fix. 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.
@@ -1518,7 +1659,7 @@LedgerSequence field. Previous versions of rippled incorrectly assumed that the optional validation field would always be included. Current versions of the software always include the field, and gracefully handle its absence.rippled 0.31.0 has been released.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum.
@@ -1560,7 +1701,7 @@rippled 0.30.1 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.30.1
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit c717006c44126aa0edb3a36ca29ee30e7a72c1d3 @@ -1619,7 +1760,7 @@
rippled 0.30.0 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.30.0
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit a8859b495b552fe1eb140771f0f2cb32d11d2ac2 @@ -1668,7 +1809,7 @@
rippled 0.29.0 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/commits/0.29.0
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 5964710f736e258c7892e8b848c48952a4c7856c @@ -1718,7 +1859,7 @@
rippled 0.28.2 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/commits/release
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 6374aad9bc94595e051a04e23580617bc1aaf300 @@ -1765,7 +1906,7 @@
rippled 0.28.1 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.28.1
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 399c43cae6e90a428e9ce6a988123972b0f03c99 @@ -1815,7 +1956,7 @@
rippled 0.28.0 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.28.0
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 7efd0ab0d6ef017331a0e214a3053893c88f38a9 @@ -1907,7 +2048,7 @@
rippled 0.27.4 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.4
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 92812fe7239ffa3ba91649b2ece1e892b866ec2a @@ -1933,7 +2074,7 @@
rippled 0.27.3-sp2 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.3-sp2
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit f999839e599e131ed624330ad0ce85bb995f02d3 @@ -1959,7 +2100,7 @@
rippled 0.27.3-sp1 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.3-sp1
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 232693419a2c9a8276a0fae991f688f6f01a3add @@ -1985,7 +2126,7 @@
rippled 0.27.3 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.3
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 70c2854f7c8a28801a7ebc81dd62bf0d068188f0 @@ -2011,7 +2152,7 @@
rippled 0.27.2 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.2
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 9cc8eec773e8afc9c12a6aab4982deda80495cf1 @@ -2051,7 +2192,7 @@
rippled 0.27.1 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.1
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 95973ba3e8b0bd28eeaa034da8b806faaf498d8a @@ -2094,7 +2235,7 @@
rippled 0.27.0 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.0
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit c6c8e5d70c6fbde02cd946135a061aa77744396f @@ -2219,7 +2360,7 @@
rippled 0.26.4 has been released. The repository tag is 0.26.4 and can be found on GitHub at: https://github.com/ripple/rippled/commits/0.26.4
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 05a04aa80192452475888479c84ff4b9b54e6ae7 @@ -2291,7 +2432,7 @@
rippled 0.26.3-sp1 has been released. The repository tag is 0.26.3-sp1 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.26.3-sp1
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 2ad6f0a65e248b4f614d38d199a9d5d02f5aaed8 @@ -2350,7 +2491,7 @@
rippled 0.26.2 has been released. The repository tag is 0.26.2 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.26.2
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit b9454e0f0ca8dbc23844a0520d49394e10d445b1 @@ -2386,7 +2527,7 @@
rippled v0.26.1 has been released. The repository tag is 0.26.1 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.26.1
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 9a0e806f78300374e20070e2573755fbafdbfd03 @@ -2411,7 +2552,7 @@
rippled v0.26.0 has been released. The repository tag is 0.26.0 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.26.0
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 9fa5e3987260e39dba322f218d39ac228a5b361b @@ -2452,7 +2593,7 @@
rippled v0.25.2 has been released. The repository tag is 0.25.2 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.25.2
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit ddf68d464d74e1c76a0cfd100a08bc8e65b91fec @@ -2478,7 +2619,7 @@
rippled v0.25.1 has been released. The repository tag is 0.25.1 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.25.1
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit b677cacb8ce0d4ef21f8c60112af1db51dce5bb4 @@ -2514,7 +2655,7 @@
rippled version 0.25.0 has been released. The repository tag is 0.25.0 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.25.0
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 29d1d5f06261a93c5e94b4011c7675ff42443b7f @@ -2548,7 +2689,7 @@
rippled version 0.24.0 has been released. The repository tag is 0.24.0 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.24.0
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 3eb1c7bd6f93e5d874192197f76571184338f702 @@ -2577,7 +2718,7 @@
rippled version 0.23.0 has been released. The repository tag is 0.23.0 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.23.0
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 29a4f61551236f70865d46d6653da2e62de1c701 @@ -2617,7 +2758,7 @@
rippled version 0.22.0 has been released. This release is currently the tip of the develop/ branch and can be found on GitHub at: https://github.com/ripple/rippled/tree/develop The tag is 0.22.0 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.22.0
This is a critical release affecting transaction processing. All partners should update immediately.
@@ -2674,7 +2815,7 @@rippled version 0.21.0 has been released. This release is currently the tip of the develop/ branch and can be found on GitHub at 1. The tag is 0.21.0-rc2 and can be found on GitHub at 2.
This is a critical release. All partners should update immediately.
@@ -2761,7 +2902,7 @@rippled version 0.20.1 has been released. This release is currently the tip of the develop branch and the tag is 0.20.1.
This is a critical release. All partners should update immediately.
@@ -2865,7 +3006,7 @@rippled version 0.19 has now been released. This release is currently the tip of the release branch and the tag is 0.19.0.
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 26783607157a8b96e6e754f71565f4eb0134efc1 @@ -2918,7 +3059,7 @@
rippled version 0.16 has now been released. This release is currently the tip of the master branch and the tag is v0.16.0.
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 15ef43505473225af21bb7b575fb0b628d5e7f73 @@ -2966,7 +3107,7 @@
Issues
None known
-+
Version 0.14
rippled version 0.14 has now been released. This release is currently the tip of the master branch and the tag is v0.12.0.
Prior to building, please confirm you have the correct source tree with the
git logcommand. The first log entry should be the change setting the version:commit b6d11c08d0245ee9bafbb97143f5d685dd2979fc @@ -3014,7 +3155,7 @@
Issues
None known
-+
Version 0.12
rippled version 0.12 has now been released. This release is currently the tip of the master branch and can be found on GitHub. The tag is v0.12.0.
Prior to building, please confirm you have the correct source tree with the
git logcommand. The first log entry should be the change setting the version:commit d0a9da6f16f4083993e4b6c5728777ffebf80f3a diff --git a/namespaceripple_1_1BuildInfo.html b/namespaceripple_1_1BuildInfo.html index 1f2cd897cf8..f259dd74a5c 100644 --- a/namespaceripple_1_1BuildInfo.html +++ b/namespaceripple_1_1BuildInfo.html @@ -99,7 +99,7 @@
Variables | |
| char const *const | versionString = "2.0.0-rc7" |
| char const *const | versionString = "2.0.0" |
| static constexpr std::uint64_t | implementationVersionIdentifier |
| char const* const ripple::BuildInfo::versionString = "2.0.0-rc7" | +char const* const ripple::BuildInfo::versionString = "2.0.0" |