ARCHIVE/rippled
1
0
Fork 0
mirror of https://github.com/XRPLF/rippled.git synced 2025-11-26 22:15:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: e5275b8577

Browse Source
This commit is contained in:
nbougalis
2022-07-26 03:00:18 +00:00
parent 70c2d3809d
commit 66f4b7af57
3 changed files with 168 additions and 118 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
BuildInfo_8cpp_source.html
View File

@@ -104,7 +104,7 @@ $(function() {
<div class="line"><a name="l00033"></a><span class="lineno"> 33</span>&#160;<span class="comment">// and follow the format described at http://semver.org/</span></div> <div class="line"><a name="l00033"></a><span class="lineno"> 33</span>&#160;<span class="comment">// and follow the format described at http://semver.org/</span></div>
<div class="line"><a name="l00034"></a><span class="lineno"> 34</span>&#160;<span class="comment">//------------------------------------------------------------------------------</span></div> <div class="line"><a name="l00034"></a><span class="lineno"> 34</span>&#160;<span class="comment">//------------------------------------------------------------------------------</span></div>
<div class="line"><a name="l00035"></a><span class="lineno"> 35</span>&#160;<span class="comment">// clang-format off</span></div> <div class="line"><a name="l00035"></a><span class="lineno"> 35</span>&#160;<span class="comment">// clang-format off</span></div>
<div class="line"><a name="l00036"></a><span class="lineno"><a class="line" href="namespaceripple_1_1BuildInfo.html#add98d1ad0d107ee61a6ace72d982cf36"> 36</a></span>&#160;<span class="keywordtype">char</span> <span class="keyword">const</span>* <span class="keyword">const</span> <a class="code" href="namespaceripple_1_1BuildInfo.html#add98d1ad0d107ee61a6ace72d982cf36">versionString</a> = <span class="stringliteral">&quot;1.9.2-rc1&quot;</span></div> <div class="line"><a name="l00036"></a><span class="lineno"><a class="line" href="namespaceripple_1_1BuildInfo.html#add98d1ad0d107ee61a6ace72d982cf36"> 36</a></span>&#160;<span class="keywordtype">char</span> <span class="keyword">const</span>* <span class="keyword">const</span> <a class="code" href="namespaceripple_1_1BuildInfo.html#add98d1ad0d107ee61a6ace72d982cf36">versionString</a> = <span class="stringliteral">&quot;1.9.2&quot;</span></div>
<div class="line"><a name="l00037"></a><span class="lineno"> 37</span>&#160;<span class="comment">// clang-format on</span></div> <div class="line"><a name="l00037"></a><span class="lineno"> 37</span>&#160;<span class="comment">// clang-format on</span></div>
<div class="line"><a name="l00038"></a><span class="lineno"> 38</span>&#160; </div> <div class="line"><a name="l00038"></a><span class="lineno"> 38</span>&#160; </div>
<div class="line"><a name="l00039"></a><span class="lineno"> 39</span>&#160;<span class="preprocessor">#if defined(DEBUG) || defined(SANITIZER)</span></div> <div class="line"><a name="l00039"></a><span class="lineno"> 39</span>&#160;<span class="preprocessor">#if defined(DEBUG) || defined(SANITIZER)</span></div>

280
md____w_rippled_rippled_RELEASENOTES.html
View File

@@ -70,30 +70,80 @@ $(function() {
<div class="caption"> <div class="caption">
@2x.png "XRP"</div></div> @2x.png "XRP"</div></div>
<p>This document contains the release notes for <code>rippled</code>, the reference server implementation of the XRP Ledger protocol. To learn more about how to build, run or update a <code>rippled</code> server, visit <a href="https://xrpl.org/install-rippled.html">https://xrpl.org/install-rippled.html</a></p> <p>This document contains the release notes for <code>rippled</code>, the reference server implementation of the XRP Ledger protocol. To learn more about how to build, run or update a <code>rippled</code> server, visit <a href="https://xrpl.org/install-rippled.html">https://xrpl.org/install-rippled.html</a></p>
<p>Have new ideas? Need help with setting up your node? Come visit us <a href="https://github.com/ripple/rippled/issues/new/choose">here</a></p> <p>Have new ideas? Need help with setting up your node? Come visit us <a href="https://github.com/xrplf/rippled/issues/new/choose">here</a></p>
<h1><a class="anchor" id="autotoc_md310"></a> <h1><a class="anchor" id="autotoc_md310"></a>
Introducing XRP Ledger version 1.9.1</h1> Introducing XRP Ledger version 1.9.2</h1>
<p>Version 1.9.1 of <code>rippled</code>, 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.</p> <p>Version 1.9.2 of <code>rippled</code>, 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.</p>
<h2><a class="anchor" id="autotoc_md311"></a> <h2><a class="anchor" id="autotoc_md311"></a>
Action Required</h2> Action Required</h2>
<p>This release introduces two new amendments to the XRP Ledger protocol. These amendments are now open for voting according to the XRP Ledger's <a href="https://xrpl.org/amendments.html">amendment process</a>, which enables protocol changes following two weeks of &gt;80% support from trusted validators.</p> <p>This release introduces a two new amendments to the XRP Ledger protocol. The first, <b>fixNFTokenNegOffer</b>, fixes a bug in code associated with the <b>NonFungibleTokensV1</b> amendment, originally introduced in <a href="https://xrpl.org/blog/2022/rippled-1.9.0.html">version 1.9.0</a>. The second, <b>NonFungibleTokensV1_1</b>, is a "roll-up" amendment that enables the <b>NonFungibleTokensV1</b> feature plus the two fix amendments associated with it, <b>fixNFTokenDirV1</b> and <b>fixNFTokenNegOffer</b>.</p>
<p>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.</p> <p>If you want to enable NFT code on the XRP Ledger Mainnet, you can vote in favor of only the <b>NonFungibleTokensV1_1</b> amendment to support enabling the feature and fixes together, without risk that the unfixed NFT code may become enabled first.</p>
<p>The <b>fixNFTokenDirV1</b> amendment fixes a bug in code associated with the <b>NonFungibleTokensV1</b> amendment, so the fixNFTokenDirV1 amendment should be enabled first. All validator operators are encouraged to <a href="https://xrpl.org/configure-amendment-voting.html">configure amendment voting</a> to oppose the NonFungibleTokensV1 amendment until <em>after</em> the fixNFTokenDirV1 amendment has become enabled. For more information about NFTs on the XRP Ledger, see <a href="https://xrpl.org/nft-conceptual-overview.html">NFT Conceptual Overview</a>.</p> <p>These amendments are now open for voting according to the XRP Ledger's <a href="https://xrpl.org/amendments.html">amendment process</a>, which enables protocol changes following two weeks of &gt;80% support from trusted validators.</p>
<p>The <b>ExpandedSignerList</b> 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.</p> <p>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.</p>
<p>For more information about NFTs on the XRP Ledger, see <a href="https://xrpl.org/nft-conceptual-overview.html">NFT Conceptual Overview</a>.</p>
<h2><a class="anchor" id="autotoc_md312"></a> <h2><a class="anchor" id="autotoc_md312"></a>
Install / Upgrade</h2> Install / Upgrade</h2>
<p>On supported platforms, see the <a href="https://xrpl.org/install-rippled.html">instructions on installing or updating <code>rippled</code></a>.</p> <p>On supported platforms, see the <a href="https://xrpl.org/install-rippled.html">instructions on installing or updating <code>rippled</code></a>.</p>
<h2><a class="anchor" id="autotoc_md313"></a> <h2><a class="anchor" id="autotoc_md313"></a>
Changelog</h2> Changelog</h2>
<p>This release contains the following features and improvements.</p> <p>This release contains the following features and improvements.</p>
<ul>
<li><b>Introduce fixNFTokenNegOffer amendment.</b> 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 <em>and</em> 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. (<a href="https://github.com/XRPLF/rippled/commit/8266d9d598d19f05e1155956b30ca443c27e119e">8266d9d</a>)</li>
<li><b>Introduce <code>NonFungibleTokensV1_1</code> amendment.</b> 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 <em>only</em> enabling the feature and fixes at the same time. (<a href="https://github.com/XRPLF/rippled/commit/59326bbbc552287e44b3a0d7b8afbb1ddddb3e3b">59326bb</a>)</li>
<li><b>Handle invalid port numbers.</b> 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. (<a href="https://github.com/XRPLF/rippled/pull/4213">#4213</a>)</li>
<li><b>Reduce log noisiness.</b> 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. (<a href="https://github.com/XRPLF/rippled/pull/4178">#4178</a>, <a href="https://github.com/XRPLF/rippled/pull/4166">#4166</a>, <a href="https://github.com/XRPLF/rippled/pull/4180">#4180</a>)</li>
<li><b>Fix race condition in history shard implementation and support clang's ThreadSafetyAnalysis tool.</b> 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. (<a href="https://github.com/XRPLF/rippled/pull/4188">#4188</a>)</li>
<li><b>Prevent crash when rotating a database with missing data.</b> 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. (<a href="https://github.com/XRPLF/rippled/pull/4182">#4182</a>)</li>
<li><b>Fix bitwise comparison in OfferCreate.</b> 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. (<a href="https://github.com/XRPLF/rippled/pull/4183">#4183</a>)</li>
<li><b>Disable cluster timer when not in a cluster.</b> Disabled a timer that was unused on servers not running in clustered mode. The functionality of clustered servers is unchanged. (<a href="https://github.com/XRPLF/rippled/pull/4173">#4173</a>)</li>
<li><b>Limit how often to process peer discovery messages.</b> 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. (<a href="https://github.com/XRPLF/rippled/pull/4202">#4202</a>)</li>
<li><b>Improve STVector256 deserialization.</b> 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. (<a href="https://github.com/XRPLF/rippled/pull/4204">#4204</a>)</li>
<li><b>Fix and refactor spinlock code.</b> The spinlock code, which protects the <code>SHAMapInnerNode</code> 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. (<a href="https://github.com/XRPLF/rippled/pull/4201">#4201</a>)</li>
<li><b>Improve comments and contributor documentation.</b> Various minor documentation changes including some to reflect the fact that the source code repository is now owned by the XRP Ledger Foundation. (<a href="https://github.com/XRPLF/rippled/pull/4214">#4214</a>, <a href="https://github.com/XRPLF/rippled/pull/4179">#4179</a>, <a href="https://github.com/XRPLF/rippled/pull/4222">#4222</a>)</li>
<li><b>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.</b> (<a href="https://github.com/XRPLF/rippled/pull/4212">#4212</a>)</li>
</ul>
<h2><a class="anchor" id="autotoc_md314"></a> <h2><a class="anchor" id="autotoc_md314"></a>
Contributions</h2>
<h3><a class="anchor" id="autotoc_md315"></a>
GitHub</h3>
<p>The public source code repository for <code>rippled</code> is hosted on GitHub at <a href="https://github.com/XRPLF/rippled">https://github.com/XRPLF/rippled</a>.</p>
<p>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.</p>
<h3><a class="anchor" id="autotoc_md316"></a>
Credits</h3>
<p>The following people contributed directly to this release:</p>
<ul>
<li>Chenna Keshava B S <a href="#" onclick="location.href='mai'+'lto:'+'ckb'+'s.'+'kes'+'ha'+'va5'+'6@'+'gma'+'il'+'.co'+'m'; return false;">ckbs.<span style="display: none;">.nosp@m.</span>kesh<span style="display: none;">.nosp@m.</span>ava56<span style="display: none;">.nosp@m.</span>@gma<span style="display: none;">.nosp@m.</span>il.co<span style="display: none;">.nosp@m.</span>m</a></li>
<li>Ed Hennis <a href="#" onclick="location.href='mai'+'lto:'+'ed@'+'ri'+'ppl'+'e.'+'com'; return false;">ed@ri<span style="display: none;">.nosp@m.</span>pple<span style="display: none;">.nosp@m.</span>.com</a></li>
<li>Ikko Ashimine <a href="#" onclick="location.href='mai'+'lto:'+'elt'+'oc'+'iea'+'r@'+'gma'+'il'+'.co'+'m'; return false;">eltoc<span style="display: none;">.nosp@m.</span>iear<span style="display: none;">.nosp@m.</span>@gmai<span style="display: none;">.nosp@m.</span>l.co<span style="display: none;">.nosp@m.</span>m</a></li>
<li>Nik Bougalis <a href="#" onclick="location.href='mai'+'lto:'+'nik'+'b@'+'bou'+'ga'+'lis'+'.n'+'et'; return false;">nikb@<span style="display: none;">.nosp@m.</span>boug<span style="display: none;">.nosp@m.</span>alis.<span style="display: none;">.nosp@m.</span>net</a></li>
<li>Richard Holland <a href="#" onclick="location.href='mai'+'lto:'+'ric'+'ha'+'rd.'+'ho'+'lla'+'nd'+'@st'+'ar'+'sto'+'ne'+'.co'+'.n'+'z'; return false;">richa<span style="display: none;">.nosp@m.</span>rd.h<span style="display: none;">.nosp@m.</span>ollan<span style="display: none;">.nosp@m.</span>d@st<span style="display: none;">.nosp@m.</span>arsto<span style="display: none;">.nosp@m.</span>ne.c<span style="display: none;">.nosp@m.</span>o.nz</a></li>
<li>Scott Schurr <a href="#" onclick="location.href='mai'+'lto:'+'sco'+'tt'+'@ri'+'pp'+'le.'+'co'+'m'; return false;">scott<span style="display: none;">.nosp@m.</span>@rip<span style="display: none;">.nosp@m.</span>ple.c<span style="display: none;">.nosp@m.</span>om</a></li>
<li>Scott Determan <a href="#" onclick="location.href='mai'+'lto:'+'sco'+'tt'+'.de'+'te'+'rma'+'n@'+'yah'+'oo'+'.co'+'m'; return false;">scott<span style="display: none;">.nosp@m.</span>.det<span style="display: none;">.nosp@m.</span>erman<span style="display: none;">.nosp@m.</span>@yah<span style="display: none;">.nosp@m.</span>oo.co<span style="display: none;">.nosp@m.</span>m</a></li>
</ul>
<p>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: <a href="https://github.com/XRPLF/rippled/graphs/contributors">https://github.com/XRPLF/rippled/graphs/contributors</a>.</p>
<h1><a class="anchor" id="autotoc_md317"></a>
Introducing XRP Ledger version 1.9.1</h1>
<p>Version 1.9.1 of <code>rippled</code>, 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.</p>
<h2><a class="anchor" id="autotoc_md318"></a>
Action Required</h2>
<p>This release introduces two new amendments to the XRP Ledger protocol. These amendments are now open for voting according to the XRP Ledger's <a href="https://xrpl.org/amendments.html">amendment process</a>, which enables protocol changes following two weeks of &gt;80% support from trusted validators.</p>
<p>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.</p>
<p>The <b>fixNFTokenDirV1</b> amendment fixes a bug in code associated with the <b>NonFungibleTokensV1</b> amendment, so the fixNFTokenDirV1 amendment should be enabled first. All validator operators are encouraged to <a href="https://xrpl.org/configure-amendment-voting.html">configure amendment voting</a> to oppose the NonFungibleTokensV1 amendment until <em>after</em> the fixNFTokenDirV1 amendment has become enabled. For more information about NFTs on the XRP Ledger, see <a href="https://xrpl.org/nft-conceptual-overview.html">NFT Conceptual Overview</a>.</p>
<p>The <b>ExpandedSignerList</b> 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.</p>
<h2><a class="anchor" id="autotoc_md319"></a>
Install / Upgrade</h2>
<p>On supported platforms, see the <a href="https://xrpl.org/install-rippled.html">instructions on installing or updating <code>rippled</code></a>.</p>
<h2><a class="anchor" id="autotoc_md320"></a>
Changelog</h2>
<p>This release contains the following features and improvements.</p>
<h2><a class="anchor" id="autotoc_md321"></a>
New Features and Amendments</h2> New Features and Amendments</h2>
<ul> <ul>
<li><b>Introduce fixNFTokenDirV1 Amendment</b> - This amendment fixes an off-by-one error that occurred in some corner cases when determining which <code>NFTokenPage</code> an <code>NFToken</code> object belongs on. It also adjusts the constraints of <code>NFTokenPage</code> invariant checks, so that certain error cases fail with a suitable error code such as <code>tecNO_SUITABLE_TOKEN_PAGE</code> instead of failing with a <code>tecINVARIANT_FAILED</code> error code. (<a href="https://github.com/ripple/rippled/pull/4155">#4155</a>)</li> <li><b>Introduce fixNFTokenDirV1 Amendment</b> - This amendment fixes an off-by-one error that occurred in some corner cases when determining which <code>NFTokenPage</code> an <code>NFToken</code> object belongs on. It also adjusts the constraints of <code>NFTokenPage</code> invariant checks, so that certain error cases fail with a suitable error code such as <code>tecNO_SUITABLE_TOKEN_PAGE</code> instead of failing with a <code>tecINVARIANT_FAILED</code> error code. (<a href="https://github.com/ripple/rippled/pull/4155">#4155</a>)</li>
<li><b>Introduce ExpandedSignerList Amendment</b> - This amendment expands the maximum signer list size to 32 entries and allows each signer to have an optional 256-bit <code>WalletLocator</code> field containing arbitrary data. (<a href="https://github.com/ripple/rippled/pull/4097">#4097</a>)</li> <li><b>Introduce ExpandedSignerList Amendment</b> - This amendment expands the maximum signer list size to 32 entries and allows each signer to have an optional 256-bit <code>WalletLocator</code> field containing arbitrary data. (<a href="https://github.com/ripple/rippled/pull/4097">#4097</a>)</li>
<li><b>Pause online deletion rather than canceling it if the server fails health check</b> - 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. (<a href="https://github.com/ripple/rippled/pull/4139">#4139</a>)</li> <li><b>Pause online deletion rather than canceling it if the server fails health check</b> - 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. (<a href="https://github.com/ripple/rippled/pull/4139">#4139</a>)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md315"></a> <h2><a class="anchor" id="autotoc_md322"></a>
Bug Fixes and Performance Improvements</h2> Bug Fixes and Performance Improvements</h2>
<ul> <ul>
<li><b>Fix performance issues introduced in 1.9.0</b> - 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. (<a href="https://github.com/ripple/rippled/pull/4152">#4152</a>)</li> <li><b>Fix performance issues introduced in 1.9.0</b> - 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. (<a href="https://github.com/ripple/rippled/pull/4152">#4152</a>)</li>
@@ -104,13 +154,13 @@ Bug Fixes and Performance Improvements</h2>
<li><b>Fix unit test failures for DatabaseDownloader</b> - Increases a timeout in the <code>DatabaseDownloader</code> code and adjusts unit tests so that the code does not return spurious failures, and more data is logged if it does fail. (<a href="https://github.com/ripple/rippled/pull/4021">#4021</a>)</li> <li><b>Fix unit test failures for DatabaseDownloader</b> - Increases a timeout in the <code>DatabaseDownloader</code> code and adjusts unit tests so that the code does not return spurious failures, and more data is logged if it does fail. (<a href="https://github.com/ripple/rippled/pull/4021">#4021</a>)</li>
<li><b>Refactor relational database interface</b> - Improves code comments, naming, and organization of the module that interfaces with relational databases (such as the SQLite database used for tracking transaction history). (<a href="https://github.com/ripple/rippled/pull/3965">#3965</a>)</li> <li><b>Refactor relational database interface</b> - Improves code comments, naming, and organization of the module that interfaces with relational databases (such as the SQLite database used for tracking transaction history). (<a href="https://github.com/ripple/rippled/pull/3965">#3965</a>)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md316"></a> <h2><a class="anchor" id="autotoc_md323"></a>
Contributions</h2> Contributions</h2>
<h3><a class="anchor" id="autotoc_md317"></a> <h3><a class="anchor" id="autotoc_md324"></a>
GitHub</h3> GitHub</h3>
<p>The public source code repository for <code>rippled</code> is hosted on GitHub at <a href="https://github.com/ripple/rippled">https://github.com/ripple/rippled</a>.</p> <p>The public source code repository for <code>rippled</code> is hosted on GitHub at <a href="https://github.com/ripple/rippled">https://github.com/ripple/rippled</a>.</p>
<p>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.</p> <p>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.</p>
<h3><a class="anchor" id="autotoc_md318"></a> <h3><a class="anchor" id="autotoc_md325"></a>
Credits</h3> Credits</h3>
<p>The following people contributed directly to this release:</p> <p>The following people contributed directly to this release:</p>
<ul> <ul>
@@ -125,17 +175,17 @@ Credits</h3>
</ul> </ul>
<p>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: <a href="https://github.com/ripple/rippled/graphs/contributors">https://github.com/ripple/rippled/graphs/contributors</a>.</p> <p>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: <a href="https://github.com/ripple/rippled/graphs/contributors">https://github.com/ripple/rippled/graphs/contributors</a>.</p>
<p>We welcome external contributions and are excited to see the broader XRP Ledger community continue to grow and thrive.</p> <p>We welcome external contributions and are excited to see the broader XRP Ledger community continue to grow and thrive.</p>
<h1><a class="anchor" id="autotoc_md319"></a> <h1><a class="anchor" id="autotoc_md326"></a>
Change log</h1> Change log</h1>
<ul> <ul>
<li>API version 2 will now return <code>signer_lists</code> in the root of the <code>account_info</code> response, no longer nested under <code>account_data</code>.</li> <li>API version 2 will now return <code>signer_lists</code> in the root of the <code>account_info</code> response, no longer nested under <code>account_data</code>.</li>
</ul> </ul>
<h1><a class="anchor" id="autotoc_md320"></a> <h1><a class="anchor" id="autotoc_md327"></a>
Releases</h1> Releases</h1>
<h2><a class="anchor" id="autotoc_md321"></a> <h2><a class="anchor" id="autotoc_md328"></a>
Version 1.9.0</h2> Version 1.9.0</h2>
<p>This is the 1.9.0 release of <code>rippled</code>, the reference implementation of the XRP Ledger protocol. This release brings several features and improvements.</p> <p>This is the 1.9.0 release of <code>rippled</code>, the reference implementation of the XRP Ledger protocol. This release brings several features and improvements.</p>
<h3><a class="anchor" id="autotoc_md322"></a> <h3><a class="anchor" id="autotoc_md329"></a>
New and Improved Features</h3> New and Improved Features</h3>
<ul> <ul>
<li><b>Introduce NFT support (XLS020):</b> This release introduces support for non-fungible tokens, currently available to the developer community for broader review and testing. Developers can create applications that allow users to mint, transfer, and ultimately burn (if desired) NFTs on the XRP Ledger. You can try out the new NFT transactions using the <a href="https://xrpl.org/xrp-testnet-faucet.html">nft-devnet</a>. Note that some fields and error codes from earlier releases of the supporting code have been refactored for this release, shown in the Code Refactoring section, below. <a href="https://github.com/ripple/rippled/commit/70779f6850b5f33cdbb9cf4129bc1c259af0013e">70779f</a></li> <li><b>Introduce NFT support (XLS020):</b> This release introduces support for non-fungible tokens, currently available to the developer community for broader review and testing. Developers can create applications that allow users to mint, transfer, and ultimately burn (if desired) NFTs on the XRP Ledger. You can try out the new NFT transactions using the <a href="https://xrpl.org/xrp-testnet-faucet.html">nft-devnet</a>. Note that some fields and error codes from earlier releases of the supporting code have been refactored for this release, shown in the Code Refactoring section, below. <a href="https://github.com/ripple/rippled/commit/70779f6850b5f33cdbb9cf4129bc1c259af0013e">70779f</a></li>
@@ -151,10 +201,10 @@ New and Improved Features</h3>
<li><b>Improve asynchronous database handlers:</b> This commit optimizes the way asynchronous node store operations are processed, both by reducing the number of times locks are held and by minimizing the number of memory allocations and data copying. <a href="https://github.com/ripple/rippled/commit/6faaa91850d6b2eb9fbf16c1256bf7ef11ac4646">6faaa9</a></li> <li><b>Improve asynchronous database handlers:</b> This commit optimizes the way asynchronous node store operations are processed, both by reducing the number of times locks are held and by minimizing the number of memory allocations and data copying. <a href="https://github.com/ripple/rippled/commit/6faaa91850d6b2eb9fbf16c1256bf7ef11ac4646">6faaa9</a></li>
<li><b>Cleanup AcceptedLedger and AcceptedLedgerTx:</b> This commit modernizes the <code>AcceptedLedger</code> and <code>AcceptedLedgerTx</code> classes, reduces their memory footprint, and reduces unnecessary dynamic memory allocations. <a href="https://github.com/ripple/rippled/commit/8f586870917818133924bf2e11acab5321c2b588">8f5868</a></li> <li><b>Cleanup AcceptedLedger and AcceptedLedgerTx:</b> This commit modernizes the <code>AcceptedLedger</code> and <code>AcceptedLedgerTx</code> classes, reduces their memory footprint, and reduces unnecessary dynamic memory allocations. <a href="https://github.com/ripple/rippled/commit/8f586870917818133924bf2e11acab5321c2b588">8f5868</a></li>
</ul> </ul>
<h3><a class="anchor" id="autotoc_md323"></a> <h3><a class="anchor" id="autotoc_md330"></a>
Code Refactoring</h3> Code Refactoring</h3>
<p>This 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.</p> <p>This 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.</p>
<h4><a class="anchor" id="autotoc_md324"></a> <h4><a class="anchor" id="autotoc_md331"></a>
&lt;tt&gt;SField&lt;/tt&gt; name changes:</h4> &lt;tt&gt;SField&lt;/tt&gt; name changes:</h4>
<ul> <ul>
<li><code>TokenTaxon -&gt; NFTokenTaxon</code></li> <li><code>TokenTaxon -&gt; NFTokenTaxon</code></li>
@@ -170,13 +220,13 @@ Code Refactoring</h3>
<li><code>SellOffer -&gt; NFTokenSellOffer</code></li> <li><code>SellOffer -&gt; NFTokenSellOffer</code></li>
<li><code>OfferNode -&gt; NFTokenOfferNode</code></li> <li><code>OfferNode -&gt; NFTokenOfferNode</code></li>
</ul> </ul>
<h4><a class="anchor" id="autotoc_md325"></a> <h4><a class="anchor" id="autotoc_md332"></a>
RPC return labels</h4> RPC return labels</h4>
<ul> <ul>
<li><code>tokenid -&gt; nft_id</code></li> <li><code>tokenid -&gt; nft_id</code></li>
<li><code>index -&gt; nft_offer_index</code></li> <li><code>index -&gt; nft_offer_index</code></li>
</ul> </ul>
<h4><a class="anchor" id="autotoc_md326"></a> <h4><a class="anchor" id="autotoc_md333"></a>
Error codes</h4> Error codes</h4>
<ul> <ul>
<li><code>temBAD_TRANSFER_FEE -&gt; temBAD_NFTOKEN_TRANSFER_FEE</code></li> <li><code>temBAD_TRANSFER_FEE -&gt; temBAD_NFTOKEN_TRANSFER_FEE</code></li>
@@ -186,15 +236,15 @@ Error codes</h4>
<li><code>tecOFFER_TYPE_MISMATCH -&gt; tecNFTOKEN_OFFER_TYPE_MISMATCH</code></li> <li><code>tecOFFER_TYPE_MISMATCH -&gt; tecNFTOKEN_OFFER_TYPE_MISMATCH</code></li>
<li><code>tecCANT_ACCEPT_OWN_OFFER -&gt; tecCANT_ACCEPT_OWN_NFTOKEN_OFFER</code></li> <li><code>tecCANT_ACCEPT_OWN_OFFER -&gt; tecCANT_ACCEPT_OWN_NFTOKEN_OFFER</code></li>
</ul> </ul>
<h3><a class="anchor" id="autotoc_md327"></a> <h3><a class="anchor" id="autotoc_md334"></a>
Bug Fixes</h3> Bug Fixes</h3>
<ul> <ul>
<li><b>Fix deletion of orphan node store directories:</b> Orphaned node store directories should only be deleted if the proper node store directories are confirmed to exist. <a href="https://github.com/ripple/rippled/commit/06e87e0f6add5b880d647e14ab3d950decfcf416">06e87e</a></li> <li><b>Fix deletion of orphan node store directories:</b> Orphaned node store directories should only be deleted if the proper node store directories are confirmed to exist. <a href="https://github.com/ripple/rippled/commit/06e87e0f6add5b880d647e14ab3d950decfcf416">06e87e</a></li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md328"></a> <h2><a class="anchor" id="autotoc_md335"></a>
Version 1.8.5</h2> Version 1.8.5</h2>
<p>This is the 1.8.5 release of <code>rippled</code>, 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.</p> <p>This is the 1.8.5 release of <code>rippled</code>, 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.</p>
<h3><a class="anchor" id="autotoc_md329"></a> <h3><a class="anchor" id="autotoc_md336"></a>
Bug Fixes</h3> Bug Fixes</h3>
<p>This release contains the following bug fixes and under-the-hood improvements:</p> <p>This release contains the following bug fixes and under-the-hood improvements:</p>
<ul> <ul>
@@ -206,24 +256,24 @@ Bug Fixes</h3>
<li><b>Correctly add GIT_COMMIT_HASH into version string:</b> When building the server from a non-tagged release, the build files now add the commit ID in a way that follows the semantic-versioning standard, and correctly handle the case where the commit hash ID cannot be retrieved. (d23d37f)</li> <li><b>Correctly add GIT_COMMIT_HASH into version string:</b> When building the server from a non-tagged release, the build files now add the commit ID in a way that follows the semantic-versioning standard, and correctly handle the case where the commit hash ID cannot be retrieved. (d23d37f)</li>
<li><b>Update RocksDB to version 6.27.3:</b> Updates the version of RocksDB included in the server from 6.7.3 (which was released on 2020-03-18) to 6.27.3 (released 2021-12-10).</li> <li><b>Update RocksDB to version 6.27.3:</b> Updates the version of RocksDB included in the server from 6.7.3 (which was released on 2020-03-18) to 6.27.3 (released 2021-12-10).</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md330"></a> <h2><a class="anchor" id="autotoc_md337"></a>
Version 1.8.4</h2> Version 1.8.4</h2>
<p>This is the 1.8.4 release of <code>rippled</code>, the reference implementation of the XRP Ledger protocol.</p> <p>This is the 1.8.4 release of <code>rippled</code>, the reference implementation of the XRP Ledger protocol.</p>
<p>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.</p> <p>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.</p>
<h3><a class="anchor" id="autotoc_md331"></a> <h3><a class="anchor" id="autotoc_md338"></a>
Bug Fixes</h3> Bug Fixes</h3>
<ul> <ul>
<li><b>Adjust mutex scope in <code>walkMapParallel</code></b>: 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.</li> <li><b>Adjust mutex scope in <code>walkMapParallel</code></b>: 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.</li>
<li><b>Adjust pathfinding configuration defaults</b>: This commit adjusts the default configuration of the pathfinding engine, to account for the size of the XRP Ledger mainnet. Unless explicitly overriden, the changes mean that pathfinding operations will return fewer, shallower paths than previous releases.</li> <li><b>Adjust pathfinding configuration defaults</b>: This commit adjusts the default configuration of the pathfinding engine, to account for the size of the XRP Ledger mainnet. Unless explicitly overriden, the changes mean that pathfinding operations will return fewer, shallower paths than previous releases.</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md332"></a> <h2><a class="anchor" id="autotoc_md339"></a>
Version 1.8.3</h2> Version 1.8.3</h2>
<p>This is the 1.8.3 release of <code>rippled</code>, the reference implementation of the XRP Ledger protocol.</p> <p>This is the 1.8.3 release of <code>rippled</code>, the reference implementation of the XRP Ledger protocol.</p>
<p>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.</p> <p>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.</p>
<h3><a class="anchor" id="autotoc_md333"></a> <h3><a class="anchor" id="autotoc_md340"></a>
Summary of Issues</h3> Summary of Issues</h3>
<p>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.</p> <p>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.</p>
<h3><a class="anchor" id="autotoc_md334"></a> <h3><a class="anchor" id="autotoc_md341"></a>
Bug Fixes</h3> Bug Fixes</h3>
<ul> <ul>
<li><p class="startli"><b>Parallel ledger loader &amp; I/O performance improvements</b>: 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, <code>rippled</code> 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 <code>[node_db]</code> stanza:</p> <li><p class="startli"><b>Parallel ledger loader &amp; I/O performance improvements</b>: 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, <code>rippled</code> 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 <code>[node_db]</code> stanza:</p>
@@ -237,14 +287,14 @@ Bug Fixes</h3>
<li><b>Adjust the number of concurrent ledger data jobs</b>: Processing a large amount of data at once can effectively bottleneck a server's I/O subsystem. This commits helps optimize I/O performance by controlling how many jobs can concurrently process ledger data.</li> <li><b>Adjust the number of concurrent ledger data jobs</b>: Processing a large amount of data at once can effectively bottleneck a server's I/O subsystem. This commits helps optimize I/O performance by controlling how many jobs can concurrently process ledger data.</li>
<li><b>Two small SHAMapSync improvements</b>: This commit makes minor changes to optimize the way memory is used and control the amount of background I/O performed when attempting to fetch missing <code>SHAMap</code> nodes.</li> <li><b>Two small SHAMapSync improvements</b>: This commit makes minor changes to optimize the way memory is used and control the amount of background I/O performed when attempting to fetch missing <code>SHAMap</code> nodes.</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md335"></a> <h2><a class="anchor" id="autotoc_md342"></a>
Version 1.8.2</h2> Version 1.8.2</h2>
<p>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.</p> <p>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.</p>
<h3><a class="anchor" id="autotoc_md336"></a> <h3><a class="anchor" id="autotoc_md343"></a>
Summary of Issues</h3> Summary of Issues</h3>
<p>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.</p> <p>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.</p>
<p>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.</p> <p>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.</p>
<h3><a class="anchor" id="autotoc_md337"></a> <h3><a class="anchor" id="autotoc_md344"></a>
Bug Fixes</h3> Bug Fixes</h3>
<ul> <ul>
<li><b>Address elevated transaction fees</b>: This change addresses the full queue problems in two ways. First, it puts deferred transactions directly into the open ledger, rather than transaction queue. This reverts a subset of the changes from <a href="https://github.com/ximinez/rippled/commit/62127d725d801641bfaa61dee7d88c95e48820c5">ximinez@62127d7</a>. A transaction that is in the open ledger but doesn't get validated should stay in the open ledger so that it can be proposed again right away. Second, it changes the order in which transactions are pulled from the transaction queue to increase the overlap in servers' initial transaction consensus proposals. Like the old rules, transactions paying higher fee levels are selected first. Unlike the old rules, transactions paying the same fee level are ordered by transaction ID / hash ascending. (Previously, transactions paying the same fee level were unsorted, resulting in each server having a different order.)</li> <li><b>Address elevated transaction fees</b>: This change addresses the full queue problems in two ways. First, it puts deferred transactions directly into the open ledger, rather than transaction queue. This reverts a subset of the changes from <a href="https://github.com/ximinez/rippled/commit/62127d725d801641bfaa61dee7d88c95e48820c5">ximinez@62127d7</a>. A transaction that is in the open ledger but doesn't get validated should stay in the open ledger so that it can be proposed again right away. Second, it changes the order in which transactions are pulled from the transaction queue to increase the overlap in servers' initial transaction consensus proposals. Like the old rules, transactions paying higher fee levels are selected first. Unlike the old rules, transactions paying the same fee level are ordered by transaction ID / hash ascending. (Previously, transactions paying the same fee level were unsorted, resulting in each server having a different order.)</li>
@@ -258,10 +308,10 @@ Bug Fixes</h3>
<li><b>Improve handling of HTTP X-Forwarded-For and Forwarded headers</b>: Fixes the way the server handles IPv6 addresses in these HTTP headers. (<a href="https://github.com/ripple/rippled/pull/4009">#4009</a>, <a href="https://github.com/ripple/rippled/pull/4030">#4030</a>)</li> <li><b>Improve handling of HTTP X-Forwarded-For and Forwarded headers</b>: Fixes the way the server handles IPv6 addresses in these HTTP headers. (<a href="https://github.com/ripple/rippled/pull/4009">#4009</a>, <a href="https://github.com/ripple/rippled/pull/4030">#4030</a>)</li>
<li><b>Other minor improvements to logging and Reporting Mode.</b></li> <li><b>Other minor improvements to logging and Reporting Mode.</b></li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md338"></a> <h2><a class="anchor" id="autotoc_md345"></a>
Version 1.8.0</h2> Version 1.8.0</h2>
<p>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.</p> <p>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.</p>
<h3><a class="anchor" id="autotoc_md339"></a> <h3><a class="anchor" id="autotoc_md346"></a>
New and Improved Features</h3> New and Improved Features</h3>
<ul> <ul>
<li><b>Improve History Sharding</b>: Shards of ledger history are now assembled in a deterministic way so that any server can make a binary-identical shard for a given range of ledgers. This makes it possible to retrieve a shard from multiple sources in parallel, then verify its integrity by comparing checksums with peers' checksums for the same shard. Additionally, there's a new admin RPC command to import ledger history from the shard store, and the crawl_shards command has been expanded with more info. (<a href="https://github.com/ripple/rippled/issues/2688">#2688</a>, <a href="https://github.com/ripple/rippled/pull/3726">#3726</a>, <a href="https://github.com/ripple/rippled/pull/3875">#3875</a>)</li> <li><b>Improve History Sharding</b>: Shards of ledger history are now assembled in a deterministic way so that any server can make a binary-identical shard for a given range of ledgers. This makes it possible to retrieve a shard from multiple sources in parallel, then verify its integrity by comparing checksums with peers' checksums for the same shard. Additionally, there's a new admin RPC command to import ledger history from the shard store, and the crawl_shards command has been expanded with more info. (<a href="https://github.com/ripple/rippled/issues/2688">#2688</a>, <a href="https://github.com/ripple/rippled/pull/3726">#3726</a>, <a href="https://github.com/ripple/rippled/pull/3875">#3875</a>)</li>
@@ -276,7 +326,7 @@ New and Improved Features</h3>
<li><b>More fields in the <code>validations</code> stream:</b> The <code>validations</code> 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. (<a href="https://github.com/ripple/rippled/pull/3865">#3865</a>)</li> <li><b>More fields in the <code>validations</code> stream:</b> The <code>validations</code> 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. (<a href="https://github.com/ripple/rippled/pull/3865">#3865</a>)</li>
<li><b>Reporting mode supports <code>validations</code> and <code>manifests</code> streams:</b> 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 <code>reportingUnsupported</code>. (<a href="https://github.com/ripple/rippled/pull/3905">#3905</a>)</li> <li><b>Reporting mode supports <code>validations</code> and <code>manifests</code> streams:</b> 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 <code>reportingUnsupported</code>. (<a href="https://github.com/ripple/rippled/pull/3905">#3905</a>)</li>
</ul> </ul>
<h3><a class="anchor" id="autotoc_md340"></a> <h3><a class="anchor" id="autotoc_md347"></a>
Bug Fixes</h3> Bug Fixes</h3>
<ul> <ul>
<li><b>Clarify the safety of NetClock::time_point arithmetic</b>: * NetClock::rep is uint32_t and can be error-prone when used with subtraction. * Fixes <a href="https://github.com/ripple/rippled/pull/3656">#3656</a></li> <li><b>Clarify the safety of NetClock::time_point arithmetic</b>: * NetClock::rep is uint32_t and can be error-prone when used with subtraction. * Fixes <a href="https://github.com/ripple/rippled/pull/3656">#3656</a></li>
@@ -290,26 +340,26 @@ Bug Fixes</h3>
<li><b>Simplify SHAMapItem construction</b>: The existing class offered several constructors which were mostly unnecessary. This eliminates all existing constructors and introduces a single new one, taking a <code>Slice</code>. The internal buffer is switched from <code><a class="elRef" href="http://en.cppreference.com/w/cpp/container/vector.html" title="STL class.">std::vector</a></code> to <code>Buffer</code> to save a minimum of 8 bytes (plus the buffer slack that is inherent in <code><a class="elRef" href="http://en.cppreference.com/w/cpp/container/vector.html" title="STL class.">std::vector</a></code>) per SHAMapItem instance.</li> <li><b>Simplify SHAMapItem construction</b>: The existing class offered several constructors which were mostly unnecessary. This eliminates all existing constructors and introduces a single new one, taking a <code>Slice</code>. The internal buffer is switched from <code><a class="elRef" href="http://en.cppreference.com/w/cpp/container/vector.html" title="STL class.">std::vector</a></code> to <code>Buffer</code> to save a minimum of 8 bytes (plus the buffer slack that is inherent in <code><a class="elRef" href="http://en.cppreference.com/w/cpp/container/vector.html" title="STL class.">std::vector</a></code>) per SHAMapItem instance.</li>
<li><b>Redesign stoppable objects</b>: Stoppable is no longer an abstract base class, but a pattern, modeled after the well-understood <code><a class="elRef" href="http://en.cppreference.com/w/cpp/thread/thread.html" title="STL class.">std::thread</a></code>. 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.</li> <li><b>Redesign stoppable objects</b>: Stoppable is no longer an abstract base class, but a pattern, modeled after the well-understood <code><a class="elRef" href="http://en.cppreference.com/w/cpp/thread/thread.html" title="STL class.">std::thread</a></code>. 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.</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md341"></a> <h2><a class="anchor" id="autotoc_md348"></a>
Version 1.7.3</h2> Version 1.7.3</h2>
<p>This is the 1.7.3 release of <code>rippled</code>, 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 <code>NegativeUNL</code> amendment, which corresponds to the feature which was introduced with the 1.6.0 release.</p> <p>This is the 1.7.3 release of <code>rippled</code>, 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 <code>NegativeUNL</code> amendment, which corresponds to the feature which was introduced with the 1.6.0 release.</p>
<h2><a class="anchor" id="autotoc_md342"></a> <h2><a class="anchor" id="autotoc_md349"></a>
Action Required</h2> Action Required</h2>
<p>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 <code>NegativeUNL</code> amendment may gain a majority, at which point a two week activation countdown will begin. If the <code>NegativeUNL</code> amendment activates, servers running versions of <code>rippled</code> prior to 1.7.3 will become <a href="https://xrpl.org/amendments.html#amendment-blocked">amendment blocked</a>.</p> <p>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 <code>NegativeUNL</code> amendment may gain a majority, at which point a two week activation countdown will begin. If the <code>NegativeUNL</code> amendment activates, servers running versions of <code>rippled</code> prior to 1.7.3 will become <a href="https://xrpl.org/amendments.html#amendment-blocked">amendment blocked</a>.</p>
<h3><a class="anchor" id="autotoc_md343"></a> <h3><a class="anchor" id="autotoc_md350"></a>
Bug Fixes</h3> Bug Fixes</h3>
<ul> <ul>
<li><b>Improve SLE usage in check cashing</b>: Fixes a situation which could result in the incorrect use of SLEs.</li> <li><b>Improve SLE usage in check cashing</b>: Fixes a situation which could result in the incorrect use of SLEs.</li>
<li><b>Address OOB in base58 decoder</b>: Corrects a technical flaw that could allow an out-of-bounds memory read in the Base58 decoder.</li> <li><b>Address OOB in base58 decoder</b>: Corrects a technical flaw that could allow an out-of-bounds memory read in the Base58 decoder.</li>
<li><b>Add <code>NegativeUNL</code> as a supported amendment</b>: Introduces an amendment for the Negative UNL feature introduced in <code>rippled</code> 1.6.0.</li> <li><b>Add <code>NegativeUNL</code> as a supported amendment</b>: Introduces an amendment for the Negative UNL feature introduced in <code>rippled</code> 1.6.0.</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md344"></a> <h2><a class="anchor" id="autotoc_md351"></a>
Version 1.7.2</h2> Version 1.7.2</h2>
<p>This the 1.7.2 release of rippled, the reference server implementation of the XRP Ledger protocol. This release protects against the security issue <a href="https://www.openssl.org/news/secadv/20210325.txt">CVE-2021-3499</a> 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.</p> <p>This the 1.7.2 release of rippled, the reference server implementation of the XRP Ledger protocol. This release protects against the security issue <a href="https://www.openssl.org/news/secadv/20210325.txt">CVE-2021-3499</a> 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.</p>
<h2><a class="anchor" id="autotoc_md345"></a> <h2><a class="anchor" id="autotoc_md352"></a>
Action Required</h2> Action Required</h2>
<p>This release introduces a new amendment to the XRP Ledger protocol: <code>fixRmSmallIncreasedQOffers</code>. This amendments is now open for voting according to the XRP Ledger's amendment process, which enables protocol changes following two weeks of &gt;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.</p> <p>This release introduces a new amendment to the XRP Ledger protocol: <code>fixRmSmallIncreasedQOffers</code>. This amendments is now open for voting according to the XRP Ledger's amendment process, which enables protocol changes following two weeks of &gt;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.</p>
<h3><a class="anchor" id="autotoc_md346"></a> <h3><a class="anchor" id="autotoc_md353"></a>
Bug Fixes</h3> Bug Fixes</h3>
<ul> <ul>
<li><b>fixRmSmallIncreasedQOffers Amendment:</b> This amendment fixes an issue where certain small offers can be left at the tip of an order book without being consumed or removed when appropriate and causes some payments and Offers to fail when they should have succeeded <a href="https://github.com/ripple/rippled/pull/3827">(#3827)</a>.</li> <li><b>fixRmSmallIncreasedQOffers Amendment:</b> This amendment fixes an issue where certain small offers can be left at the tip of an order book without being consumed or removed when appropriate and causes some payments and Offers to fail when they should have succeeded <a href="https://github.com/ripple/rippled/pull/3827">(#3827)</a>.</li>
@@ -320,13 +370,13 @@ Bug Fixes</h3>
<li><b>Properly encode metadata from tx RPC command:</b> Fixes a problem where transaction metadata in the tx API method response would be in JSON format even when binary was requested <a href="https://github.com/ripple/rippled/pull/3843/commits/73116297aa94c4acbfc74c2593d1aa2323b4cc52">(7311629)</a>.</li> <li><b>Properly encode metadata from tx RPC command:</b> Fixes a problem where transaction metadata in the tx API method response would be in JSON format even when binary was requested <a href="https://github.com/ripple/rippled/pull/3843/commits/73116297aa94c4acbfc74c2593d1aa2323b4cc52">(7311629)</a>.</li>
<li><b>Updates to Windows builds:</b> When building on Windows, use vcpkg 2021 by default and add compatibility with MSVC 2019 <a href="https://github.com/ripple/rippled/pull/3843/commits/36fe1966c3cd37f668693b5d9910fab59c3f8b1f">(36fe196)</a>, <a href="https://github.com/ripple/rippled/pull/3843/commits/30fd45890b1d3d5f372a2091d1397b1e8e29d2ca">(30fd458)</a>.</li> <li><b>Updates to Windows builds:</b> When building on Windows, use vcpkg 2021 by default and add compatibility with MSVC 2019 <a href="https://github.com/ripple/rippled/pull/3843/commits/36fe1966c3cd37f668693b5d9910fab59c3f8b1f">(36fe196)</a>, <a href="https://github.com/ripple/rippled/pull/3843/commits/30fd45890b1d3d5f372a2091d1397b1e8e29d2ca">(30fd458)</a>.</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md347"></a> <h2><a class="anchor" id="autotoc_md354"></a>
Version 1.7.0</h2> Version 1.7.0</h2>
<p>Ripple has released version 1.7.0 of <code>rippled</code>, the reference server implementation of the XRP Ledger protocol. This release <a href="https://blog.ripplex.io/how-ripples-c-team-cut-rippleds-memory-footprint-down-to-size/">significantly improves memory usage</a>, introduces a protocol amendment to allow out-of-order transaction execution with Tickets, and brings several other features and improvements.</p> <p>Ripple has released version 1.7.0 of <code>rippled</code>, the reference server implementation of the XRP Ledger protocol. This release <a href="https://blog.ripplex.io/how-ripples-c-team-cut-rippleds-memory-footprint-down-to-size/">significantly improves memory usage</a>, introduces a protocol amendment to allow out-of-order transaction execution with Tickets, and brings several other features and improvements.</p>
<h2><a class="anchor" id="autotoc_md348"></a> <h2><a class="anchor" id="autotoc_md355"></a>
Upgrading (SPECIAL ACTION REQUIRED)</h2> Upgrading (SPECIAL ACTION REQUIRED)</h2>
<p>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. </p> <p>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. </p>
<h3><a class="anchor" id="autotoc_md349"></a> <h3><a class="anchor" id="autotoc_md356"></a>
Red Hat Enterprise Linux / CentOS</h3> Red Hat Enterprise Linux / CentOS</h3>
<p>Perform a <a href="https://xrpl.org/update-rippled-manually-on-centos-rhel.html">manual upgrade</a>. When prompted, confirm that the key's fingerprint matches the following example, then press <code>y</code> to accept the updated key:</p> <p>Perform a <a href="https://xrpl.org/update-rippled-manually-on-centos-rhel.html">manual upgrade</a>. When prompted, confirm that the key's fingerprint matches the following example, then press <code>y</code> to accept the updated key:</p>
<div class="fragment"><div class="line">$ sudo yum install rippled</div> <div class="fragment"><div class="line">$ sudo yum install rippled</div>
@@ -343,14 +393,14 @@ Red Hat Enterprise Linux / CentOS</h3>
<div class="line">Fingerprint: c001 0ec2 05b3 5a33 10dc 90de 395f 97ff ccaf d9a2</div> <div class="line">Fingerprint: c001 0ec2 05b3 5a33 10dc 90de 395f 97ff ccaf d9a2</div>
<div class="line">From : https://repos.ripple.com/repos/rippled-rpm/nightly/repodata/repomd.xml.key</div> <div class="line">From : https://repos.ripple.com/repos/rippled-rpm/nightly/repodata/repomd.xml.key</div>
<div class="line">Is this ok [y/N]: y</div> <div class="line">Is this ok [y/N]: y</div>
</div><!-- fragment --><h3><a class="anchor" id="autotoc_md350"></a> </div><!-- fragment --><h3><a class="anchor" id="autotoc_md357"></a>
Ubuntu / Debian</h3> Ubuntu / Debian</h3>
<p>Download and trust the updated public key, then perform a <a href="https://xrpl.org/update-rippled-manually-on-ubuntu.html">manual upgrade</a> as follows:</p> <p>Download and trust the updated public key, then perform a <a href="https://xrpl.org/update-rippled-manually-on-ubuntu.html">manual upgrade</a> as follows:</p>
<div class="fragment"><div class="line">wget -q -O - &quot;https://repos.ripple.com/repos/api/gpg/key/public&quot; | \</div> <div class="fragment"><div class="line">wget -q -O - &quot;https://repos.ripple.com/repos/api/gpg/key/public&quot; | \</div>
<div class="line"> sudo apt-key add -</div> <div class="line"> sudo apt-key add -</div>
<div class="line">sudo apt -y update</div> <div class="line">sudo apt -y update</div>
<div class="line">sudo apt -y install rippled</div> <div class="line">sudo apt -y install rippled</div>
</div><!-- fragment --><h3><a class="anchor" id="autotoc_md351"></a> </div><!-- fragment --><h3><a class="anchor" id="autotoc_md358"></a>
New and Improved Features</h3> New and Improved Features</h3>
<ul> <ul>
<li><b>Rework deferred node logic and async fetch behavior:</b> This change significantly improves ledger sync and fetch times while reducing memory consumption. (<a href="https://blog.ripplex.io/how-ripples-c-team-cut-rippleds-memory-footprint-down-to-size/">https://blog.ripplex.io/how-ripples-c-team-cut-rippleds-memory-footprint-down-to-size/</a>)</li> <li><b>Rework deferred node logic and async fetch behavior:</b> This change significantly improves ledger sync and fetch times while reducing memory consumption. (<a href="https://blog.ripplex.io/how-ripples-c-team-cut-rippleds-memory-footprint-down-to-size/">https://blog.ripplex.io/how-ripples-c-team-cut-rippleds-memory-footprint-down-to-size/</a>)</li>
@@ -369,7 +419,7 @@ New and Improved Features</h3>
<li><b>Improvements to shard downloading:</b> Previously the download_shard command could only load shards over HTTPS. Compressed shards can now also be downloaded over plain HTTP. The server fully checks the data for integrity and consistency, so the encryption is not strictly necessary. When initiating multiple shard downloads, the server now returns an error if there is not enough space to store all the shards currently being downloaded.</li> <li><b>Improvements to shard downloading:</b> Previously the download_shard command could only load shards over HTTPS. Compressed shards can now also be downloaded over plain HTTP. The server fully checks the data for integrity and consistency, so the encryption is not strictly necessary. When initiating multiple shard downloads, the server now returns an error if there is not enough space to store all the shards currently being downloaded.</li>
<li><b>The manifest command is now public:</b> The manifest API method returns public information about a given validator. The required permissions have been changed so it is now part of the public API.</li> <li><b>The manifest command is now public:</b> The manifest API method returns public information about a given validator. The required permissions have been changed so it is now part of the public API.</li>
</ul> </ul>
<h3><a class="anchor" id="autotoc_md352"></a> <h3><a class="anchor" id="autotoc_md359"></a>
Bug Fixes</h3> Bug Fixes</h3>
<ul> <ul>
<li><b>Implement sticky DNS resolution for validator list retrieval:</b> When attempting to load a validator list from a configured site, attempt to reuse the last IP that was successfully used if that IP is still present in the DNS response. (<a href="https://github.com/ripple/rippled/issues/3494">https://github.com/ripple/rippled/issues/3494</a>).</li> <li><b>Implement sticky DNS resolution for validator list retrieval:</b> When attempting to load a validator list from a configured site, attempt to reuse the last IP that was successfully used if that IP is still present in the DNS response. (<a href="https://github.com/ripple/rippled/issues/3494">https://github.com/ripple/rippled/issues/3494</a>).</li>
@@ -386,10 +436,10 @@ Bug Fixes</h3>
<li><b>Fixed a potential thread deadlock with history sharding.</b> ( <a href="https://github.com/ripple/rippled/pull/3683">https://github.com/ripple/rippled/pull/3683</a> )</li> <li><b>Fixed a potential thread deadlock with history sharding.</b> ( <a href="https://github.com/ripple/rippled/pull/3683">https://github.com/ripple/rippled/pull/3683</a> )</li>
<li><b>Various fixes to typos and comments, refactoring, and build system improvements</b></li> <li><b>Various fixes to typos and comments, refactoring, and build system improvements</b></li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md353"></a> <h2><a class="anchor" id="autotoc_md360"></a>
Version 1.6.0</h2> Version 1.6.0</h2>
<p>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.</p> <p>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.</p>
<h3><a class="anchor" id="autotoc_md354"></a> <h3><a class="anchor" id="autotoc_md361"></a>
New and Improved Features</h3> New and Improved Features</h3>
<ul> <ul>
<li>Initial implementation of Negative UNL functionality: This change can improve the liveness of the network during periods of network instability, by allowing servers to track which validators are temporarily offline and to adjust quorum calculations to match. This change requires an amendment, but the amendment is not in the <b>1.6.0</b> release. Ripple expects to run extensive public testing for Negative UNL functionality on the Devnet in the coming weeks. If public testing satisfies all requirements across security, reliability, stability, and performance, then the amendment could be included in a version 2.0 release. [<a href="https://github.com/ripple/rippled/pull/3380">#3380</a>]</li> <li>Initial implementation of Negative UNL functionality: This change can improve the liveness of the network during periods of network instability, by allowing servers to track which validators are temporarily offline and to adjust quorum calculations to match. This change requires an amendment, but the amendment is not in the <b>1.6.0</b> release. Ripple expects to run extensive public testing for Negative UNL functionality on the Devnet in the coming weeks. If public testing satisfies all requirements across security, reliability, stability, and performance, then the amendment could be included in a version 2.0 release. [<a href="https://github.com/ripple/rippled/pull/3380">#3380</a>]</li>
@@ -405,7 +455,7 @@ New and Improved Features</h3>
<li>Various Build and CI Improvements including updates to RocksDB 6.7.3 [<a href="https://github.com/ripple/rippled/pull/3356">#3356</a>], NuDB 2.0.3 [<a href="https://github.com/ripple/rippled/pull/3437">#3437</a>], adjusting CMake settings so that rippled can be built as a submodule [<a href="https://github.com/ripple/rippled/pull/3449">#3449</a>], and adding Travis CI settings for Ubuntu Bionic Beaver [<a href="https://github.com/ripple/rippled/pull/3319">#3319</a>].</li> <li>Various Build and CI Improvements including updates to RocksDB 6.7.3 [<a href="https://github.com/ripple/rippled/pull/3356">#3356</a>], NuDB 2.0.3 [<a href="https://github.com/ripple/rippled/pull/3437">#3437</a>], adjusting CMake settings so that rippled can be built as a submodule [<a href="https://github.com/ripple/rippled/pull/3449">#3449</a>], and adding Travis CI settings for Ubuntu Bionic Beaver [<a href="https://github.com/ripple/rippled/pull/3319">#3319</a>].</li>
<li>Better documentation in the config file for online deletion and database tuning. [<a href="https://github.com/ripple/rippled/pull/3429">#3429</a>]</li> <li>Better documentation in the config file for online deletion and database tuning. [<a href="https://github.com/ripple/rippled/pull/3429">#3429</a>]</li>
</ul> </ul>
<h3><a class="anchor" id="autotoc_md355"></a> <h3><a class="anchor" id="autotoc_md362"></a>
Bug Fixes</h3> Bug Fixes</h3>
<ul> <ul>
<li>Fix the 14 day timer to enable amendment to start at the correct quorum size [<a href="https://github.com/ripple/rippled/pull/3396">#3396</a>]</li> <li>Fix the 14 day timer to enable amendment to start at the correct quorum size [<a href="https://github.com/ripple/rippled/pull/3396">#3396</a>]</li>
@@ -420,7 +470,7 @@ Bug Fixes</h3>
<li>Add the <code>ledger_cleaner</code> command to rippled command line help [<a href="https://github.com/ripple/rippled/pull/3305">#3305</a>]</li> <li>Add the <code>ledger_cleaner</code> command to rippled command line help [<a href="https://github.com/ripple/rippled/pull/3305">#3305</a>]</li>
<li>Various typo and comments fixes.</li> <li>Various typo and comments fixes.</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md356"></a> <h2><a class="anchor" id="autotoc_md363"></a>
Version 1.5.0</h2> Version 1.5.0</h2>
<p>The <code>rippled</code> 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 <code>validator_info</code> and <code>manifest</code>, augmented <code>submit</code> method, improved <code>tx</code> method response, improved command line parsing, improved handshake protocol, improved package building and various other minor bug fixes and improvements.</p> <p>The <code>rippled</code> 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 <code>validator_info</code> and <code>manifest</code>, augmented <code>submit</code> method, improved <code>tx</code> method response, improved command line parsing, improved handshake protocol, improved package building and various other minor bug fixes and improvements.</p>
<p>This release also introduces two new amendments: <code>fixQualityUpperBound</code> and <code>RequireFullyCanonicalSig</code>.</p> <p>This release also introduces two new amendments: <code>fixQualityUpperBound</code> and <code>RequireFullyCanonicalSig</code>.</p>
@@ -445,7 +495,7 @@ Version 1.5.0</h2>
<li>Remove unused <code>Beast</code> code. <a href="https://github.com/ripple/rippled/commit/172ead822159a3c1f9b73217da4316df48851ab6"><code>172ead822</code></a></li> <li>Remove unused <code>Beast</code> code. <a href="https://github.com/ripple/rippled/commit/172ead822159a3c1f9b73217da4316df48851ab6"><code>172ead822</code></a></li>
<li>Lag ratchet code fix to use proper ephemeral public keys instead of the long-term master public keys.<a href="https://github.com/ripple/rippled/commit/6529d3e6f7333fc5226e5aa9ae65f834cb93dfe5"><code>6529d3e6f</code></a></li> <li>Lag ratchet code fix to use proper ephemeral public keys instead of the long-term master public keys.<a href="https://github.com/ripple/rippled/commit/6529d3e6f7333fc5226e5aa9ae65f834cb93dfe5"><code>6529d3e6f</code></a></li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md357"></a> <h2><a class="anchor" id="autotoc_md364"></a>
Version 1.4.0</h2> Version 1.4.0</h2>
<p>The <code>rippled</code> 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 <a href="https://en.wikipedia.org/wiki/C%2B%2B17">C++17</a> and <a href="https://www.boost.org/users/history/version_1_71_0.html">Boost 1.71</a>. Finally, this release removes the code for the <code>SHAMapV2</code> amendment which failed to gain majority support and has been obsoleted by other improvements.</p> <p>The <code>rippled</code> 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 <a href="https://en.wikipedia.org/wiki/C%2B%2B17">C++17</a> and <a href="https://www.boost.org/users/history/version_1_71_0.html">Boost 1.71</a>. Finally, this release removes the code for the <code>SHAMapV2</code> amendment which failed to gain majority support and has been obsoleted by other improvements.</p>
<p><b>New and Updated Features</b></p><ul> <p><b>New and Updated Features</b></p><ul>
@@ -463,7 +513,7 @@ Version 1.4.0</h2>
<li>Properly update the <code>server_state</code> when a server detects a disagreement between itself and the network.</li> <li>Properly update the <code>server_state</code> when a server detects a disagreement between itself and the network.</li>
<li>Allow Ed25519 keys to be used with the <code>channel_authorize</code> command.</li> <li>Allow Ed25519 keys to be used with the <code>channel_authorize</code> command.</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md358"></a> <h2><a class="anchor" id="autotoc_md365"></a>
Version 1.3.1</h2> Version 1.3.1</h2>
<p>The <code>rippled</code> 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.</p> <p>The <code>rippled</code> 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.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
@@ -472,7 +522,7 @@ Version 1.3.1</h2>
<li>Add a LogicError when a deadlock is detected (355a7b04)</li> <li>Add a LogicError when a deadlock is detected (355a7b04)</li>
<li>Improve logging during process startup (7c24f7b1)</li> <li>Improve logging during process startup (7c24f7b1)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md359"></a> <h2><a class="anchor" id="autotoc_md366"></a>
Version 1.3.0</h2> Version 1.3.0</h2>
<p>The <code>rippled</code> 1.3.0 release introduces several new features and overall improvements to the codebase, including the <code>fixMasterKeyAsRegularKey</code> 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.</p> <p>The <code>rippled</code> 1.3.0 release introduces several new features and overall improvements to the codebase, including the <code>fixMasterKeyAsRegularKey</code> 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.</p>
<p><b>New and Updated Features</b></p><ul> <p><b>New and Updated Features</b></p><ul>
@@ -484,7 +534,7 @@ Version 1.3.0</h2>
<li>Improve ledger trie ancestry tracking to reduce unnecessary error messages.</li> <li>Improve ledger trie ancestry tracking to reduce unnecessary error messages.</li>
<li>More efficient detection of dry paths in the payment engine. Although not a transaction-breaking change, this should reduce spurious error messages in the log files.</li> <li>More efficient detection of dry paths in the payment engine. Although not a transaction-breaking change, this should reduce spurious error messages in the log files.</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md360"></a> <h2><a class="anchor" id="autotoc_md367"></a>
Version 1.2.4</h2> Version 1.2.4</h2>
<p>The <code>rippled</code> 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.</p> <p>The <code>rippled</code> 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.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
@@ -494,7 +544,7 @@ Version 1.2.4</h2>
<li>Use public keys when routing shard crawl requests</li> <li>Use public keys when routing shard crawl requests</li>
<li>Enforce a 20s timeout when making validator list requests (RIPD-1737)</li> <li>Enforce a 20s timeout when making validator list requests (RIPD-1737)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md361"></a> <h2><a class="anchor" id="autotoc_md368"></a>
Version 1.2.3</h2> Version 1.2.3</h2>
<p>The <code>rippled</code> 1.2.3 release corrects a technical flaw which in some circumstances can cause a null pointer dereference that can crash the server.</p> <p>The <code>rippled</code> 1.2.3 release corrects a technical flaw which in some circumstances can cause a null pointer dereference that can crash the server.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
@@ -503,7 +553,7 @@ Version 1.2.3</h2>
<ul> <ul>
<li>Fix a technical flaw which in some circumstances can cause a null pointer dereference that can crash the server.</li> <li>Fix a technical flaw which in some circumstances can cause a null pointer dereference that can crash the server.</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md362"></a> <h2><a class="anchor" id="autotoc_md369"></a>
Version 1.2.2</h2> Version 1.2.2</h2>
<p>The <code>rippled</code> 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.</p> <p>The <code>rippled</code> 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.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
@@ -512,7 +562,7 @@ Version 1.2.2</h2>
<ul> <ul>
<li>Fix a technical flaw in the fee escalation engine which could cause some fee metrics to be calculated incorrectly (4c06b3f86)</li> <li>Fix a technical flaw in the fee escalation engine which could cause some fee metrics to be calculated incorrectly (4c06b3f86)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md363"></a> <h2><a class="anchor" id="autotoc_md370"></a>
Version 1.2.1</h2> Version 1.2.1</h2>
<p>The <code>rippled</code> 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.</p> <p>The <code>rippled</code> 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.</p>
<p>The release also adds the <code>delivered_amount</code> field to more responses to simplify the handling of payment or check cashing transactions.</p> <p>The release also adds the <code>delivered_amount</code> field to more responses to simplify the handling of payment or check cashing transactions.</p>
@@ -525,7 +575,7 @@ Version 1.2.1</h2>
<li>Display validator status only in response to admin requests (2d6a518a)</li> <li>Display validator status only in response to admin requests (2d6a518a)</li>
<li>Add the <code>delivered_amount</code> to more RPC commands (f2756914)</li> <li>Add the <code>delivered_amount</code> to more RPC commands (f2756914)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md364"></a> <h2><a class="anchor" id="autotoc_md371"></a>
Version 1.2.0</h2> Version 1.2.0</h2>
<p>The <code>rippled</code> 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, <code>rippled</code> 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.</p> <p>The <code>rippled</code> 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, <code>rippled</code> 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.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
@@ -553,7 +603,7 @@ Version 1.2.0</h2>
<li>Eliminate potential undefined behavior (c71eb45)</li> <li>Eliminate potential undefined behavior (c71eb45)</li>
<li>Add safe_cast to sure no overflow in casts between enums and integral types (a7e4541)</li> <li>Add safe_cast to sure no overflow in casts between enums and integral types (a7e4541)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md365"></a> <h2><a class="anchor" id="autotoc_md372"></a>
Version 1.1.2</h2> Version 1.1.2</h2>
<p>The <code>rippled</code> 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.</p> <p>The <code>rippled</code> 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.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
@@ -563,7 +613,7 @@ Version 1.1.2</h2>
<li>Properly bypass connection limits for cluster peers (#2795, #2796)</li> <li>Properly bypass connection limits for cluster peers (#2795, #2796)</li>
<li>Improve preferred ledger calculation (#2784)</li> <li>Improve preferred ledger calculation (#2784)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md366"></a> <h2><a class="anchor" id="autotoc_md373"></a>
Version 1.1.1</h2> Version 1.1.1</h2>
<p>The <code>rippled</code> 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</p> <p>The <code>rippled</code> 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</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
@@ -575,7 +625,7 @@ Version 1.1.1</h2>
<ul> <ul>
<li>Properly handle expired validator lists when validating (#2734)</li> <li>Properly handle expired validator lists when validating (#2734)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md367"></a> <h2><a class="anchor" id="autotoc_md374"></a>
Version 1.1.0</h2> Version 1.1.0</h2>
<p>The <code>rippled</code> 1.1.0 release release includes the <code>DepositPreAuth</code> amendment, which combined with the previously released <code>DepositAuth</code> 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 (<code>fix1515</code> amendment), deprecates support for the <code>sign</code> and <code>sign_for</code> commands from the rippled API and improves invariant checking for enhanced security.</p> <p>The <code>rippled</code> 1.1.0 release release includes the <code>DepositPreAuth</code> amendment, which combined with the previously released <code>DepositAuth</code> 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 (<code>fix1515</code> amendment), deprecates support for the <code>sign</code> and <code>sign_for</code> commands from the rippled API and improves invariant checking for enhanced security.</p>
<p>Ripple recommends that all server operators upgrade to XRP Ledger version 1.1.0 by Thursday, 2018-09-27, to ensure service continuity.</p> <p>Ripple recommends that all server operators upgrade to XRP Ledger version 1.1.0 by Thursday, 2018-09-27, to ensure service continuity.</p>
@@ -611,7 +661,7 @@ Version 1.1.0</h2>
<li>Improve JSON exception handling (#2605)</li> <li>Improve JSON exception handling (#2605)</li>
<li>Add missing virtual destructors (#2532)</li> <li>Add missing virtual destructors (#2532)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md368"></a> <h2><a class="anchor" id="autotoc_md375"></a>
Version 1.0.0.</h2> Version 1.0.0.</h2>
<p>The <code>rippled</code> 1.0.0 release includes incremental improvements to several previously released features.</p> <p>The <code>rippled</code> 1.0.0 release includes incremental improvements to several previously released features.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
@@ -625,7 +675,7 @@ Version 1.0.0.</h2>
<li>Add <code>check</code>, <code>escrow</code>, and <code>pay_chan</code> to <code>ledger_entry</code> (RIPD-1600)</li> <li>Add <code>check</code>, <code>escrow</code>, and <code>pay_chan</code> to <code>ledger_entry</code> (RIPD-1600)</li>
<li>Clarify Escrow semantics (RIPD-1571)</li> <li>Clarify Escrow semantics (RIPD-1571)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md369"></a> <h2><a class="anchor" id="autotoc_md376"></a>
Version 0.90.1</h2> Version 0.90.1</h2>
<p>The <code>rippled</code> 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.</p> <p>The <code>rippled</code> 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.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
@@ -641,7 +691,7 @@ Version 0.90.1</h2>
</li> </li>
<li>Use lock when creating a peer shard rangeset</li> <li>Use lock when creating a peer shard rangeset</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md370"></a> <h2><a class="anchor" id="autotoc_md377"></a>
Version 0.90.0</h2> Version 0.90.0</h2>
<p>The <code>rippled</code> 0.90.0 release introduces several features and enhancements that improve the reliability, scalability and security of the XRP Ledger.</p> <p>The <code>rippled</code> 0.90.0 release introduces several features and enhancements that improve the reliability, scalability and security of the XRP Ledger.</p>
<p>Highlights of this release include:</p> <p>Highlights of this release include:</p>
@@ -684,7 +734,7 @@ Version 0.90.0</h2>
<li>Avoid AppVeyor stack overflow (<a href="https://github.com/ripple/rippled/issues/2344">#2344</a>)</li> <li>Avoid AppVeyor stack overflow (<a href="https://github.com/ripple/rippled/issues/2344">#2344</a>)</li>
<li>Reduce noise in log (<a href="https://github.com/ripple/rippled/issues/2352">#2352</a>)</li> <li>Reduce noise in log (<a href="https://github.com/ripple/rippled/issues/2352">#2352</a>)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md371"></a> <h2><a class="anchor" id="autotoc_md378"></a>
Version 0.81.0</h2> Version 0.81.0</h2>
<p>The <code>rippled</code> 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 <a href="https://ripple.com/dev-blog/decentralization-strategy-update/">Decentralization Strategy Update</a> post.</p> <p>The <code>rippled</code> 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 <a href="https://ripple.com/dev-blog/decentralization-strategy-update/">Decentralization Strategy Update</a> post.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
@@ -695,7 +745,7 @@ Version 0.81.0</h2>
<ul> <ul>
<li>Optimize queries for account_tx to work around SQLite query planner (<a href="https://github.com/ripple/rippled/issues/2312">#2312</a>)</li> <li>Optimize queries for account_tx to work around SQLite query planner (<a href="https://github.com/ripple/rippled/issues/2312">#2312</a>)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md372"></a> <h2><a class="anchor" id="autotoc_md379"></a>
Version 0.80.2</h2> Version 0.80.2</h2>
<p>The <code>rippled</code> 0.80.2 release introduces changes that improve the scalability of the XRP Ledger.</p> <p>The <code>rippled</code> 0.80.2 release introduces changes that improve the scalability of the XRP Ledger.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
@@ -706,7 +756,7 @@ Version 0.80.2</h2>
<li>Increase the number of transaction handlers that can be in flight in the job queue and decrease the relative cost for peers to share transaction and ledger data.</li> <li>Increase the number of transaction handlers that can be in flight in the job queue and decrease the relative cost for peers to share transaction and ledger data.</li>
<li>Make better use of resources by adjusting the number of threads we initialize, by reverting commit <a href="https://github.com/ripple/rippled/commit/68b8ffdb638d07937f841f7217edeb25efdb3b5d">#68b8ffd</a>.</li> <li>Make better use of resources by adjusting the number of threads we initialize, by reverting commit <a href="https://github.com/ripple/rippled/commit/68b8ffdb638d07937f841f7217edeb25efdb3b5d">#68b8ffd</a>.</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md373"></a> <h2><a class="anchor" id="autotoc_md380"></a>
Version 0.80.1</h2> Version 0.80.1</h2>
<p>The <code>rippled</code> 0.80.1 release provides several enhancements in support of published validator lists and corrects several bugs.</p> <p>The <code>rippled</code> 0.80.1 release provides several enhancements in support of published validator lists and corrects several bugs.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
@@ -723,7 +773,7 @@ Version 0.80.1</h2>
<li>Explictly use <a class="elRef" href="http://en.cppreference.com/w/cpp/container/deque.html" title="STL class.">std::deque</a> for missing node handler in SHAMap code (<a href="https://github.com/ripple/rippled/issues/2252">#2252</a>)</li> <li>Explictly use <a class="elRef" href="http://en.cppreference.com/w/cpp/container/deque.html" title="STL class.">std::deque</a> for missing node handler in SHAMap code (<a href="https://github.com/ripple/rippled/issues/2252">#2252</a>)</li>
<li>Verify validator token manifest matches private key (<a href="https://github.com/ripple/rippled/issues/2268">#2268</a>)</li> <li>Verify validator token manifest matches private key (<a href="https://github.com/ripple/rippled/issues/2268">#2268</a>)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md374"></a> <h2><a class="anchor" id="autotoc_md381"></a>
Version 0.80.0</h2> Version 0.80.0</h2>
<p>The <code>rippled</code> 0.80.0 release introduces several enhancements that improve the reliability, scalability and security of the XRP Ledger.</p> <p>The <code>rippled</code> 0.80.0 release introduces several enhancements that improve the reliability, scalability and security of the XRP Ledger.</p>
<p>Highlights of this release include:</p> <p>Highlights of this release include:</p>
@@ -751,7 +801,7 @@ Version 0.80.0</h2>
<li>Fix an issue where <code>setAmendmentBlocked</code> is only called when processing the <code>EnableAmendment</code> transaction for the amendment (<a href="https://github.com/ripple/rippled/issues/2137">#2137</a>)</li> <li>Fix an issue where <code>setAmendmentBlocked</code> is only called when processing the <code>EnableAmendment</code> transaction for the amendment (<a href="https://github.com/ripple/rippled/issues/2137">#2137</a>)</li>
<li>Track escrow in recipient's owner directory (<a href="https://github.com/ripple/rippled/issues/2212">#2212</a>)</li> <li>Track escrow in recipient's owner directory (<a href="https://github.com/ripple/rippled/issues/2212">#2212</a>)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md375"></a> <h2><a class="anchor" id="autotoc_md382"></a>
Version 0.70.2</h2> Version 0.70.2</h2>
<p>The <code>rippled</code> 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.</p> <p>The <code>rippled</code> 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.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
@@ -760,7 +810,7 @@ Version 0.70.2</h2>
<ul> <ul>
<li>Recent fee rises and TxQ issues (<a href="https://github.com/ripple/rippled/issues/2215">#2215</a>)</li> <li>Recent fee rises and TxQ issues (<a href="https://github.com/ripple/rippled/issues/2215">#2215</a>)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md376"></a> <h2><a class="anchor" id="autotoc_md383"></a>
Version 0.70.1</h2> Version 0.70.1</h2>
<p>The <code>rippled</code> 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 <code>rippled</code> under the 1.1.x releases of OpenSSL.</p> <p>The <code>rippled</code> 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 <code>rippled</code> under the 1.1.x releases of OpenSSL.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
@@ -771,7 +821,7 @@ Version 0.70.1</h2>
<li>Log invariant check messages at "fatal" level (<a href="https://github.com/ripple/rippled/pull/2154">2154</a>)</li> <li>Log invariant check messages at "fatal" level (<a href="https://github.com/ripple/rippled/pull/2154">2154</a>)</li>
<li>Fix the consensus code to update all disputed transactions after a node changes a position (<a href="https://github.com/ripple/rippled/pull/2156">2156</a>)</li> <li>Fix the consensus code to update all disputed transactions after a node changes a position (<a href="https://github.com/ripple/rippled/pull/2156">2156</a>)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md377"></a> <h2><a class="anchor" id="autotoc_md384"></a>
Version 0.70.0</h2> Version 0.70.0</h2>
<p>The <code>rippled</code> 0.70.0 release introduces several enhancements that improve the reliability, scalability and security of the network.</p> <p>The <code>rippled</code> 0.70.0 release introduces several enhancements that improve the reliability, scalability and security of the network.</p>
<p>Highlights of this release include:</p> <p>Highlights of this release include:</p>
@@ -807,28 +857,28 @@ Version 0.70.0</h2>
<li>JobQueue occasionally crashes on shutdown (#2025)</li> <li>JobQueue occasionally crashes on shutdown (#2025)</li>
<li>Improve pseudo-transaction handling (#2104)</li> <li>Improve pseudo-transaction handling (#2104)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md378"></a> <h2><a class="anchor" id="autotoc_md385"></a>
Version 0.60.3</h2> Version 0.60.3</h2>
<p>The <code>rippled</code> 0.60.3 release helps to increase the stability of the network under heavy load.</p> <p>The <code>rippled</code> 0.60.3 release helps to increase the stability of the network under heavy load.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
<p>This release has no new features.</p> <p>This release has no new features.</p>
<p><b>Bug Fixes</b></p> <p><b>Bug Fixes</b></p>
<p>Server overlay improvements (<a href="https://github.com/ripple/rippled/pull/2011">#2110</a>)</p> <p>Server overlay improvements (<a href="https://github.com/ripple/rippled/pull/2011">#2110</a>)</p>
<h2><a class="anchor" id="autotoc_md379"></a> <h2><a class="anchor" id="autotoc_md386"></a>
Version 0.60.2</h2> Version 0.60.2</h2>
<p>The <code>rippled</code> 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.</p> <p>The <code>rippled</code> 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.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
<p>This release has no new features.</p> <p>This release has no new features.</p>
<p><b>Bug Fixes</b></p> <p><b>Bug Fixes</b></p>
<p>Prevent the ability to bypass the <code>NoRipple</code> flag using offers (<a href="https://github.com/ripple/rippled/commit/4ff40d4954dfaa237c8b708c2126cb39566776da">#7cd4d78</a>)</p> <p>Prevent the ability to bypass the <code>NoRipple</code> flag using offers (<a href="https://github.com/ripple/rippled/commit/4ff40d4954dfaa237c8b708c2126cb39566776da">#7cd4d78</a>)</p>
<h2><a class="anchor" id="autotoc_md380"></a> <h2><a class="anchor" id="autotoc_md387"></a>
Version 0.60.1</h2> Version 0.60.1</h2>
<p>The <code>rippled</code> 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.</p> <p>The <code>rippled</code> 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.</p>
<p><b>New and Updated Feature</b></p> <p><b>New and Updated Feature</b></p>
<p>This release has no new features.</p> <p>This release has no new features.</p>
<p><b>Bug Fixes</b></p> <p><b>Bug Fixes</b></p>
<p>Correct calculation of Escrow and Payment Channel indices. Fix WebSocket timeout timer issues.</p> <p>Correct calculation of Escrow and Payment Channel indices. Fix WebSocket timeout timer issues.</p>
<h2><a class="anchor" id="autotoc_md381"></a> <h2><a class="anchor" id="autotoc_md388"></a>
Version 0.60.0</h2> Version 0.60.0</h2>
<p>The <code>rippled</code> 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.</p> <p>The <code>rippled</code> 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.</p>
<p>Highlights of this release include:</p> <p>Highlights of this release include:</p>
@@ -870,21 +920,21 @@ Version 0.60.0</h2>
<li>Check for malformed public key on payment channel (#2027)</li> <li>Check for malformed public key on payment channel (#2027)</li>
<li>Send a websocket ping before timing out in server (#2035)</li> <li>Send a websocket ping before timing out in server (#2035)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md382"></a> <h2><a class="anchor" id="autotoc_md389"></a>
Version 0.50.3</h2> Version 0.50.3</h2>
<p>The <code>rippled</code> 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 <a href="https://ripple.com/build/understanding-the-noripple-flag/"><code>NoRipple</code></a> flag. Ripple recommends that all server operators immediately upgrade to version 0.50.3.</p> <p>The <code>rippled</code> 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 <a href="https://ripple.com/build/understanding-the-noripple-flag/"><code>NoRipple</code></a> flag. Ripple recommends that all server operators immediately upgrade to version 0.50.3.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
<p>This release has no new features.</p> <p>This release has no new features.</p>
<p><b>Bug Fixes</b></p> <p><b>Bug Fixes</b></p>
<p>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.</p> <p>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.</p>
<h2><a class="anchor" id="autotoc_md383"></a> <h2><a class="anchor" id="autotoc_md390"></a>
Version 0.50.2</h2> Version 0.50.2</h2>
<p>The <code>rippled</code> 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 <code>wss</code> keyword. Ripple recommends upgrading to 0.50.2 only if server operators are running rippled servers that accept client connections over TLS.</p> <p>The <code>rippled</code> 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 <code>wss</code> keyword. Ripple recommends upgrading to 0.50.2 only if server operators are running rippled servers that accept client connections over TLS.</p>
<p><b>New and Updated Features</b></p> <p><b>New and Updated Features</b></p>
<p>This release has no new features.</p> <p>This release has no new features.</p>
<p><b>Bug Fixes</b></p> <p><b>Bug Fixes</b></p>
<p>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 <code>wss</code> keyword (#1985)</p> <p>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 <code>wss</code> keyword (#1985)</p>
<h2><a class="anchor" id="autotoc_md384"></a> <h2><a class="anchor" id="autotoc_md391"></a>
Version 0.50.0</h2> Version 0.50.0</h2>
<p>The <code>rippled</code> 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.</p> <p>The <code>rippled</code> 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.</p>
<p>You can <a href="https://ripple.com/build/rippled-setup/#updating-rippled">update to the new version</a> on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please <a href="https://wiki.ripple.com/Rippled_build_instructions">compile the new version from source</a>.</p> <p>You can <a href="https://ripple.com/build/rippled-setup/#updating-rippled">update to the new version</a> on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please <a href="https://wiki.ripple.com/Rippled_build_instructions">compile the new version from source</a>.</p>
@@ -937,7 +987,7 @@ Version 0.50.0</h2>
<p>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 <a href="https://ripple.com/build/amendments/#suspay">SusPay</a> Amendment on Tuesday, 2017-02-21.</p> <p>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 <a href="https://ripple.com/build/amendments/#suspay">SusPay</a> Amendment on Tuesday, 2017-02-21.</p>
<p>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.</p> <p>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.</p>
<p>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 <a href="https://ripple.com/build/amendments/#shamapv2">SHAMapV2</a>. 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).</p> <p>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 <a href="https://ripple.com/build/amendments/#shamapv2">SHAMapV2</a>. 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).</p>
<h2><a class="anchor" id="autotoc_md385"></a> <h2><a class="anchor" id="autotoc_md392"></a>
Version 0.40.1</h2> Version 0.40.1</h2>
<p>The <code>rippled</code> 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.</p> <p>The <code>rippled</code> 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.</p>
<p>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.</p> <p>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.</p>
@@ -945,7 +995,7 @@ Version 0.40.1</h2>
<p>This release has no new features.</p> <p>This release has no new features.</p>
<p><b>Bug Fixes</b></p> <p><b>Bug Fixes</b></p>
<p>Increase SQLite database limits to prevent full-history servers from crashing when restarting. (#1961)</p> <p>Increase SQLite database limits to prevent full-history servers from crashing when restarting. (#1961)</p>
<h2><a class="anchor" id="autotoc_md386"></a> <h2><a class="anchor" id="autotoc_md393"></a>
Version 0.40.0</h2> Version 0.40.0</h2>
<p>The <code>rippled</code> 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 <a href="https://ripple.com/build/amendments/#suspay">SusPay</a> on Tuesday, 2017-01-17.</p> <p>The <code>rippled</code> 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 <a href="https://ripple.com/build/amendments/#suspay">SusPay</a> on Tuesday, 2017-01-17.</p>
<p>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.</p> <p>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.</p>
@@ -960,7 +1010,7 @@ Version 0.40.0</h2>
<p>Correct an issue in payment flow code that did not remove an unfunded offer (#1860)</p> <p>Correct an issue in payment flow code that did not remove an unfunded offer (#1860)</p>
<p>Sign validator manifests with both ephemeral and master keys (#1865)</p> <p>Sign validator manifests with both ephemeral and master keys (#1865)</p>
<p>Correctly parse multi-buffer JSON messages (#1862)</p> <p>Correctly parse multi-buffer JSON messages (#1862)</p>
<h2><a class="anchor" id="autotoc_md387"></a> <h2><a class="anchor" id="autotoc_md394"></a>
Version 0.33.0</h2> Version 0.33.0</h2>
<p>The <code>rippled</code> 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 <a href="https://ripple.com/build/amendments/#flow">Flow</a>. We are also introducing XRP Payment Channels, a new structure in the ledger designed to support <a href="https://interledger.org/">Interledger Protocol</a> trust lines as balances get substantial, which we expect to be activated via Amendment on a future date (TBA) with the name <a href="https://ripple.com/build/amendments/#paychan">PayChan</a>. 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 <a href="https://ripple.com/build/amendments/#shamapv2">SHAMapV2</a>.</p> <p>The <code>rippled</code> 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 <a href="https://ripple.com/build/amendments/#flow">Flow</a>. We are also introducing XRP Payment Channels, a new structure in the ledger designed to support <a href="https://interledger.org/">Interledger Protocol</a> trust lines as balances get substantial, which we expect to be activated via Amendment on a future date (TBA) with the name <a href="https://ripple.com/build/amendments/#paychan">PayChan</a>. 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 <a href="https://ripple.com/build/amendments/#shamapv2">SHAMapV2</a>.</p>
<p>You can <a href="https://ripple.com/build/rippled-setup/#updating-rippled">update to the new version</a> on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please <a href="https://wiki.ripple.com/Rippled_build_instructions">compile the new version from source</a>.</p> <p>You can <a href="https://ripple.com/build/rippled-setup/#updating-rippled">update to the new version</a> on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please <a href="https://wiki.ripple.com/Rippled_build_instructions">compile the new version from source</a>.</p>
@@ -985,7 +1035,7 @@ Version 0.33.0</h2>
<p><code>PaymentSandbox::balanceHook</code> can return the wrong issuer, which could cause the transfer fee to be incorrectly by-passed in rare circumstances. [RIPD-1274, #1827]</p> <p><code>PaymentSandbox::balanceHook</code> can return the wrong issuer, which could cause the transfer fee to be incorrectly by-passed in rare circumstances. [RIPD-1274, #1827]</p>
<p>Prevent concurrent write operations in websockets [#1806]</p> <p>Prevent concurrent write operations in websockets [#1806]</p>
<p>Add HTTP status page for new websocket implementation [#1855]</p> <p>Add HTTP status page for new websocket implementation [#1855]</p>
<h2><a class="anchor" id="autotoc_md388"></a> <h2><a class="anchor" id="autotoc_md395"></a>
Version 0.32.1</h2> Version 0.32.1</h2>
<p>The <code>rippled</code> 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.</p> <p>The <code>rippled</code> 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.</p>
<p>You can <a href="https://ripple.com/build/rippled-setup/#updating-rippled">update to the new version</a> on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please <a href="https://wiki.ripple.com/Rippled_build_instructions">compile the new version from source</a>.</p> <p>You can <a href="https://ripple.com/build/rippled-setup/#updating-rippled">update to the new version</a> on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please <a href="https://wiki.ripple.com/Rippled_build_instructions">compile the new version from source</a>.</p>
@@ -1004,7 +1054,7 @@ protocol = wss2
<p>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)</p> <p>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)</p>
<p>Remove incompatible OS X switches in Test.py (RIPD-1250)</p> <p>Remove incompatible OS X switches in Test.py (RIPD-1250)</p>
<p>Autofilling a transaction fee (sign / submit) with the experimental <code>x-queue-okay</code> 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)</p> <p>Autofilling a transaction fee (sign / submit) with the experimental <code>x-queue-okay</code> 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)</p>
<h2><a class="anchor" id="autotoc_md389"></a> <h2><a class="anchor" id="autotoc_md396"></a>
Version 0.32.0</h2> Version 0.32.0</h2>
<p>The <code>rippled</code> 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 <code>server_info</code> and <code>server_state</code> commands now include information on transaction cost multipliers and the fee command is available to unprivileged users. We advise rippled operators to upgrade immediately.</p> <p>The <code>rippled</code> 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 <code>server_info</code> and <code>server_state</code> commands now include information on transaction cost multipliers and the fee command is available to unprivileged users. We advise rippled operators to upgrade immediately.</p>
<p>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.</p> <p>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.</p>
@@ -1050,7 +1100,7 @@ Version 0.32.0</h2>
<li>Remove obsolete sendGetPeers support (RIPD-164)</li> <li>Remove obsolete sendGetPeers support (RIPD-164)</li>
<li>Remove obsolete internal command (RIPD-888)</li> <li>Remove obsolete internal command (RIPD-888)</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md390"></a> <h2><a class="anchor" id="autotoc_md397"></a>
Version 0.31.2</h2> Version 0.31.2</h2>
<p>The <code>rippled</code> 0.31.2 release corrects issues with the fee escalation algorithm. We advise <code>rippled</code> operators to upgrade immediately.</p> <p>The <code>rippled</code> 0.31.2 release corrects issues with the fee escalation algorithm. We advise <code>rippled</code> operators to upgrade immediately.</p>
<p>You can <a href="https://ripple.com/build/rippled-setup/#updating-rippled">update to the new version</a> on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please <a href="https://wiki.ripple.com/Rippled_build_instructions">compile the new version from source</a>.</p> <p>You can <a href="https://ripple.com/build/rippled-setup/#updating-rippled">update to the new version</a> on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please <a href="https://wiki.ripple.com/Rippled_build_instructions">compile the new version from source</a>.</p>
@@ -1061,7 +1111,7 @@ Version 0.31.2</h2>
<li>A defect in the fee escalation algorithm that caused network fees to escalate more rapidly than intended has been corrected. (RIPD-1177)</li> <li>A defect in the fee escalation algorithm that caused network fees to escalate more rapidly than intended has been corrected. (RIPD-1177)</li>
<li>The minimum local fee advertised by validators will no longer be adjusted upwards.</li> <li>The minimum local fee advertised by validators will no longer be adjusted upwards.</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md391"></a> <h2><a class="anchor" id="autotoc_md398"></a>
Version 0.31.1</h2> Version 0.31.1</h2>
<p>The <code>rippled</code> 0.31.1 release contains one important bug fix. We advise <code>rippled</code> operators to upgrade immediately.</p> <p>The <code>rippled</code> 0.31.1 release contains one important bug fix. We advise <code>rippled</code> operators to upgrade immediately.</p>
<p>You can <a href="https://ripple.com/build/rippled-setup/#updating-rippled">update to the new version</a> on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please <a href="https://wiki.ripple.com/Rippled_build_instructions">compile the new version from source</a>.</p> <p>You can <a href="https://ripple.com/build/rippled-setup/#updating-rippled">update to the new version</a> on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please <a href="https://wiki.ripple.com/Rippled_build_instructions">compile the new version from source</a>.</p>
@@ -1072,7 +1122,7 @@ Version 0.31.1</h2>
<ul> <ul>
<li>Correctly handle ledger validations with no <code>LedgerSequence</code> field. Previous versions of <code>rippled</code> 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.</li> <li>Correctly handle ledger validations with no <code>LedgerSequence</code> field. Previous versions of <code>rippled</code> 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.</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md392"></a> <h2><a class="anchor" id="autotoc_md399"></a>
Version 0.31.0</h2> Version 0.31.0</h2>
<p><code>rippled</code> 0.31.0 has been released.</p> <p><code>rippled</code> 0.31.0 has been released.</p>
<p>You can <a href="https://ripple.com/build/rippled-setup/#updating-rippled">update to the new version</a> on Red Hat Enterprise Linux 7 or CentOS 7 using yum.</p> <p>You can <a href="https://ripple.com/build/rippled-setup/#updating-rippled">update to the new version</a> on Red Hat Enterprise Linux 7 or CentOS 7 using yum.</p>
@@ -1114,7 +1164,7 @@ Version 0.31.0</h2>
<li>Improve error message when signing fails (RIPD-1066)</li> <li>Improve error message when signing fails (RIPD-1066)</li>
<li>Fix websocket deadlock</li> <li>Fix websocket deadlock</li>
</ul> </ul>
<h2><a class="anchor" id="autotoc_md393"></a> <h2><a class="anchor" id="autotoc_md400"></a>
Version 0.30.1</h2> Version 0.30.1</h2>
<p>rippled 0.30.1 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.30.1">https://github.com/ripple/rippled/tree/0.30.1</a></p> <p>rippled 0.30.1 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.30.1">https://github.com/ripple/rippled/tree/0.30.1</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit c717006c44126aa0edb3a36ca29ee30e7a72c1d3 <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit c717006c44126aa0edb3a36ca29ee30e7a72c1d3
@@ -1173,7 +1223,7 @@ Version 0.30.1</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md395"></a> <h2><a class="anchor" id="autotoc_md402"></a>
Version 0.30.0</h2> Version 0.30.0</h2>
<p>rippled 0.30.0 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.30.0">https://github.com/ripple/rippled/tree/0.30.0</a></p> <p>rippled 0.30.0 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.30.0">https://github.com/ripple/rippled/tree/0.30.0</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit a8859b495b552fe1eb140771f0f2cb32d11d2ac2 <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit a8859b495b552fe1eb140771f0f2cb32d11d2ac2
@@ -1222,7 +1272,7 @@ Version 0.30.0</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md397"></a> <h2><a class="anchor" id="autotoc_md404"></a>
Version 0.29.0</h2> Version 0.29.0</h2>
<p>rippled 0.29.0 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/commits/0.29.0">https://github.com/ripple/rippled/commits/0.29.0</a></p> <p>rippled 0.29.0 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/commits/0.29.0">https://github.com/ripple/rippled/commits/0.29.0</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 5964710f736e258c7892e8b848c48952a4c7856c <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 5964710f736e258c7892e8b848c48952a4c7856c
@@ -1272,7 +1322,7 @@ Version 0.29.0</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md399"></a> <h2><a class="anchor" id="autotoc_md406"></a>
Version 0.28.2</h2> Version 0.28.2</h2>
<p>rippled 0.28.2 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/commits/release">https://github.com/ripple/rippled/commits/release</a></p> <p>rippled 0.28.2 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/commits/release">https://github.com/ripple/rippled/commits/release</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 6374aad9bc94595e051a04e23580617bc1aaf300 <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 6374aad9bc94595e051a04e23580617bc1aaf300
@@ -1319,7 +1369,7 @@ Version 0.28.2</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md401"></a> <h2><a class="anchor" id="autotoc_md408"></a>
Version 0.28.1</h2> Version 0.28.1</h2>
<p>rippled 0.28.1 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.28.1">https://github.com/ripple/rippled/tree/0.28.1</a></p> <p>rippled 0.28.1 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.28.1">https://github.com/ripple/rippled/tree/0.28.1</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 399c43cae6e90a428e9ce6a988123972b0f03c99 <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 399c43cae6e90a428e9ce6a988123972b0f03c99
@@ -1369,7 +1419,7 @@ Version 0.28.1</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md403"></a> <h2><a class="anchor" id="autotoc_md410"></a>
Version 0.28.0</h2> Version 0.28.0</h2>
<p>rippled 0.28.0 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.28.0">https://github.com/ripple/rippled/tree/0.28.0</a></p> <p>rippled 0.28.0 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.28.0">https://github.com/ripple/rippled/tree/0.28.0</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 7efd0ab0d6ef017331a0e214a3053893c88f38a9 <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 7efd0ab0d6ef017331a0e214a3053893c88f38a9
@@ -1461,7 +1511,7 @@ Version 0.28.0</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md405"></a> <h2><a class="anchor" id="autotoc_md412"></a>
Version 0.27.4</h2> Version 0.27.4</h2>
<p>rippled 0.27.4 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.27.4">https://github.com/ripple/rippled/tree/0.27.4</a></p> <p>rippled 0.27.4 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.27.4">https://github.com/ripple/rippled/tree/0.27.4</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 92812fe7239ffa3ba91649b2ece1e892b866ec2a <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 92812fe7239ffa3ba91649b2ece1e892b866ec2a
@@ -1487,7 +1537,7 @@ Version 0.27.4</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md407"></a> <h2><a class="anchor" id="autotoc_md414"></a>
Version 0.27.3-sp2</h2> Version 0.27.3-sp2</h2>
<p>rippled 0.27.3-sp2 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.27.3-sp2">https://github.com/ripple/rippled/tree/0.27.3-sp2</a></p> <p>rippled 0.27.3-sp2 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.27.3-sp2">https://github.com/ripple/rippled/tree/0.27.3-sp2</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit f999839e599e131ed624330ad0ce85bb995f02d3 <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit f999839e599e131ed624330ad0ce85bb995f02d3
@@ -1513,7 +1563,7 @@ Version 0.27.3-sp2</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md409"></a> <h2><a class="anchor" id="autotoc_md416"></a>
Version 0.27.3-sp1</h2> Version 0.27.3-sp1</h2>
<p>rippled 0.27.3-sp1 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.27.3-sp1">https://github.com/ripple/rippled/tree/0.27.3-sp1</a></p> <p>rippled 0.27.3-sp1 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.27.3-sp1">https://github.com/ripple/rippled/tree/0.27.3-sp1</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 232693419a2c9a8276a0fae991f688f6f01a3add <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 232693419a2c9a8276a0fae991f688f6f01a3add
@@ -1539,7 +1589,7 @@ Version 0.27.3-sp1</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md411"></a> <h2><a class="anchor" id="autotoc_md418"></a>
Version 0.27.3</h2> Version 0.27.3</h2>
<p>rippled 0.27.3 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.27.3">https://github.com/ripple/rippled/tree/0.27.3</a></p> <p>rippled 0.27.3 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.27.3">https://github.com/ripple/rippled/tree/0.27.3</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 70c2854f7c8a28801a7ebc81dd62bf0d068188f0 <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 70c2854f7c8a28801a7ebc81dd62bf0d068188f0
@@ -1565,7 +1615,7 @@ Version 0.27.3</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md413"></a> <h2><a class="anchor" id="autotoc_md420"></a>
Version 0.27.2</h2> Version 0.27.2</h2>
<p>rippled 0.27.2 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.27.2">https://github.com/ripple/rippled/tree/0.27.2</a></p> <p>rippled 0.27.2 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.27.2">https://github.com/ripple/rippled/tree/0.27.2</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 9cc8eec773e8afc9c12a6aab4982deda80495cf1 <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 9cc8eec773e8afc9c12a6aab4982deda80495cf1
@@ -1605,7 +1655,7 @@ Version 0.27.2</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md415"></a> <h2><a class="anchor" id="autotoc_md422"></a>
Version 0.27.1</h2> Version 0.27.1</h2>
<p>rippled 0.27.1 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.27.1">https://github.com/ripple/rippled/tree/0.27.1</a></p> <p>rippled 0.27.1 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.27.1">https://github.com/ripple/rippled/tree/0.27.1</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 95973ba3e8b0bd28eeaa034da8b806faaf498d8a <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 95973ba3e8b0bd28eeaa034da8b806faaf498d8a
@@ -1648,7 +1698,7 @@ Version 0.27.1</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md417"></a> <h2><a class="anchor" id="autotoc_md424"></a>
Version 0.27.0</h2> Version 0.27.0</h2>
<p>rippled 0.27.0 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.27.0">https://github.com/ripple/rippled/tree/0.27.0</a></p> <p>rippled 0.27.0 has been released. The commit can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.27.0">https://github.com/ripple/rippled/tree/0.27.0</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit c6c8e5d70c6fbde02cd946135a061aa77744396f <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit c6c8e5d70c6fbde02cd946135a061aa77744396f
@@ -1773,7 +1823,7 @@ Version 0.27.0</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md419"></a> <h2><a class="anchor" id="autotoc_md426"></a>
Version 0.26.4</h2> Version 0.26.4</h2>
<p>rippled 0.26.4 has been released. The repository tag is <em>0.26.4</em> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/commits/0.26.4">https://github.com/ripple/rippled/commits/0.26.4</a></p> <p>rippled 0.26.4 has been released. The repository tag is <em>0.26.4</em> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/commits/0.26.4">https://github.com/ripple/rippled/commits/0.26.4</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 05a04aa80192452475888479c84ff4b9b54e6ae7 <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 05a04aa80192452475888479c84ff4b9b54e6ae7
@@ -1845,7 +1895,7 @@ Version 0.26.4</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md421"></a> <h2><a class="anchor" id="autotoc_md428"></a>
Version 0.26.3-sp1</h2> Version 0.26.3-sp1</h2>
<p>rippled 0.26.3-sp1 has been released. The repository tag is <em>0.26.3-sp1</em> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.26.3-sp1">https://github.com/ripple/rippled/tree/0.26.3-sp1</a></p> <p>rippled 0.26.3-sp1 has been released. The repository tag is <em>0.26.3-sp1</em> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.26.3-sp1">https://github.com/ripple/rippled/tree/0.26.3-sp1</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 2ad6f0a65e248b4f614d38d199a9d5d02f5aaed8 <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 2ad6f0a65e248b4f614d38d199a9d5d02f5aaed8
@@ -1904,7 +1954,7 @@ Version 0.26.3-sp1</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md423"></a> <h2><a class="anchor" id="autotoc_md430"></a>
Version 0.26.2</h2> Version 0.26.2</h2>
<p>rippled 0.26.2 has been released. The repository tag is <em>0.26.2</em> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.26.2">https://github.com/ripple/rippled/tree/0.26.2</a></p> <p>rippled 0.26.2 has been released. The repository tag is <em>0.26.2</em> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.26.2">https://github.com/ripple/rippled/tree/0.26.2</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit b9454e0f0ca8dbc23844a0520d49394e10d445b1 <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit b9454e0f0ca8dbc23844a0520d49394e10d445b1
@@ -1940,7 +1990,7 @@ Version 0.26.2</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md425"></a> <h2><a class="anchor" id="autotoc_md432"></a>
Version 0.26.1</h2> Version 0.26.1</h2>
<p>rippled v0.26.1 has been released. The repository tag is <b>0.26.1</b> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.26.1">https://github.com/ripple/rippled/tree/0.26.1</a></p> <p>rippled v0.26.1 has been released. The repository tag is <b>0.26.1</b> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.26.1">https://github.com/ripple/rippled/tree/0.26.1</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 9a0e806f78300374e20070e2573755fbafdbfd03 <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 9a0e806f78300374e20070e2573755fbafdbfd03
@@ -1965,7 +2015,7 @@ Version 0.26.1</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md427"></a> <h2><a class="anchor" id="autotoc_md434"></a>
Version 0.26.0</h2> Version 0.26.0</h2>
<p>rippled v0.26.0 has been released. The repository tag is <b>0.26.0</b> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.26.0">https://github.com/ripple/rippled/tree/0.26.0</a></p> <p>rippled v0.26.0 has been released. The repository tag is <b>0.26.0</b> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.26.0">https://github.com/ripple/rippled/tree/0.26.0</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 9fa5e3987260e39dba322f218d39ac228a5b361b <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 9fa5e3987260e39dba322f218d39ac228a5b361b
@@ -2006,7 +2056,7 @@ Version 0.26.0</h2>
<li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li> <li><a href="https://webchat.freenode.net/?channels=#ripple">IRC</a></li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md429"></a> <h2><a class="anchor" id="autotoc_md436"></a>
Version 0.25.2</h2> Version 0.25.2</h2>
<p>rippled v0.25.2 has been released. The repository tag is <b>0.25.2</b> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.25.2">https://github.com/ripple/rippled/tree/0.25.2</a></p> <p>rippled v0.25.2 has been released. The repository tag is <b>0.25.2</b> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.25.2">https://github.com/ripple/rippled/tree/0.25.2</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit ddf68d464d74e1c76a0cfd100a08bc8e65b91fec <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit ddf68d464d74e1c76a0cfd100a08bc8e65b91fec
@@ -2032,7 +2082,7 @@ Version 0.25.2</h2>
<li>Transactions with unreasonably long path lengths are rejected. The maximum is now eight (8) hops.</li> <li>Transactions with unreasonably long path lengths are rejected. The maximum is now eight (8) hops.</li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md431"></a> <h2><a class="anchor" id="autotoc_md438"></a>
Version 0.25.1</h2> Version 0.25.1</h2>
<p><code>rippled</code> v0.25.1 has been released. The repository tag is <code>0.25.1</code> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.25.1">https://github.com/ripple/rippled/tree/0.25.1</a></p> <p><code>rippled</code> v0.25.1 has been released. The repository tag is <code>0.25.1</code> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.25.1">https://github.com/ripple/rippled/tree/0.25.1</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <code>git log</code> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit b677cacb8ce0d4ef21f8c60112af1db51dce5bb4 <p>Prior to building, please confirm you have the correct source tree with the <code>git log</code> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit b677cacb8ce0d4ef21f8c60112af1db51dce5bb4
@@ -2068,7 +2118,7 @@ Version 0.25.1</h2>
<li>Reduced number of asynchronous fetches.</li> <li>Reduced number of asynchronous fetches.</li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md433"></a> <h2><a class="anchor" id="autotoc_md440"></a>
Version 0.25.0</h2> Version 0.25.0</h2>
<p>rippled version 0.25.0 has been released. The repository tag is <b>0.25.0</b> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.25.0">https://github.com/ripple/rippled/tree/0.25.0</a></p> <p>rippled version 0.25.0 has been released. The repository tag is <b>0.25.0</b> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.25.0">https://github.com/ripple/rippled/tree/0.25.0</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 29d1d5f06261a93c5e94b4011c7675ff42443b7f <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 29d1d5f06261a93c5e94b4011c7675ff42443b7f
@@ -2102,7 +2152,7 @@ Version 0.25.0</h2>
<li>Reduced number of asynchronous fetches.</li> <li>Reduced number of asynchronous fetches.</li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md435"></a> <h2><a class="anchor" id="autotoc_md442"></a>
Version 0.24.0</h2> Version 0.24.0</h2>
<p>rippled version 0.24.0 has been released. The repository tag is <b>0.24.0</b> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.24.0">https://github.com/ripple/rippled/tree/0.24.0</a></p> <p>rippled version 0.24.0 has been released. The repository tag is <b>0.24.0</b> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.24.0">https://github.com/ripple/rippled/tree/0.24.0</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 3eb1c7bd6f93e5d874192197f76571184338f702 <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 3eb1c7bd6f93e5d874192197f76571184338f702
@@ -2131,7 +2181,7 @@ Version 0.24.0</h2>
<li>Build process enforces minimum versions of OpenSSL and BOOST for operation.</li> <li>Build process enforces minimum versions of OpenSSL and BOOST for operation.</li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md437"></a> <h2><a class="anchor" id="autotoc_md444"></a>
Version 0.23.0</h2> Version 0.23.0</h2>
<p>rippled version 0.23.0 has been released. The repository tag is <b>0.23.0</b> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.23.0">https://github.com/ripple/rippled/tree/0.23.0</a></p> <p>rippled version 0.23.0 has been released. The repository tag is <b>0.23.0</b> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.23.0">https://github.com/ripple/rippled/tree/0.23.0</a></p>
<p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 29a4f61551236f70865d46d6653da2e62de1c701 <p>Prior to building, please confirm you have the correct source tree with the <b>git log</b> command. The first log entry should be the change setting the version: </p><pre class="fragment"> commit 29a4f61551236f70865d46d6653da2e62de1c701
@@ -2171,7 +2221,7 @@ Version 0.23.0</h2>
<li>Fix typos in transaction engine error code identifiers</li> <li>Fix typos in transaction engine error code identifiers</li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md439"></a> <h2><a class="anchor" id="autotoc_md446"></a>
Version 0.22.0</h2> Version 0.22.0</h2>
<p>rippled version 0.22.0 has been released. This release is currently the tip of the <b>develop/</b> branch and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/develop">https://github.com/ripple/rippled/tree/develop</a> The tag is <b>0.22.0</b> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.22.0">https://github.com/ripple/rippled/tree/0.22.0</a></p> <p>rippled version 0.22.0 has been released. This release is currently the tip of the <b>develop/</b> branch and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/develop">https://github.com/ripple/rippled/tree/develop</a> The tag is <b>0.22.0</b> and can be found on GitHub at: <a href="https://github.com/ripple/rippled/tree/0.22.0">https://github.com/ripple/rippled/tree/0.22.0</a></p>
<p><b>This is a critical release affecting transaction processing. All partners should update immediately.</b></p> <p><b>This is a critical release affecting transaction processing. All partners should update immediately.</b></p>
@@ -2228,7 +2278,7 @@ Version 0.22.0</h2>
<li>Optimized transaction node lookup circumstances in the node store.</li> <li>Optimized transaction node lookup circumstances in the node store.</li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md441"></a> <h2><a class="anchor" id="autotoc_md448"></a>
Version 0.21.0</h2> Version 0.21.0</h2>
<p>rippled version 0.21.0 has been released. This release is currently the tip of the <b>develop/</b> branch and can be found on GitHub at <a href="https://github.com/ripple/rippled/tree/develop">1</a>. The tag is <b>0.21.0-rc2</b> and can be found on GitHub at <a href="https://github.com/ripple/rippled/tree/0.21.0-rc2">2</a>.</p> <p>rippled version 0.21.0 has been released. This release is currently the tip of the <b>develop/</b> branch and can be found on GitHub at <a href="https://github.com/ripple/rippled/tree/develop">1</a>. The tag is <b>0.21.0-rc2</b> and can be found on GitHub at <a href="https://github.com/ripple/rippled/tree/0.21.0-rc2">2</a>.</p>
<p><b>This is a critical release. All partners should update immediately.</b></p> <p><b>This is a critical release. All partners should update immediately.</b></p>
@@ -2315,7 +2365,7 @@ Date: Fri Jan 24 11:17:16 2014 -0800
<li><b>Note</b>: HyperLevelDB and RocksDB are not available on Windows platform.</li> <li><b>Note</b>: HyperLevelDB and RocksDB are not available on Windows platform.</li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md443"></a> <h2><a class="anchor" id="autotoc_md450"></a>
Version 0.20.1</h2> Version 0.20.1</h2>
<p>rippled version 0.20.1 has been released. This release is currently the tip of the <a href="https://github.com/ripple/rippled/tree/develop">develop</a> branch and the tag is <a href="https://github.com/ripple/rippled/tree/0.20.1">0.20.1</a>.</p> <p>rippled version 0.20.1 has been released. This release is currently the tip of the <a href="https://github.com/ripple/rippled/tree/develop">develop</a> branch and the tag is <a href="https://github.com/ripple/rippled/tree/0.20.1">0.20.1</a>.</p>
<p><b>This is a critical release. All partners should update immediately.</b></p> <p><b>This is a critical release. All partners should update immediately.</b></p>
@@ -2419,7 +2469,7 @@ file_size_mult=2
<li><b>Note</b>: HyperLevelDB and RocksDB are not available on Windows platform.</li> <li><b>Note</b>: HyperLevelDB and RocksDB are not available on Windows platform.</li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md445"></a> <h2><a class="anchor" id="autotoc_md452"></a>
Version 0.19</h2> Version 0.19</h2>
<p>rippled version 0.19 has now been released. This release is currently the tip of the <a href="https://github.com/ripple/rippled/tree/release">release</a> branch and the tag is <a href="https://github.com/ripple/rippled/tree/0.19.0">0.19.0</a>.</p> <p>rippled version 0.19 has now been released. This release is currently the tip of the <a href="https://github.com/ripple/rippled/tree/release">release</a> branch and the tag is <a href="https://github.com/ripple/rippled/tree/0.19.0">0.19.0</a>.</p>
<p>Prior to building, please confirm you have the correct source tree with the <code>git log</code> command. The first log entry should be the change setting the version: </p><pre class="fragment">commit 26783607157a8b96e6e754f71565f4eb0134efc1 <p>Prior to building, please confirm you have the correct source tree with the <code>git log</code> command. The first log entry should be the change setting the version: </p><pre class="fragment">commit 26783607157a8b96e6e754f71565f4eb0134efc1
@@ -2472,7 +2522,7 @@ file_size_mult=2
<li><b>Note:</b> HyperLevelDB and RocksDB are not available on Windows platform.</li> <li><b>Note:</b> HyperLevelDB and RocksDB are not available on Windows platform.</li>
</ul> </ul>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md447"></a> <h2><a class="anchor" id="autotoc_md454"></a>
Version 0.16</h2> Version 0.16</h2>
<p>rippled version 0.16 has now been released. This release is currently the tip of the <a href="https://github.com/ripple/rippled/tree/master">master</a> branch and the tag is <a href="https://github.com/ripple/rippled/tree/v0.16.0">v0.16.0</a>.</p> <p>rippled version 0.16 has now been released. This release is currently the tip of the <a href="https://github.com/ripple/rippled/tree/master">master</a> branch and the tag is <a href="https://github.com/ripple/rippled/tree/v0.16.0">v0.16.0</a>.</p>
<p>Prior to building, please confirm you have the correct source tree with the <code>git log</code> command. The first log entry should be the change setting the version: </p><pre class="fragment">commit 15ef43505473225af21bb7b575fb0b628d5e7f73 <p>Prior to building, please confirm you have the correct source tree with the <code>git log</code> command. The first log entry should be the change setting the version: </p><pre class="fragment">commit 15ef43505473225af21bb7b575fb0b628d5e7f73
@@ -2520,7 +2570,7 @@ path=db/hashnode
<p><b>Issues</b></p> <p><b>Issues</b></p>
<p>None known</p> <p>None known</p>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md449"></a> <h2><a class="anchor" id="autotoc_md456"></a>
Version 0.14</h2> Version 0.14</h2>
<p>rippled version 0.14 has now been released. This release is currently the tip of the <a href="https://github.com/ripple/rippled/tree/master">master</a> branch and the tag is <a href="https://github.com/ripple/rippled/tree/v0.14.0">v0.12.0</a>.</p> <p>rippled version 0.14 has now been released. This release is currently the tip of the <a href="https://github.com/ripple/rippled/tree/master">master</a> branch and the tag is <a href="https://github.com/ripple/rippled/tree/v0.14.0">v0.12.0</a>.</p>
<p>Prior to building, please confirm you have the correct source tree with the <code>git log</code> command. The first log entry should be the change setting the version: </p><pre class="fragment">commit b6d11c08d0245ee9bafbb97143f5d685dd2979fc <p>Prior to building, please confirm you have the correct source tree with the <code>git log</code> command. The first log entry should be the change setting the version: </p><pre class="fragment">commit b6d11c08d0245ee9bafbb97143f5d685dd2979fc
@@ -2568,7 +2618,7 @@ path=db/hashnode
<p><b>Issues</b></p> <p><b>Issues</b></p>
<p>None known</p> <p>None known</p>
<hr /> <hr />
<h2><a class="anchor" id="autotoc_md451"></a> <h2><a class="anchor" id="autotoc_md458"></a>
Version 0.12</h2> Version 0.12</h2>
<p>rippled version 0.12 has now been released. This release is currently the tip of the <a href="https://github.com/ripple/rippled/tree/master">master branch</a> and can be found on GitHub. The tag is <a href="https://github.com/ripple/rippled/tree/v0.12.0">v0.12.0</a>.</p> <p>rippled version 0.12 has now been released. This release is currently the tip of the <a href="https://github.com/ripple/rippled/tree/master">master branch</a> and can be found on GitHub. The tag is <a href="https://github.com/ripple/rippled/tree/v0.12.0">v0.12.0</a>.</p>
<p>Prior to building, please confirm you have the correct source tree with the <code>git log</code> command. The first log entry should be the change setting the version: </p><pre class="fragment">commit d0a9da6f16f4083993e4b6c5728777ffebf80f3a <p>Prior to building, please confirm you have the correct source tree with the <code>git log</code> command. The first log entry should be the change setting the version: </p><pre class="fragment">commit d0a9da6f16f4083993e4b6c5728777ffebf80f3a

4
namespaceripple_1_1BuildInfo.html
View File

@@ -99,7 +99,7 @@ Functions</h2></td></tr>
</table><table class="memberdecls"> </table><table class="memberdecls">
<tr class="heading"><td colspan="2"><h2 class="groupheader"><a name="var-members"></a> <tr class="heading"><td colspan="2"><h2 class="groupheader"><a name="var-members"></a>
Variables</h2></td></tr> Variables</h2></td></tr>
<tr class="memitem:add98d1ad0d107ee61a6ace72d982cf36"><td class="memItemLeft" align="right" valign="top">char const *const&#160;</td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceripple_1_1BuildInfo.html#add98d1ad0d107ee61a6ace72d982cf36">versionString</a> = &quot;1.9.2-rc1&quot;</td></tr> <tr class="memitem:add98d1ad0d107ee61a6ace72d982cf36"><td class="memItemLeft" align="right" valign="top">char const *const&#160;</td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceripple_1_1BuildInfo.html#add98d1ad0d107ee61a6ace72d982cf36">versionString</a> = &quot;1.9.2&quot;</td></tr>
<tr class="separator:add98d1ad0d107ee61a6ace72d982cf36"><td class="memSeparator" colspan="2">&#160;</td></tr> <tr class="separator:add98d1ad0d107ee61a6ace72d982cf36"><td class="memSeparator" colspan="2">&#160;</td></tr>
<tr class="memitem:a3f9689f7affc4d0b0c9e63869fd0deeb"><td class="memItemLeft" align="right" valign="top">static constexpr <a class="elRef" href="http://en.cppreference.com/w/cpp/types/integer.html">std::uint64_t</a>&#160;</td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceripple_1_1BuildInfo.html#a3f9689f7affc4d0b0c9e63869fd0deeb">implementationVersionIdentifier</a></td></tr> <tr class="memitem:a3f9689f7affc4d0b0c9e63869fd0deeb"><td class="memItemLeft" align="right" valign="top">static constexpr <a class="elRef" href="http://en.cppreference.com/w/cpp/types/integer.html">std::uint64_t</a>&#160;</td><td class="memItemRight" valign="bottom"><a class="el" href="namespaceripple_1_1BuildInfo.html#a3f9689f7affc4d0b0c9e63869fd0deeb">implementationVersionIdentifier</a></td></tr>
<tr class="separator:a3f9689f7affc4d0b0c9e63869fd0deeb"><td class="memSeparator" colspan="2">&#160;</td></tr> <tr class="separator:a3f9689f7affc4d0b0c9e63869fd0deeb"><td class="memSeparator" colspan="2">&#160;</td></tr>
@@ -281,7 +281,7 @@ N: 6-bit rc/beta number (1-63)
<div class="memproto"> <div class="memproto">
<table class="memname"> <table class="memname">
<tr> <tr>
<td class="memname">char const* const ripple::BuildInfo::versionString = &quot;1.9.2-rc1&quot;</td> <td class="memname">char const* const ripple::BuildInfo::versionString = &quot;1.9.2&quot;</td>
</tr> </tr>
</table> </table>
</div><div class="memdoc"> </div><div class="memdoc">