rippled (XRP Ledger server) Version 1.12.0-b2 (beta)

What's Changed

This release makes a breaking change to the Clawback amendment, and introduces a new amendment called AMM.

• replace hand-rolled lexicalCast by @dangell7 in #4473
• Fix package definition for Conan by @thejohnfreeman in #4485
• remove deprecated fields in ledger command, fix for #3214 by @ckeshava in #4244
• Trivial: Rename ServerHandlerImp to ServerHandler by @scottschurr in #4516
• [Trivial] Fix build references to deleted ServerHandlerImp by @ximinez in #4592
• APIv2(AccountTx): Added error messages on AccountTx by @PeterChen13579 in #4571
• Change enum values to be powers of two (fix #3417) by @ckeshava in #4239
• Cancel overridden workflows by @thejohnfreeman in #4597
• Fix deb package build by @legleux in #4591
• APIv2(account_info): handle invalid "signer_lists" value by @PeterChen13579 in #4585
• [TRIVIAL] Update checkout action version to resolve warning by @ximinez in #4598
• add pre-commit hook for clang-format by @mvadari in #4599
• Add binary hardening compile and link flags by @thejohnfreeman in #4603
• Add allowClawback flag for account_info by @shawnxie999 in #4590
• Change the return type of mulDiv to std::optional by @ckeshava in #4243
• APIv2(ledger_entry): return "invalidParams" when fields missing by @arihantkothari in #4552
• docs(CONTRIBUTING): push beta releases to release by @intelliot in #4589
• Adapt to change in Conan recipe for NuDB by @thejohnfreeman in #4615
• Introduce AMM support (XLS-30d) by @gregtatcam in #4294
• Update dependencies by @thejohnfreeman in #4595
• Rename allowClawback flag to allowTrustLineClawback by @shawnxie999 in #4617
• BUILD: list steps after dependencies update by @intelliot in #4623
• Proposed 1.12.0-b2 by @intelliot in #4627

New Contributors

• @PeterChen13579 made their first contribution in #4571
• @mvadari made their first contribution in #4599
• @arihantkothari made their first contribution in #4552
• @gregtatcam made their first contribution in #4294

Full Changelog: 1.12.0-b1...1.12.0-b2

PR: #4627

rippled (XRP Ledger server) Version 1.12.0-b1 (beta)

What's Changed

This release introduces two new amendments: fixReducedOffersV1 and Clawback.

• Enable the Beta RPC API (v2) for all unit tests: by @ximinez in #4573
• fixReducedOffersV1: curtail the occurrence of order books that are blocked by reduced offers by @scottschurr in #4512
• Add RPC/WS ports to server_info by @drlongle in #4427
• Use Artifactory remote in nix workflow by @thejohnfreeman in #4556
• Typedfield has bad move constructor by @HowardHinnant in #4567
• XLS-39 Clawback: by @shawnxie999 in #4553
• Proposed 1.12.0-b1 by @intelliot in #4586

Full Changelog: 1.11.0...1.12.0-b1

PR: #4586

rippled (XRP Ledger server) Version 1.11.0

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

Action Required

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.

Install / Upgrade

On supported platforms, see the instructions on installing or updating rippled.

What's Changed

New Features and Improvements

• Allow port numbers be be specified using a either a colon or a space by @RichardAH in #4328
• Eliminate memory allocation from critical path: by @nbougalis in #4353
• Make it easy for projects to depend on libxrpl by @thejohnfreeman in #4449
• Add the ability to mark amendments as obsolete by @ximinez in #4291
• Always create the FeeSettings object in genesis ledger by @ximinez in #4319
• Log exception messages in several locations by @drlongle in #4400
• Parse flags in account_info method by @drlongle in #4459
• Add NFTokenPages to account_objects RPC by @RichardAH in #4352
• add jss fields used by clio nft_info by @ledhed2222 in #4320
• Introduce a slab-based memory allocator and optimize SHAMapItem by @nbougalis in #4218
• Add NetworkID field to transactions to help prevent replay attacks on and from side-chains by @RichardAH in #4370
• If present, set quorum based on command line. by @mtrippled in #4489
• API does not accept seed or public key for account by @drlongle in #4404
• Add nftoken_id, nftoken_ids and offer_id meta fields into NFT Tx responses by @shawnxie999 in #4447

Bug Fixes

• fix(gateway_balances): handle overflow exception by @RichardAH in #4355
• fix(ValidatorSite): handle rare null pointer dereference in timeout by @ximinez in #4420
• RPC commands understand markers derived from all ledger object types by @ximinez in #4361
• fixNFTokenRemint: prevent NFT re-mint: by @shawnxie999 in #4406
• Fix a case where ripple::Expected returned a json array, not a value by @scottschurr in #4401
• fix: Ledger data returns an empty list (instead of null) when all entries are filtered out by @drlongle in #4398
• Fix unit test ripple.app.LedgerData by @drlongle in #4484
• Fix the fix for std::result_of by @thejohnfreeman in #4496
• Fix errors for Clang 16 by @thejohnfreeman in #4501
• Ensure that switchover vars are initialized before use: by @seelabs in #4527
• Move faulty assert by @ximinez in #4533
• Fix unaligned load and stores: (#4528) by @seelabs in #4531
• fix node size estimation by @dangell7 in #4536
• fix: remove redundant moves by @ckeshava in #4565

Code Cleanup and Testing

• Replace compare() with the three-way comparison operator in base_uint, Issue and Book by @drlongle in #4411
• Rectify the import paths of boost::function_output_iterator by @ckeshava in #4293
• Expand Linux test matrix by @thejohnfreeman in #4454
• Add patched recipe for SOCI by @thejohnfreeman in #4510
• Switch to self-hosted runners for macOS by @thejohnfreeman in #4511
• [TRIVIAL] Add missing includes by @seelabs in #4555

Docs

• Refactor build instructions by @thejohnfreeman in #4381
• Add install instructions for package managers by @thejohnfreeman in #4472
• Fix typo by @solmsted in #4508
• Update environment.md by @sappenin in #4498
• Update BUILD.md by @oeggert in #4514
• Trivial: add comments for NFToken-related invariants by @scottschurr in #4558

New Contributors

• @drlongle made their first contribution in #4411
• @ckeshava made their first contribution in #4293
• @solmsted made their first contribution in #4508
• @sappenin made their first contribution in #4498
• @oeggert made their first contribution in #4514

Full Changelog: 1.10.1...1.11.0

GitHub

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.

Credits

The following people contributed directly to this release:

• Alloy Networks [email protected]
• Brandon Wilson [email protected]
• Chenna Keshava B S [email protected]
• David Fuelling [email protected]
• Denis Angell [email protected]
• Ed Hennis [email protected]
• Elliot Lee [email protected]
• John Freeman [email protected]
• Mark Travis [email protected]
• Nik Bougalis [email protected]
• RichardAH [email protected]
• Scott Determan [email protected]
• Scott Schurr [email protected]
• Shawn Xie [email protected]
• drlongle [email protected]
• ledhed2222 [email protected]
• oeggert [email protected]
• solmsted [email protected]

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:

[email protected]

rippled (XRP Ledger server) Version 1.10.1

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

Install / Upgrade

On supported platforms, see the instructions on installing or updating rippled.

Changelog

• da18c86cbf Build packages with Ubuntu 18.04
• f7b3ddd87b Reporting Mode: Do not attempt to acquire missing data from peer network (#4458)

Full Changelog: 1.10.0...1.10.1

GitHub

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.

Credits

The following people contributed directly to this release:

• John Freeman [email protected]
• Mark Travis [email protected]
• Michael Legleux [email protected]

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:

[email protected]

rippled (XRP Ledger server) Version 1.10.0

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

Action Required

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.

Install / Upgrade

On supported platforms, see the instructions on installing or updating rippled.

New Amendments

• 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. #4157

• featureDisallowIncoming: Enables an account to block incoming checks, payment channels, NFToken offers, and trust lines. #4336

• featureXRPFees: Simplifies transaction cost calculations to use XRP directly, rather than calculating indirectly in "fee units" and translating the results to XRP. Updates all instances of "fee units" in the protocol and ledger data to be drops of XRP instead. #4247

  • BREAKING CHANGE: If this amendment is enabled, the fee_ref field will be removed from the Ledger subscription stream, as it will no longer be relevant.

• fixUniversalNumber: Simplifies and unifies the code for decimal floating point math. In some cases, this provides slightly better accuracy than the previous code, resulting in calculations whose least significant digits are different than when calculated with the previous code. The different results may cause other edge case differences where precise calculations are used, such as ranking of offers or processing of payments that use several different paths. #4192

• fixNonFungibleTokensV1_2: This amendment is a combination of NFToken fixes. #4417

  • Fixes unburnable NFTokens when it has over 500 offers. #4346
  • Fixes 3 NFToken offer acceptance issues. #4380
  • Prevents brokered sales of NFTokens to owners. #4403
  • Only allows the destination to settle NFToken offers through brokerage. #4399

• fixTrustLinesToSelf: 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. 69bb2be

Changelog

New Features and Improvements

• Improve Handshake in the peer protocol: Switched to using a cryptographically secure PRNG for the Instance Cookie. rippled now uses hex encoding for the Closed-Ledger and Previous-Ledger fields in the Handshake. Also added --newnodeid and --nodeid command line options. 5a15229

• RPC tooBusy response now has 503 HTTP status code: Added ripplerpc 3.0, enabling RPC tooBusy responses to return relevant HTTP status codes. This is a non-breaking change that only applies to JSON-RPC when you include "ripplerpc": "3.0" in the request. #4143

• Use the Conan package manager: Added a conanfile.py and Conan recipe for Snappy. Removed the RocksDB recipe from the repo; you can now get it from Conan Center. #4367, c2b03fe

• Update Build Instructions: Updated the build instructions to build with the Conan package manager and restructured info for easier comprehension. #4376, #4383

• Revise CONTRIBUTING: Updated code contribution guidelines. rippled is an open source project and contributions are very welcome. #4382

• Update documented pathfinding configuration defaults: 417cfc2 changed the default Path Finding configuration values, but missed updating the values documented in rippled-example.cfg. Updated those defaults and added recommended values for nodes that want to support advanced pathfinding. #4409

• Remove gRPC code previously used for the Xpring SDK: Removed gRPC code used for the Xpring SDK. The gRPC API is also enabled locally by default in rippled-example.cfg. This API is used for Reporting Mode and Clio. 28f4cc7

• Switch from C++17 to C++20: Updated rippled to use C++20. 92d35e5

• Support for Boost 1.80.0:: 04ef885

• Reduce default reserves to 10/2: Updated the hard-coded default reserves to match the current settings on Mainnet. #4329

• Improve self-signed certificate generation: Improved speed and security of TLS certificate generation on fresh startup. 0ecfc7c

Bug Fixes

• Update command-line usage help message: Added manifest and validator_info to the rippled CLI usage statement. b88ed5a

• Work around gdb bug by changing a template parameter: Added a workaround for a bug in gdb, where unsigned template parameters caused issues with RTTI. #4332

• Fix clang 15 warnings: #4325

• Catch transaction deserialization error in doLedgerGrpc: Fixed an issue in the gRPC API, so Clio can extract ledger headers and state objects from specific transactions that can't be deserialized by rippled code. #4323

• Update dependency: gRPC: New Conan recipes broke the old version of gRPC, so the dependency was updated. #4407

• Fix Doxygen workflow: Added options to build documentation that don't depend on the library dependencies of rippled. #4372

• Don't try to read SLE with key 0 from the ledger: Fixed the preclaim function to check for 0 in NFTokenSellOffer and NFTokenBuyOffer before calling Ledger::read. This issue only affected debug builds. #4351

• Update broken link to hosted Doxygen content: 5e1cb09

Code Cleanup

• Prevent unnecessary shared_ptr copies by accepting a value in SHAMapInnerNode::setChild: #4266

• Release TaggedCache object memory outside the lock: 3726f8b

• Rename SHAMapStoreImp::stopping() to healthWait(): 7e9e910

• Improve wrapper around OpenSSL RAND: 7b3507b

• Improve AccountID string conversion caching: Improved memory cache usage. e2eed96

• Build the command map at compile time: 9aaa0df

• Avoid unnecessary copying and dynamic memory allocations: d318ab6

• Use constexpr to check memo validity: e67f905

• Remove charUnHex: 83ac141

• Remove deprecated AccountTxOld.cpp: ce64f7a

• Remove const_cast usage: 23ce431

• Remove inaccessible code paths and outdated data format wchar_t: 95fabd5

• Improve move semantics in Expected: #4326

GitHub

The public source code repository for...

rippled (XRP Ledger server) Version 1.10.0-rc4

Version 1.10.0-rc4 (release candidate) of rippled, the reference implementation of the XRP Ledger protocol is now available. The 1.10.0 release line introduces six new amendments:

• fixTrustLinesToSelf
• featureImmediateOfferKilled
• featureDisallowIncoming
• featureXRPFees
• fixUniversalNumber
• fixNonFungibleTokensV1_2

Information about these amendments can be found on Known Amendments.

rippled (XRP Ledger server) Version 1.9.4

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.

Action Required

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.

Install / Upgrade

On supported platforms, see the instructions on installing or updating rippled.

Changelog

Contributions

The primary change in this release is the following bug fix:

• Introduce fixRemoveNFTokenAutoTrustLine amendment: Introduces the 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)

GitHub

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.

Credits

The following people contributed directly to this release:

• Scott Schurr [email protected]
• Howard Hinnant [email protected]
• Scott Determan [email protected]
• Ikko Ashimine [email protected]

rippled (XRP Ledger server) Version 1.9.3

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.

Install / Upgrade

On supported platforms, see the instructions on installing or updating rippled.

Changelog

Contributions

This releases contains the following bug fixes:

• Change by-value to by-reference to persist vote: A minor technical flaw, caused by use of a copy instead of a reference, resulted in operator-configured "yes" votes to not be properly loaded after a restart. (#4256)
• Properly handle self-assignment of PublicKey: The PublicKey copy assignment operator mishandled the case where a PublicKey would be assigned to itself, and could result in undefined behavior.

GitHub

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.

Credits

The following people contributed directly to this release:

• Howard Hinnant [email protected]
• Crypto Brad Garlinghouse [email protected]
• Wo Jake [email protected]

rippled (XRP Ledger server) Version 1.9.2

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.

Action Required

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.

Install / Upgrade

On supported platforms, see the instructions on installing or updating rippled.

Changelog

This release contains the following features and improvements.

• Introduce fixNFTokenNegOffer amendment. This amendment fixes a bug in the Non-Fungible Tokens (NFTs) functionality provided by the NonFungibleTokensV1 amendment (not currently enabled on Mainnet). The bug allowed users to place offers to buy tokens for negative amounts of money when using Brokered Mode. Anyone who accepted such an offer would transfer the token and pay money. This amendment explicitly disallows offers to buy or sell NFTs for negative amounts of money, and returns an appropriate error code. This also corrects the error code returned when placing offers to buy or sell NFTs for negative amounts in Direct Mode. (8266d9d)
• Introduce NonFungibleTokensV1_1 amendment. This amendment encompasses three NFT-related amendments: the original NonFungibleTokensV1 amendment (from version 1.9.0), the fixNFTokenDirV1 amendment (from version 1.9.1), and the new fixNFTokenNegOffer amendment from this release. This amendment contains no changes other than enabling those three amendments together; this allows validators to vote in favor of only enabling the feature and fixes at the same time. (59326bb)
• Handle invalid port numbers. If the user specifies a URL with an invalid port number, the server would silently attempt to use port 0 instead. Now it raises an error instead. This affects admin API methods and config file parameters for downloading history shards and specifying validator list sites. (#4213)
• Reduce log noisiness. Decreased the severity of benign log messages in several places: "addPathsForType" messages during regular operation, expected errors during unit tests, and missing optional documentation components when compiling from source. (#4178, #4166, #4180)
• Fix race condition in history shard implementation and support clang's ThreadSafetyAnalysis tool. Added build settings so that developers can use this feature of the clang compiler to analyze the code for correctness, and fix an error found by this tool, which was the source of rare crashes in unit tests. (#4188)
• Prevent crash when rotating a database with missing data. When rotating databases, a missing entry could cause the server to crash. While there should never be a missing database entry, this change keeps the server running by aborting database rotation. (#4182)
• Fix bitwise comparison in OfferCreate. Fixed an expression that incorrectly used a bitwise comparison for two boolean values rather than a true boolean comparison. The outcome of the two comparisons is equivalent, so this is not a transaction processing change, but the bitwise comparison relied on compilers to implicitly fix the expression. (#4183)
• Disable cluster timer when not in a cluster. Disabled a timer that was unused on servers not running in clustered mode. The functionality of clustered servers is unchanged. (#4173)
• Limit how often to process peer discovery messages. In the peer-to-peer network, servers periodically share IP addresses of their peers with each other to facilitate peer discovery. It is not necessary to process these types of messages too often; previously, the code tracked whether it needed to process new messages of this type but always processed them anyway. With this change, the server no longer processes peer discovery messages if it has done so recently. (#4202)
• Improve STVector256 deserialization. Optimized the processing of this data type in protocol messages. This data type is used in several types of ledger entry that are important for bookkeeping, including directory pages that track other ledger types, amendments tracking, and the ledger hashes history. (#4204)
• Fix and refactor spinlock code. The spinlock code, which protects the SHAMapInnerNode child lists, had a mistake that allowed the same child to be repeatedly locked under some circumstances. Fixed this bug and improved the spinlock code to make it easier to use correctly and easier to verify that the code works correctly. (#4201)
• Improve comments and contributor documentation. Various minor documentation changes including some to reflect the fact that the source code repository is now owned by the XRP Ledger Foundation. (#4214, #4179, #4222)
• Introduces a new API book_changes to provide information in a format that is useful for building charts that highlight DEX activity at a per-ledger level. (#4212)

Contributions

GitHub

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.

Credits

The following people contributed directly to this release:

• Chenna Keshava B S [email protected]
• Ed Hennis [email protected]
• Ikko Ashimine [email protected]
• Nik Bougalis [email protected]
• Richard Holland [email protected]
• Scott Schurr [email protected]
• Scott Determan [email protected]

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.

rippled (XRP Ledger server) Version 1.9.1

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.

Action Required

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.

Install / Upgrade

On supported platforms, see the instructions on installing or updating rippled.

Changelog

This release contains the following features and improvements.

New Features and Amendments

• Introduce fixNFTokenDirV1 Amendment - This amendment fixes an off-by-one error that occurred in some corner cases when determining which 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)

• Introduce ExpandedSignerList Amendment - This amendment expands the maximum signer list size to 32 entries and allows each signer to have an optional 256-bit WalletLocator field containing arbitrary data. (#4097)

• Pause online deletion rather than canceling it if the server fails health check - The server stops performing online deletion of old ledger history if the server fails its internal health check during this time. Online deletion can now resume after the server recovers, rather than having to start over. (#4139)

Bug Fixes and Performance Improvements

• Fix performance issues introduced in 1.9.0 - Readjusts some parameters of the ledger acquisition engine to revert some changes introduced in 1.9.0 that had adverse effects on some systems, including causing some systems to fail to sync to the network. (#4152)

• Improve Memory Efficiency of Path Finding - Finding paths for cross-currency payments is a resource-intensive operation. While that remains true, this fix improves memory usage of pathfinding by discarding trust line results that cannot be used before those results are fully loaded or cached. (#4111)

• Fix incorrect CMake behavior on Windows when platform is unspecified or x64 - Fixes handling of platform selection when using the cmake-gui tool to build on Windows. The generator expects Win64 but the GUI only provides x64 as an option, which raises an error. This fix only raises an error if the platform is Win32 instead, allowing the generation of solution files to succeed. (#4150)

• Fix test failures with newer MSVC compilers on Windows - Fixes some cases where the API handler code used string pointer comparisons, which may not work correctly with some versions of the MSVC compiler. (#4149)

• Update minimum Boost version to 1.71.0 - This release is compatible with Boost library versions 1.71.0 through 1.77.0. The build configuration and documentation have been updated to reflect this. (#4134)

• Fix unit test failures for DatabaseDownloader - Increases a timeout in the 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)

• Refactor relational database interface - Improves code comments, naming, and organization of the module that interfaces with relational databases (such as the SQLite database used for tracking transaction history). (#3965)

Contributions

GitHub

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.

Credits

The following people contributed directly to this release:

• Devon White [email protected]
• Ed Hennis [email protected]
• Gregory Popovitch [email protected]
• Mark Travis [email protected]
• Manoj Doshi [email protected]
• Nik Bougalis [email protected]
• Richard Holland [email protected]
• Scott Schurr [email protected]

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.