mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-21 20:25:51 +00:00
Update/remove legacy links
This commit is contained in:
mDuo13
@@ -66,7 +66,7 @@ XRPは、XRP Ledgerの _アカウント_ （ _ウォレット_ や _アドレス
|
||||
|
||||
<!-- STYLE_OVERRIDE: hot wallet, warm wallet, cold wallet, wallet -->
|
||||
|
||||
Rippleが推奨するベストプラクティスに従い、Alpha Exchangeは、XRP Ledgerに最低2つのアカウントを作成する必要があります。シークレットキーが悪用された場合の危険を最小限にとどめるため、Rippleでは、[ _コールドアカウント_ 、 _ホットアカウント_ 、 _ウォームアカウント_ ](https://ripple.com/build/issuing-operational-addresses/)（それぞれコールドウォレット、ホットウォレット、ウォームウォレットとも呼ばれる）の作成をお勧めしています。コールド/ホット/ウォームのモデルは、セキュリティと利便性のバランスをとるためのものです。XRPを上場する取引所は、以下のアカウントを作成する必要があります。
|
||||
Rippleが推奨するベストプラクティスに従い、Alpha Exchangeは、XRP Ledgerに最低2つのアカウントを作成する必要があります。シークレットキーが悪用された場合の危険を最小限にとどめるため、Rippleでは、[ _コールドアカウント_ 、 _ホットアカウント_ 、 _ウォームアカウント_ ](../../concepts/accounts/account-types.md)（それぞれコールドウォレット、ホットウォレット、ウォームウォレットとも呼ばれる）の作成をお勧めしています。コールド/ホット/ウォームのモデルは、セキュリティと利便性のバランスをとるためのものです。XRPを上場する取引所は、以下のアカウントを作成する必要があります。
|
||||
|
||||
* 大部分のXRPと顧客の資金を維持する[ _コールドウォレット_ ](../../concepts/accounts/account-types.md#発行アドレス)。取引所にとって、これはユーザが[預入れ](#取引所へのxrpの入金)をするアドレスです。 セキュリティを最適化するため、このアカウントのシークレットキーはオフラインにする必要があります。
|
||||
|
||||
|
||||
@@ -11,9 +11,9 @@ author: Rome Reginelli
|
||||
---
|
||||
# Dev Portal Adds rippled APIs
|
||||
|
||||
Today, the [Ripple Dev Portal](https://developers.ripple.com/) gets a big boost of content and usability. The new additions to our development portal include thorough and tested documentation of all the public API methods for our core server software, ‘rippled’, alongside a host of improvements in styling and formatting, as well as new introductory material to give you direction in navigating the sea of Ripple technology.
|
||||
Today, the Ripple Dev Portal gets a big boost of content and usability. The new additions to our development portal include thorough and tested documentation of all the public API methods for our core server software, ‘rippled’, alongside a host of improvements in styling and formatting, as well as new introductory material to give you direction in navigating the sea of Ripple technology.
|
||||
|
||||
This update brings very crucial content into the fold of documentation that's thorough, complete, and software-tested. Today, you can access [full specs and usage information for all 20+ public methods in the rippled WebSocket API](https://developers.ripple.com/rippled-api.html).
|
||||
This update brings very crucial content into the fold of documentation that's thorough, complete, and software-tested. Today, you can access [full specs and usage information for all 20+ public methods in the rippled WebSocket API](/docs/references/http-websocket-apis/public-api-methods).
|
||||
|
||||
<!-- BREAK -->
|
||||
|
||||
|
||||
@@ -8,8 +8,10 @@ markdown:
|
||||
---
|
||||
# Do You Have What It Takes to Be a Gateway?
|
||||
|
||||
We're proud to announce the first release of [our new Gateway Guide](https://developers.ripple.com/become-an-xrp-ledger-gateway.html), a comprehensive manual to operating a gateway in the Ripple network. Whether you're trying to understand [how a gateway makes revenue](https://developers.ripple.com/become-an-xrp-ledger-gateway.html#fees-and-revenue-sources), or how to use the [authorized accounts](https://developers.ripple.com/become-an-xrp-ledger-gateway.html#authorized-trust-lines) feature, or even just [what a warm wallet is](https://developers.ripple.com/issuing-and-operational-addresses.html), the gateway guide has you covered.
|
||||
We're proud to announce the first release of our new Gateway Guide, a comprehensive manual to operating a gateway in the Ripple network. Whether you're trying to understand how a gateway makes revenue, or how to use the authorized accounts feature, or even just what a warm wallet is, the gateway guide has you covered.
|
||||
|
||||
The guide comes with step-by-step, diagrammed explanations of typical gateway operations, a hefty [list of precautions](https://developers.ripple.com/become-an-xrp-ledger-gateway.html#precautions) to make your gateway safer, and concrete examples of all the API calls you need to perform in order to get your gateway accounts set up and secure.
|
||||
The guide comes with step-by-step, diagrammed explanations of typical gateway operations, a hefty list of precautions to make your gateway safer, and concrete examples of all the API calls you need to perform in order to get your gateway accounts set up and secure.
|
||||
|
||||
We're proud of all the work we've done to make the business of running a gateway easier, but there's still more work to do. If you have any questions, comments, or ideas, please send feedback to <developers@ripple.com> - or post it on our forums. We'd love to hear from you!
|
||||
|
||||
> _Editor's note, 2025: This guide is now obsolete and removed. For the nearest modern equivalent, see the [Stablecoin Issuer use case](/docs/use-cases/tokenization/stablecoin-issuer)._
|
||||
|
||||
@@ -20,7 +20,7 @@ The Data API also includes a lot of new capabilities, including:
|
||||
- a new endpoint to show account balance changes
|
||||
- new metrics in transaction stats
|
||||
|
||||
We are making these changes quickly and are focusing our resources on building out and testing new endpoints. Documentation for the Data API will soon be available on [ripple.com/build](http://ripple.com/build). The API will live at [data.ripple.com](http://data.ripple.com). In the meantime, you can look through the [Data API in GitHub](https://github.com/ripple/rippled-historical-database/blob/develop/README.md).
|
||||
We are making these changes quickly and are focusing our resources on building out and testing new endpoints. Documentation for the Data API will soon be available on `ripple.com/build`. The API will live at `data.ripple.com`. In the meantime, you can look through the [Data API in GitHub](https://github.com/ripple/rippled-historical-database/blob/develop/README.md).
|
||||
|
||||
Because we are pulling all of the data endpoints under one API, we are shutting down some of our underutilized endpoints that are relying on infrastructure we are not moving forward with. The first shutdown will be CouchDB on August 19th, which we used early on for Ripple Charts. We are replacing some of the endpoints that hit CouchDB in the Data API, but other, less frequently used calls are being removed. In the next few months, we will also be shutting down the Ripple Charts API and replacing aspects of that by expanding the Data API. The Historical Database API – version one – will live in parallel to the Data API as we make this transition. It will be deprecated by the end of the year.
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ markdown:
|
||||
|
||||
At Ripple Labs, our goal is to expand the size and diversity of the Ripple consensus network by enabling people to easily run rippled validators and understand how those validators perform. We aim to create a network where validating participants are well known and respected by gathering and publicizing identity information of validators in addition to performance statistics.
|
||||
|
||||
Today, we are excited to announce the launch of the Ripple Validator Registry at [xrpcharts.ripple.com/#/validators](https://xrpcharts.ripple.com/#/validators). The Validator Registry gathers and publishes data for all network validators, enabling rippled operators to determine which validators to trust. An [http-based API](https://data.ripple.com/v2/network/validators) is also available for dynamically constructing rippled configurations.
|
||||
Today, we are excited to announce the launch of the Ripple Validator Registry at `xrpcharts.ripple.com/#/validators`. The Validator Registry gathers and publishes data for all network validators, enabling rippled operators to determine which validators to trust. An http-based API is also available for dynamically constructing rippled configurations. _[2025 Update: See <https://livenet.xrpl.org/network/validators> for the modern equivalent of the validator registry.]_
|
||||
|
||||
|
||||
## Build a UNL
|
||||
@@ -25,6 +25,6 @@ The Validator Registry provides several metrics for each validator based on upti
|
||||
- disagreement - the percentage of ledgers validated by the validator that did not pass consensus
|
||||
|
||||
### Identity
|
||||
Network participants are unlikely to trust validators without knowing who is operating them. To address this concern, validator operators can associate their validator with a web domain that they operate by following the steps on the [Ripple Dev Portal](https://ripple.com/build/rippled-apis/rippled-setup/#domain-verification). The Validator Registry verifies these domains and lists them with the validators.
|
||||
Network participants are unlikely to trust validators without knowing who is operating them. To address this concern, validator operators can associate their validator with a web domain that they operate by following the steps for [Domain Verification](https://xrpl.org/docs/references/xrp-ledger-toml#domain-verification). The Validator Registry verifies these domains and lists them with the validators.
|
||||
|
||||
As the consensus network continues to grow, we hope the Validator Registry plays a key role in decentralizing and strengthening the network through open data.
|
||||
|
||||
@@ -12,14 +12,14 @@ markdown:
|
||||
|
||||
The Data team is proud to announce the release of the [Ripple Data API v2.2](https://github.com/ripple/rippled-historical-database/releases/tag/v2.2.0)! This release includes lots of new features, including a total of 15 new methods, improvements in data quality, and documentation.
|
||||
|
||||
One of the biggest changes in the new version is the incorporation of data relating to the Ripple network itself. This includes expanded information on [validator reports](https://ripple.com/build/data-api-v2/#get-daily-validator-reports), [network topology](https://ripple.com/build/data-api-v2/#get-topology), and the [XRP transaction costs](https://ripple.com/build/data-api-v2/#get-transaction-costs) currently being paid to the network. You can interact with all of the new methods using our [Data API Tool](https://ripple.com/build/data-api-tool/).
|
||||
One of the biggest changes in the new version is the incorporation of data relating to the Ripple network itself. This includes expanded information on validator reports, network topology, and the XRP transaction costs currently being paid to the network. You can interact with all of the new methods using our Data API Tool.
|
||||
|
||||
Also part of the new release is a method to calculate the [distribution of XRP](https://ripple.com/build/data-api-v2/#get-xrp-distribution) from Ripple (the company) to others, along with the total amount of XRP in existence. The [XRP Portal](https://ripple.com/xrp-portal/) is already using the new method to report the most recent totals automatically.
|
||||
Also part of the new release is a method to calculate the distribution of XRP from Ripple (the company) to others, along with the total amount of XRP in existence. The XRP Portal is already using the new method to report the most recent totals automatically.
|
||||
|
||||
For more information, check out the following resources:
|
||||
|
||||
* [Data API Docs in the Ripple Developer Center](https://ripple.com/build/data-api-v2/)
|
||||
* [Data API source code](https://github.com/ripple/rippled-historical-database)
|
||||
* [Data visualizations on Ripple Charts](https://xrpcharts.ripple.com/)
|
||||
|
||||
_\[Update: Data API docs and Data visualizations on Ripple Charts are no longer available. The links have been removed.\]_
|
||||
|
||||
We look forward to seeing what you developers can do with all this data!
|
||||
|
||||
@@ -10,7 +10,7 @@ markdown:
|
||||
---
|
||||
# The Flow Amendment is Now Available
|
||||
|
||||
The Flow Amendment became available on the Ripple Consensus Ledger in ledger 24,970,753 [(2016-10-21T19:47:22Z)](https://xrpcharts.ripple.com/#/transactions/C06CE3CABA3907389E4DD296C5F31C73B1548CC20BD7B83416C78CD7D4CD38FC).
|
||||
The Flow Amendment became available on the Ripple Consensus Ledger in ledger 24,970,753 [(2016-10-21T19:47:22Z)](https://livenet.xrpl.org/transactions/C06CE3CABA3907389E4DD296C5F31C73B1548CC20BD7B83416C78CD7D4CD38FC).
|
||||
|
||||
This amendment replaces the payment processing engine with a more robust and efficient rewrite called the Flow engine. The new payments engine adds no new features, but improves efficiency and robustness in payment handling.
|
||||
|
||||
@@ -21,23 +21,23 @@ This amendment replaces the payment processing engine with a more robust and eff
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
If you operate a `rippled` server but don’t upgrade to version 0.33.0 or later, immediately, then your server will become [amendment blocked](https://ripple.com/build/amendments/#amendment-blocked), meaning that your server:
|
||||
If you operate a `rippled` server but don’t upgrade to version 0.33.0 or later, immediately, then your server will become [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that your server:
|
||||
|
||||
* Cannot determine the validity of a ledger
|
||||
* Cannot submit or process transactions
|
||||
* Does not participate in the consensus process
|
||||
* Does not vote on future amendments
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
For other platforms, please [compile version 0.33.0 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.33.0 from source](https://github.com/XRPLF/rippled/tree/0.33.0/Builds).
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Forum _(Shut down. Formerly `forum.ripple.com`)_
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -10,7 +10,7 @@ markdown:
|
||||
---
|
||||
# The Flow Amendment Will Soon Be Available
|
||||
|
||||
A majority of `rippled` validators voted to enable the [Flow Amendment](https://ripple.com/build/amendments/#flow), which is scheduled to become active on the protocol on Thursday, 2016-10-20. This amendment replaces the payment processing engine with a more robust and efficient rewrite called the Flow engine. The new payments engine adds no new features, but improves efficiency and robustness in payment handling.
|
||||
A majority of `rippled` validators voted to enable the [Flow Amendment](/resources/known-amendments.md#flow), which is scheduled to become active on the protocol on Thursday, 2016-10-20. This amendment replaces the payment processing engine with a more robust and efficient rewrite called the Flow engine. The new payments engine adds no new features, but improves efficiency and robustness in payment handling.
|
||||
|
||||
## Action Required
|
||||
|
||||
@@ -18,7 +18,7 @@ A majority of `rippled` validators voted to enable the [Flow Amendment](https://
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
If you operate a `rippled` server but don’t upgrade to version 0.33.0 by Thursday, 2016-10-20, when Flow is expected to be enabled via Amendment, then your server will become [amendment blocked](https://ripple.com/build/amendments/#amendment-blocked), meaning that your server:
|
||||
If you operate a `rippled` server but don’t upgrade to version 0.33.0 by Thursday, 2016-10-20, when Flow is expected to be enabled via Amendment, then your server will become [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that your server:
|
||||
|
||||
* Cannot determine the validity of a ledger
|
||||
* Cannot submit or process transactions
|
||||
@@ -27,17 +27,17 @@ If you operate a `rippled` server but don’t upgrade to version 0.33.0 by Thurs
|
||||
|
||||
If the Flow amendment is vetoed or does not pass, then your server will not become amendment blocked and should continue to operate.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
For other platforms, please [compile version 0.33.0-hf1 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.33.0-hf1 from source](https://github.com/XRPLF/rippled/blob/0.33.0-hf1/Builds).
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: support@ripple.com
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -10,7 +10,7 @@ markdown:
|
||||
---
|
||||
# The Flow Amendment is Open for Voting
|
||||
|
||||
Originally introduced in `rippled` [version 0.32.1](https://developers.ripple.com/blog/2016/rippled-0.32.1.html), but later [vetoed](https://developers.ripple.com/blog/2016/flowv2-vetoed.html) after a flaw was discovered in the code while testing, the new [Flow Amendment](https://ripple.com/build/amendments/#flow) is now open for voting. This amendment replaces the payment processing engine with a more robust and efficient rewrite called the Flow engine. The new payments engine adds no new features, but improves efficiency and robustness in payment handling.
|
||||
Originally introduced in `rippled` [version 0.32.1](/blog/2016/rippled-0.32.1.md), but later [vetoed](/blog/2016/flowv2-vetoed.md) after a flaw was discovered in the code while testing, the new [Flow Amendment](/resources/known-amendments.md#flow) is now open for voting. This amendment replaces the payment processing engine with a more robust and efficient rewrite called the Flow engine. The new payments engine adds no new features, but improves efficiency and robustness in payment handling.
|
||||
|
||||
|
||||
## Action Required
|
||||
@@ -19,7 +19,7 @@ Originally introduced in `rippled` [version 0.32.1](https://developers.ripple.co
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
If you operate a `rippled` server but don’t upgrade to version 0.33.0 by Thursday, 2016-10-20, when Flow is expected to be enabled via Amendment, then your server will become [amendment blocked](https://ripple.com/build/amendments/#amendment-blocked), meaning that your server:
|
||||
If you operate a `rippled` server but don’t upgrade to version 0.33.0 by Thursday, 2016-10-20, when Flow is expected to be enabled via Amendment, then your server will become [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that your server:
|
||||
|
||||
* Cannot determine the validity of a ledger
|
||||
* Cannot submit or process transactions
|
||||
@@ -28,16 +28,16 @@ If you operate a `rippled` server but don’t upgrade to version 0.33.0 by Thurs
|
||||
|
||||
If the Flow amendment is vetoed or does not pass, then your server will not become amendment blocked and should continue to operate.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
For other platforms, please [compile version 0.33.0-hf1 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.33.0-hf1 from source](https://github.com/XRPLF/rippled/blob/0.33.0-hf1/Builds).
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: support@ripple.com
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -10,7 +10,7 @@ markdown:
|
||||
---
|
||||
# The FlowV2 Amendment Was Vetoed
|
||||
|
||||
The `rippled` team found a flaw in FlowV2 while testing. As a result, the Ripple network has [vetoed](https://ripple.com/build/amendments/#amendment-voting) the new payment engine amendment. [Originally](https://developers.ripple.com/blog/2016/rippled-0.32.1.html), the [FlowV2 amendment](https://ripple.com/build/amendments/#flowv2) was planned to replace `rippled`’s payment processing engine with a more robust and efficient implementation. It was previously expected to become active on Wednesday, 2016-08-24.
|
||||
The `rippled` team found a flaw in FlowV2 while testing. As a result, the Ripple network has [vetoed](/docs/concepts/networks-and-servers/amendments#amendment-voting) the new payment engine amendment. [Originally](/blog/2016/rippled-0.32.1.md), the [FlowV2 amendment](/resources/known-amendments.md#flowv2) was planned to replace `rippled`’s payment processing engine with a more robust and efficient implementation. It was previously expected to become active on Wednesday, 2016-08-24.
|
||||
|
||||
A corrected version of the payment processing engine has been created and is now undergoing further testing. It is scheduled to be included in a future version of `rippled` as an amendment called [Flow](https://github.com/seelabs/rippled/blob/6466629f935821583eeddadbd06fabd9ea0875d0/src/ripple/app/main/Amendments.cpp#L50-L51).
|
||||
|
||||
@@ -28,11 +28,11 @@ To veto the amendment, add the following, single line, under the `[veto_amendmen
|
||||
|
||||
## Learn, Ask Questions, and Discuss
|
||||
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing: <https://ripple.com/build/>
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
### Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* The Ripple Dev Blog: <https://developers.ripple.com/blog/>
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* XRP Chat: <http://www.xrpchat.com>
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -10,7 +10,7 @@ markdown:
|
||||
---
|
||||
# The FlowV2 Amendment is Open for Voting
|
||||
|
||||
The [FlowV2 Amendment](https://ripple.com/build/amendments/#flowv2) is now open for voting. This amendment replaces the payment processing engine with a more robust and efficient rewrite called the FlowV2 engine. The new version of the payment processing engine is intended to follow the same rules as the old engine. However, the new engine occasionally produces different results due to floating point rounding.
|
||||
The [FlowV2 Amendment](/resources/known-amendments.md#flowv2) is now open for voting. This amendment replaces the payment processing engine with a more robust and efficient rewrite called the FlowV2 engine. The new version of the payment processing engine is intended to follow the same rules as the old engine. However, the new engine occasionally produces different results due to floating point rounding.
|
||||
|
||||
The FlowV2 Engine also makes it easier to improve and expand the payment engine with further Amendments. Ripple’s validators will vote in favor of the FlowV2 amendment. We expect the new feature to become active on Wednesday, 2016-08-24.
|
||||
|
||||
@@ -24,17 +24,17 @@ If you operate a `rippled` server, you should upgrade to version 0.32.1 by Wedne
|
||||
|
||||
If you operate a `rippled` server but don’t upgrade to version 0.32.1 by Wednesday, 2016-08-24 (when FlowV2 is expected to become available via Amendment) then your server will become "amendment blocked" and unable to process transactions or evaluate the validity of ledgers.
|
||||
|
||||
For instruction on updating `rippled` on supported platforms, see: <https://ripple.com/build/rippled-setup/#updating-rippled>
|
||||
For instruction on updating `rippled` on supported platforms, see: </docs/infrastructure/installation/update-rippled-automatically-on-linux>
|
||||
|
||||
For other platforms, please compile version 0.32.1 from source. For details, see <https://github.com/ripple/rippled/tree/master/Builds>
|
||||
For other platforms, please [compile version 0.32.1 from source](https://github.com/XRPLF/rippled/tree/0.32.1/Builds).
|
||||
|
||||
## Learn, Ask Questions, and Discuss
|
||||
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing: <https://ripple.com/build/>
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
## Other Resources
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* The Ripple Dev Blog: <https://developers.ripple.com/blog/>
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: support@ripple.com
|
||||
* XRP Chat: <http://www.xrpchat.com>
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -12,11 +12,13 @@ markdown:
|
||||
|
||||
Ripple is proud to announce an improved, unified interface to the Ripple Consensus Ledger: the new **RippleAPI**! RippleAPI merges ripple-lib and Ripple-REST into a single high-level interface for JavaScript that is fully-documented, fully-tested, schema-validated, stateless, and easier to use.
|
||||
|
||||
> _Editor's note: RippleAPI is obsolete. This post has been edited to remove dead links, but otherwise preserved in its original form. For a modern equivalent, see [xrpl.js](https://js.xrpl.org/)._
|
||||
|
||||
If you’re excited to get started with the new RippleAPI right away, jump right in with the following resources:
|
||||
|
||||
1. [RippleAPI Beginners Guide](https://ripple.com/build/rippleapi-beginners-guide/) - A tutorial that introduces the basics of RippleAPI, even if you have minimal prior experience writing JavaScript applications.
|
||||
2. [RippleAPI Reference](https://ripple.com/build/rippleapi/) - A thorough reference of all methods and features contained in the new API.
|
||||
3. [Sample Code](https://github.com/ripple/ripple-lib/tree/develop/docs/samples) - Additional code samples for a growing variety of use cases.
|
||||
1. **RippleAPI Beginners Guide** - A tutorial that introduces the basics of RippleAPI, even if you have minimal prior experience writing JavaScript applications.
|
||||
2. **RippleAPI Reference** - A thorough reference of all methods and features contained in the new API.
|
||||
3. **Sample Code** - Additional code samples for a growing variety of use cases.
|
||||
4. [`ripple-lib` on GitHub](https://github.com/ripple/ripple-lib) - The RippleAPI source code is available under an open-source license so you can freely download, modify, and contribute back to the project.
|
||||
|
||||
For more information on how and why we built RippleAPI, read on.
|
||||
@@ -33,7 +35,7 @@ In order to better focus our efforts as a company, as well as providing a better
|
||||
|
||||
Unfortunately, all good things come to an end, and this is the end of the line for Ripple-REST. We are no longer developing or supporting Ripple-REST, and we recommend you migrate your applications away from it. Fortunately, RippleAPI also includes an [experimental REST-like HTTP API](https://github.com/ripple/ripple-lib/blob/0.17.1/src/index.js#L7-L8), although this interface is currently unsupported.
|
||||
|
||||
Meanwhile, the [`rippled` APIs](https://ripple.com/build/rippled-apis/) continue to provide an alternative method of interacting with the Ripple Consensus Ledger, providing maximum power at a cost of increased complexity, so you can choose the tradeoffs that are best for your use case.
|
||||
Meanwhile, the [`rippled` APIs](/docs/references/http-websocket-apis) continue to provide an alternative method of interacting with the Ripple Consensus Ledger, providing maximum power at a cost of increased complexity, so you can choose the tradeoffs that are best for your use case.
|
||||
|
||||
## Source Code Improvements
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ markdown:
|
||||
---
|
||||
# Multi-Signing Now Available #
|
||||
|
||||
As [predicted previously](https://developers.ripple.com/blog/2016/multisign-reminder.html), multi-signing became available on the Ripple Consensus Ledger this afternoon in Pacific time ([2016-06-27T11:34:41Z](https://xrpcharts.ripple.com/#/transactions/168F8B15F643395E59B9977FC99D6310E8708111C85659A9BAF8B9222EEAC5A7), to be exact).
|
||||
As [predicted previously](/blog/2016/multisign-reminder), multi-signing became available on the Ripple Consensus Ledger this afternoon in Pacific time ([2016-06-27T11:34:41Z](https://xrpcharts.ripple.com/#/transactions/168F8B15F643395E59B9977FC99D6310E8708111C85659A9BAF8B9222EEAC5A7), to be exact).
|
||||
|
||||
Multi-signing provides more flexibility for sending transactions from your Ripple address. You can use multi-signing alongside a master key pair or regular key pair, or you can disable your other keys and use multi-signing exclusively. You can set and update a list of up to 8 signers, with customizable weights and quorum enabling many different use cases. The members of your signer list can be any Ripple addresses, whether they're funded addresses in the ledger or not.
|
||||
|
||||
@@ -25,20 +25,20 @@ The Ripple Consensus Ledger's multi-signing feature also allows signers to indep
|
||||
|
||||
1. Include the signer's address in your SignerList.
|
||||
2. Fund the signer's address in the ledger.
|
||||
3. Assign a [Regular Key Pair](https://ripple.com/build/transactions/#setregularkey) to the signer's address and disable its master key. (Funded addresses can only sign using their master key pair if it's not disabled.)
|
||||
3. [Assign a Regular Key Pair](/docs/tutorials/how-tos/manage-account-settings/assign-a-regular-key-pair) to the signer's address and disable its master key. (Funded addresses can only sign using their master key pair if it's not disabled.)
|
||||
4. Have that signer use its regular key pair to contribute to your multi-signatures.
|
||||
|
||||
|
||||
## Further Reading ##
|
||||
|
||||
- [Multi-Signing Summary](https://ripple.com/build/transactions/#multi-signing)
|
||||
- [How to Multi-Sign](https://ripple.com/build/how-to-multi-sign/)
|
||||
- [MultiSign Amendment](https://ripple.com/build/amendments/#multisign)
|
||||
- [Multi-Signing Summary](/docs/concepts/accounts/multi-signing)
|
||||
- [How to Multi-Sign](/docs/tutorials/how-tos/manage-account-settings/send-a-multi-signed-transaction)
|
||||
- [MultiSign Amendment](/resources/known-amendments.md#multisign)
|
||||
|
||||
|
||||
## Other resources: ##
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* The Ripple Dev Blog: <https://developers.ripple.com/blog/>
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: [support@ripple.com](mailto:support@ripple.com)
|
||||
* XRP Chat: <http://www.xrpchat.com/>
|
||||
|
||||
@@ -12,8 +12,8 @@ markdown:
|
||||
|
||||
The multi-signing amendment is currently supported by the majority of voting validators on Ripple, and is scheduled to become active on the protocol on Monday, **2016-06-27**. For more information, please see the multi-signing documentation in the Ripple Developer Portal:
|
||||
|
||||
* [How to Multi-Sign](https://ripple.com/build/how-to-multi-sign/)
|
||||
* [MultiSign Amendment Information](https://ripple.com/build/amendments/#multisign)
|
||||
* [How to Multi-Sign](/docs/tutorials/how-tos/manage-account-settings/send-a-multi-signed-transaction)
|
||||
* [MultiSign Amendment Information](/resources/known-amendments.md#multisign)
|
||||
|
||||
To continue receiving updates about the `rippled` server, please subscribe to the Ripple Server Google Group:
|
||||
|
||||
|
||||
@@ -13,5 +13,5 @@ markdown:
|
||||
The latest version of `rippled`, the core server of the Ripple Consensus Ledger, is here! Version 0.30.1 contains lots of small features and improvements, including updates to account\_offers, server\_info, peer subscriptions, and more. It also adds several optimizations to the consensus process that have already led to a dramatic increase in the number of ledgers validated per day! Learn more:
|
||||
|
||||
- See the full [rippled 0.30.1 Release Notes](https://github.com/ripple/rippled/releases/0.30.1).
|
||||
- See our [installation instructions](https://ripple.com/build/rippled-setup/#installing-rippled) to set up `rippled` yourself.
|
||||
- Visit the [Developer Center](https://ripple.com/build/) for more information on how to use the Ripple Consensus Ledger.
|
||||
- See our [installation instructions](/docs/infrastructure/installation) to set up `rippled` yourself.
|
||||
- Visit the Developer Center for more information on how to use the Ripple Consensus Ledger.
|
||||
|
||||
@@ -23,8 +23,8 @@ The `rippled` team is proud to announce a bundle of related news items:
|
||||
|
||||
We recommend all users, especially validators, upgrade as soon as possible:
|
||||
|
||||
* For Red Hat Enterprise Linux 7 or CentOS, you can [update to the new version using `yum`](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
* For other platforms, please [compile the new version from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
* For Red Hat Enterprise Linux 7 or CentOS, you can [update to the new version using `yum`](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
* For other platforms, please [compile the new version from source](https://github.com/XRPLF/rippled/tree/0.31.2/Builds).
|
||||
* For more information, see the `rippled` [0.31.2 release notes](https://github.com/ripple/rippled/releases/tag/0.31.2) and [0.31.0 release notes](https://github.com/ripple/rippled/releases/tag/0.31.0) on GitHub.
|
||||
|
||||
## Amendments System ##
|
||||
@@ -33,11 +33,11 @@ Amendments are a new feature introduced in `rippled` 0.31.0. The Amendments syst
|
||||
|
||||
The next amendment, MultiSign, introduces a way to authorize transactions using multiple signatures, for greater security and flexibility.
|
||||
|
||||
For more information, see [Amendments in the Ripple Developer Center](https://ripple.com/build/amendments/).
|
||||
For more information, see [Amendments](/docs/concepts/networks-and-servers/amendments).
|
||||
|
||||
## Transaction Cost Changes ##
|
||||
|
||||
We have brought two significant changes to [transaction costs](https://ripple.com/build/transaction-cost/) in the `rippled` 0.31 releases. First, the FeeEscalation amendment changed the way the network escalates transaction costs under load. Second, `rippled` 0.31.2 has decreased the minimum transaction cost back to its previous value of 0.00001 XRP (10 drops).
|
||||
We have brought two significant changes to [transaction costs](/docs/concepts/transactions/transaction-cost) in the `rippled` 0.31 releases. First, the FeeEscalation amendment changed the way the network escalates transaction costs under load. Second, `rippled` 0.31.2 has decreased the minimum transaction cost back to its previous value of 0.00001 XRP (10 drops).
|
||||
|
||||
Previously, transaction costs tended to spike rapidly when the network was under load and drop quickly when the backlog was processed, causing network volatility. As a temporary fix, Ripple configured the official validating servers to always report a load multiplier of 1000 or more. This effectively increased transaction costs from 0.00001 XRP to 0.01 XRP.
|
||||
|
||||
@@ -53,8 +53,9 @@ The `rippled` team is excited to announce that the next feature to be enabled by
|
||||
|
||||
Ripple plans to configure its validators to start voting in favor of the MultiSign amendment on 2016-06-13. If the feature maintains a majority for two weeks after that, multi-signing will become an active part of the protocol starting **2016-06-27**.
|
||||
|
||||
For more information, see the following articles in the Ripple Developer Center:
|
||||
For more information, see the following articles:
|
||||
|
||||
* [MultiSign Amendment](https://ripple.com/build/amendments/#multisign)
|
||||
* [Multi-Signing transaction reference](https://ripple.com/build/transactions/#multi-signing)
|
||||
* [How to Multi-Sign Tutorial](https://ripple.com/build/how-to-multi-sign/)
|
||||
* [MultiSign Amendment](/resources/known-amendments.md#multisign)
|
||||
* [Multi-Signing Overview](/docs/concepts/accounts/multi-signing)
|
||||
* [Tutorial - Set Up Multi-Signing](/docs/tutorials/how-tos/manage-account-settings/set-up-multi-signing)
|
||||
* [Tutorial - Send a Multi-Signed Transaction](/docs/tutorials/how-tos/manage-account-settings/send-a-multi-signed-transaction)
|
||||
|
||||
@@ -14,8 +14,8 @@ Ripple is proud to announce the release of `rippled` version 0.32.0. This releas
|
||||
|
||||
Highlights of this release include:
|
||||
|
||||
* The transaction queue 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. This encourages liquidity for XRP since important transactions now have a more reliable way of getting into the ledger. For more information, see [Queued Transactions](https://ripple.com/build/transaction-cost/#queued-transactions) in the Ripple Developer Portal.
|
||||
* The `server_info` and `server_state` commands now include information on transaction cost multipliers. Customers who want to robustly submit transactions now have additional tools for accurately setting the fee based on changing network conditions. Furthermore, the `fee` command is now available to unprivileged users. For more information, see the [`rippled` API Method Reference](https://ripple.com/build/rippled-apis/#api-methods) in the Ripple Developer Portal.
|
||||
* The transaction queue 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. This encourages liquidity for XRP since important transactions now have a more reliable way of getting into the ledger. For more information, see [Transaction Queue](/docs/concepts/transactions/transaction-queue).
|
||||
* The `server_info` and `server_state` commands now include information on transaction cost multipliers. Customers who want to robustly submit transactions now have additional tools for accurately setting the fee based on changing network conditions. Furthermore, the `fee` command is now available to unprivileged users. For more information, see the [`rippled` API Method Reference](/docs/references/http-websocket-apis).
|
||||
* There's a new WebSocket implementation based on [Beast](https://github.com/vinniefalco/Beast). Use of this implementation is optional. A future version of `rippled` will make this WebSocket implementation the default, with the old implementation removed.
|
||||
|
||||
Read the complete [release notes in GitHub](https://github.com/ripple/rippled/releases/tag/0.32.0).
|
||||
@@ -29,30 +29,32 @@ Read the complete [release notes in GitHub](https://github.com/ripple/rippled/re
|
||||
|
||||
If you operate a `rippled` server but don’t upgrade to version 0.32.0, your server might lose synchronization with the rest of the upgraded network for brief periods of time. That is, the local view of ledgers may be slightly behind the rest of the network.
|
||||
|
||||
For instruction on updating rippled on supported platforms, please see [Updating `rippled`](https://ripple.com/build/rippled-setup/#updating-rippled) in the Ripple Developer Center.
|
||||
For instruction on updating rippled on supported platforms, please see [Updating `rippled`](/docs/infrastructure/installation/update-rippled-automatically-on-linux) in the Ripple Developer Center.
|
||||
|
||||
The md5sum for the rpm is: **1b37fd80fd869e42a715f17a9e30c81a**.
|
||||
The md5sum for the source rpm is: **d43f4d371416b213d6197fb1c630cf44**.
|
||||
|
||||
For other platforms, please compile version 0.32.0 from source. See [`rippled` Build Instructions](https://github.com/ripple/rippled/tree/master/Builds) for details.
|
||||
For other platforms, please [compile version 0.32.0 from source](https://github.com/XRPLF/rippled/tree/0.32.0/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit d22eb0caa25ecfbd373cc9af0347e56031a23646
|
||||
Author: seelabs <scott.determan@yahoo.com>
|
||||
Date: Fri Jun 24 11:30:09 2016 -0400
|
||||
|
||||
Set version to 0.32.0
|
||||
```
|
||||
|
||||
## Network Update ##
|
||||
The Ripple operations team plans to deploy version 0.32.0 to all rippled servers under its operational control, including private clusters, starting at 1:00 PM PDT on Wednesday, 2016-06-29. The deployment is expected to complete within 4 hours.
|
||||
|
||||
## Learn, ask questions, and discuss ##
|
||||
Ripple supported documentation including detailed example API calls and web tools for API testing are located on the Ripple Developer Portal: <https://ripple.com/build/>
|
||||
Ripple supported documentation including detailed example API calls and web tools for API testing are located on the Ripple Developer Portal.
|
||||
|
||||
### Other resources: ###
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* The Ripple Dev Blog: <https://developers.ripple.com/blog/>
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: [support@ripple.com](mailto:support@ripple.com)
|
||||
* XRP Chat: <http://www.xrpchat.com/>
|
||||
|
||||
@@ -15,7 +15,7 @@ Ripple is proud to announce the release of `rippled` version 0.32.1, which intro
|
||||
Highlights of this release include:
|
||||
|
||||
* A new, optional WebSocket implementation based on [Beast](https://github.com/vinniefalco/Beast). See below for details.
|
||||
* An improved version of the payment code, which we expect to be available via an [Amendment named "FlowV2"](https://ripple.com/build/amendments/#flowv2) on Wednesday, 2016-08-24. See below for details.
|
||||
* An improved version of the payment code, which we expect to be available via an [Amendment named "FlowV2"](/resources/known-amendments.md#flowv2) on Wednesday, 2016-08-24. See below for details.
|
||||
|
||||
## Actions Required
|
||||
|
||||
@@ -25,41 +25,42 @@ Highlights of this release include:
|
||||
## Impact of Not Upgrading
|
||||
If you operate a rippled server but don’t upgrade to version 0.32.1 by Wednesday, 2016-08-24, when FlowV2 is expected to become available via Amendment, then your server might lose synchronization with the rest of the upgraded network for brief periods of time. That is, the local view of ledgers may be slightly behind the rest of the network. Any rippled server operator running versions prior to 0.32.1, will also become amendment blocked.
|
||||
|
||||
For supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The md5sum for the rpm is: 5dcdcef01f3cfc452b0b503eaaeb07bb
|
||||
|
||||
The md5sum for the source rpm is: 3180fca1e83001307346f85628823a9c
|
||||
|
||||
For other platforms, please [compile version 0.32.1 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.32.1 from source](https://github.com/XRPLF/rippled/tree/0.32.1/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 1ff972fbd3b82f0f7062f05f64f1abd5e274a7bc
|
||||
Author: Nik Bougalis <nikb@bougalis.net>
|
||||
Date: Fri Jul 29 12:52:26 2016 -0700
|
||||
|
||||
Set version to 0.32.1
|
||||
|
||||
```
|
||||
|
||||
## Network Update
|
||||
The Ripple operations team plans to deploy version 0.32.1 to all rippled servers under its operational control, including private clusters, starting at 1:00 PM PDT on Thursday, 2016-08-04. The deployment is expected to complete within 4 hours. The network will continue operating during deployment and no outage is expected.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: support@ripple.com
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
|
||||
## Full Release Notes
|
||||
The `rippled` 0.32.1 release includes an improved version of the payment code, which we expect to be available via Amendment on Wednesday, 2016-08-24 with the name FlowV2, and a completely new implementation of the WebSocket protocol for serving clients.
|
||||
|
||||
You can [update to the new version](https://ripple.com/build/rippled-setup/#updating-rippled) on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please [compile the new version from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
You can [update to the new version](/docs/infrastructure/installation/update-rippled-automatically-on-linux) on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please [compile the new version from source](https://github.com/XRPLF/rippled/tree/0.32.1/Builds).
|
||||
|
||||
**New and Updated Features**
|
||||
|
||||
|
||||
@@ -20,21 +20,23 @@ Ripple has released `rippled` version 0.33.0-hf1, which fixes a JSON parsing iss
|
||||
|
||||
If you operate a `rippled` server and are experiencing a `jsonInvalid` error response to client requests, but don’t upgrade to version 0.33.0-hf1, then your server will continue to experience failing client requests.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The md5sum for the rpm is: f181f1fc801e3387487d246f9a975517
|
||||
|
||||
The md5sum for the source rpm is: 7993f125ed05bfeeda4e091761021429
|
||||
|
||||
For other platforms, please [compile version 0.33.0-hf1 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.33.0-hf1 from source](https://github.com/XRPLF/rippled/blob/0.33.0-hf1/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 98f878cf10a32e26021b6a6ed44990bccbbc92c2
|
||||
Author: Vinnie Falco <vinnie.falco@gmail.com>
|
||||
Date: Sat Oct 1 12:12:34 2016 -0400
|
||||
|
||||
Set version to 0.33.0-hf1
|
||||
```
|
||||
|
||||
## Bug Fixes
|
||||
|
||||
@@ -44,11 +46,11 @@ Fix a JSON parsing issue that can fail to parse valid JSON requests when the dat
|
||||
The Ripple operations team has deployed version 0.33.0-hf1 to all client facing `rippled` servers under its operational control.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: support@ripple.com
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -14,9 +14,9 @@ Ripple has released `rippled` version 0.33.0, which introduces several new enhan
|
||||
|
||||
Highlights of this release include:
|
||||
|
||||
* An improved version of the payment code, which Ripple expects to be available via an [Amendment named "Flow"](https://ripple.com/build/amendments/#flow) on Wednesday, 2016-10-20. See below for details.
|
||||
* Payment Channels that permit scalable, off-ledger checkpoints for high volume, low value payments flowing in a single direction, which Ripple expects to be activated via an [Amendment named “PayChan”](https://ripple.com/build/amendments/#paychan) on a future date TBA. See below for details.
|
||||
* SHAMapV2 changes the hash tree structure that rippled uses to represent a ledger, which Ripple expects to be activated via an [Amendment named SHAMapV2](https://ripple.com/build/amendments/#shamapv2) on a future date TBA. See below for details.
|
||||
* An improved version of the payment code, which Ripple expects to be available via an [Amendment named "Flow"](/resources/known-amendments.md#flow) on Wednesday, 2016-10-20. See below for details.
|
||||
* Payment Channels that permit scalable, off-ledger checkpoints for high volume, low value payments flowing in a single direction, which Ripple expects to be activated via an [Amendment named “PayChan”](/resources/known-amendments.md#paychan) on a future date TBA. See below for details.
|
||||
* SHAMapV2 changes the hash tree structure that rippled uses to represent a ledger, which Ripple expects to be activated via an [Amendment named SHAMapV2](/resources/known-amendments.md#shamapv2) on a future date TBA. See below for details.
|
||||
|
||||
## Action Required
|
||||
|
||||
@@ -33,54 +33,56 @@ The Flow amendment is expected to be activated on Wednesday, 2016-10-20. If you
|
||||
|
||||
If the Flow amendment is vetoed or does not pass via majority vote, then your server will not become amendment blocked and should continue to operate.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The md5sum for the rpm is: 5ad8fa43e9acf645a76d0a383eb5600a
|
||||
|
||||
The md5sum for the source rpm is: 38fe8c022e2fe5086f71fb9623a18064
|
||||
|
||||
For other platforms, please [compile version 0.33.0 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.33.0 from source](https://github.com/XRPLF/rippled/tree/0.33.0/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit f05321d501002cd7b8e7fba3ef361834689b3c26
|
||||
Author: Nik Bougalis <nikb@bougalis.net>
|
||||
Date: Thu Sep 29 09:25:46 2016 -0700
|
||||
|
||||
Set version to 0.33.0
|
||||
```
|
||||
|
||||
## Network Update
|
||||
The Ripple operations team plans to deploy version 0.33.0 to all rippled servers under its operational control, including private clusters, starting at 2:00 PM PDT on Thursday, 2016-09-29. The deployment is expected to complete within 4 hours. The network should continue to operate during deployment and no outage is expected.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: support@ripple.com
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
## Full Release Notes
|
||||
|
||||
The `rippled` 0.33.0 release includes:
|
||||
|
||||
* The ["Flow"](https://ripple.com/build/amendments/#flow) amendment. Ripple expects this amendment to be on Wednesday, 2016-10-20.
|
||||
* The ["Flow"](/resources/known-amendments.md#flow) amendment. Ripple expects this amendment to be on Wednesday, 2016-10-20.
|
||||
|
||||
* XRP Payment Channels. Payment channels are a new structure in the ledger designed to support [Interledger Protocol](https://interledger.org/) trust lines as balances get substantial. Ripple expects to be activated via Amendment on a future date (TBA) with the name [“PayChan”](https://ripple.com/build/amendments/#paychan).
|
||||
* XRP Payment Channels. Payment channels are a new structure in the ledger designed to support [Interledger Protocol](https://interledger.org/) trust lines as balances get substantial. Ripple expects to be activated via Amendment on a future date (TBA) with the name [“PayChan”](/resources/known-amendments.md#paychan).
|
||||
|
||||
* Changes to the hash tree structure, which `rippled` uses hash trees to represent a ledger. Ripple expects these changes expect to be available via Amendment on a future date (TBA) with the name [SHAMapV2](https://ripple.com/build/amendments/#shamapv2).
|
||||
* Changes to the hash tree structure, which `rippled` uses hash trees to represent a ledger. Ripple expects these changes expect to be available via Amendment on a future date (TBA) with the name [SHAMapV2](/resources/known-amendments.md#shamapv2).
|
||||
|
||||
You can [update to the new version](https://ripple.com/build/rippled-setup/#updating-rippled) on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please [compile the new version from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
You can [update to the new version](/docs/infrastructure/installation/update-rippled-automatically-on-linux) on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please [compile the new version from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md).
|
||||
|
||||
**New and Updated Features**
|
||||
|
||||
A fixed version of the new payment processing engine, which Ripple initially [announced on Friday, 2016-07-29](https://developers.ripple.com/blog/2016/rippled-0.32.1.html), is expected to be available via Amendment on Wednesday, 2016-10-20 with the name ["Flow"](https://ripple.com/build/amendments/#flow). The new payments code adds no new features, but improves efficiency and robustness in payment handling.
|
||||
A fixed version of the new payment processing engine, which Ripple initially [announced on Friday, 2016-07-29](/blog/2016/rippled-0.32.1.md), is expected to be available via Amendment on Wednesday, 2016-10-20 with the name ["Flow"](/resources/known-amendments.md#flow). The new payments code adds no new features, but improves efficiency and robustness in payment handling.
|
||||
|
||||
Ripple will be introducing changes to the hash tree structure that rippled uses to represent a ledger. Ripple expects these changes to be activated via Amendment on a future date (TBA) with the name [SHAMapV2](https://ripple.com/build/amendments/#shamapv2). The new structure is more compact and efficient than the previous version. This affects how ledger hashes are calculated, but has no other user-facing consequences. The activation of the SHAMapV2 amendment will require brief scheduled allowable downtime, while the changes to the hash tree structure are propagated by the network. Ripple will keep the community updated as we progress towards this date (TBA).
|
||||
Ripple will be introducing changes to the hash tree structure that rippled uses to represent a ledger. Ripple expects these changes to be activated via Amendment on a future date (TBA) with the name [SHAMapV2](/resources/known-amendments.md#shamapv2). The new structure is more compact and efficient than the previous version. This affects how ledger hashes are calculated, but has no other user-facing consequences. The activation of the SHAMapV2 amendment will require brief scheduled allowable downtime, while the changes to the hash tree structure are propagated by the network. Ripple will keep the community updated as we progress towards this date (TBA).
|
||||
|
||||
In an effort to make RCL more scalable and to support [Interledger Protocol](https://interledger.org/) (ILP) trust lines as balances get more substantial, Ripple is introducing XRP Payment Channels, a new structure in the ledger, which we expect to be available via Amendment on a future date (TBA) with the name [“PayChan”](https://ripple.com/build/amendments/#paychan).
|
||||
In an effort to make RCL more scalable and to support [Interledger Protocol](https://interledger.org/) (ILP) trust lines as balances get more substantial, Ripple is introducing XRP Payment Channels, a new structure in the ledger, which we expect to be available via Amendment on a future date (TBA) with the name [“PayChan”](/resources/known-amendments.md#paychan).
|
||||
|
||||
XRP Payment Channels permit scalable, intermittent, off-ledger settlement of ILP trust lines for high volume, low value payments flowing in a single direction. For bidirectional channels, an XRP Payment Channel can be used in each direction. The recipient can claim any unpaid balance at any time. The owner can top off the channel as needed. The owner must wait out a delay to close the channel to give the recipient a chance to supply any claims. The total amount paid increases monotonically as newer claims are issued.
|
||||
|
||||
|
||||
@@ -14,7 +14,7 @@ Ripple has released `rippled` version 0.40.0, which introduces several enhanceme
|
||||
|
||||
Highlights of this release include:
|
||||
|
||||
* Suspended Payments, a new transaction type on the Ripple network that functions similar to an escrow service, which permits users to cryptographically escrow XRP on RCL with an expiration date. Ripple expects Suspended Payments to be enabled via an [Amendment named “SusPay”](https://ripple.com/build/amendments/#suspay) on Tuesday, 2017-01-17. See below for details.
|
||||
* Suspended Payments, a new transaction type on the Ripple network that functions similar to an escrow service, which permits users to cryptographically escrow XRP on RCL with an expiration date. Ripple expects Suspended Payments to be enabled via an [Amendment named “SusPay”](/resources/known-amendments.md#suspay) on Tuesday, 2017-01-17. See below for details.
|
||||
|
||||
## Action Required
|
||||
|
||||
@@ -22,7 +22,7 @@ If you operate a `rippled` server, then you should upgrade to version 0.40.0 by
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
If you operate a `rippled` server but don’t upgrade to version 0.40.0 by Wednesday, 2017-01-17, when SusPay is expected to be activated via Amendment, then your server will become [amendment blocked](https://ripple.com/build/amendments/#amendment-blocked), meaning that your server:
|
||||
If you operate a `rippled` server but don’t upgrade to version 0.40.0 by Wednesday, 2017-01-17, when SusPay is expected to be activated via Amendment, then your server will become [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that your server:
|
||||
|
||||
* Cannot determine the validity of a ledger
|
||||
* Cannot submit or process transactions
|
||||
@@ -32,52 +32,54 @@ If you operate a `rippled` server but don’t upgrade to version 0.40.0 by Wedne
|
||||
|
||||
If the SusPay amendment is vetoed or does not pass via majority vote, then your server will not become amendment blocked.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The md5sum for the rpm is: 27d0d142f29bcde7d240d91d44b5d7dc
|
||||
|
||||
The md5sum for the source rpm is: b3b5ab6897f3c08b492f383ef7763c21
|
||||
|
||||
For other platforms, please [compile version 0.40.0 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.40.0 from source](https://github.com/XRPLF/rippled/tree/0.40.0/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 7fc780dd70faef819eace27a12de35dd1363c069
|
||||
Author: Nik Bougalis <nikb@bougalis.net>
|
||||
Date: Tue Dec 20 09:20:17 2016 -0800
|
||||
|
||||
Set version to 0.40.0
|
||||
```
|
||||
|
||||
## Network Update
|
||||
The Ripple operations team plans to deploy version 0.40.0 to a subset of rippled servers under its operational control configured with the new websocket implementation, starting at 2:00 PM PDT on Thursday, 2017-12-20. The network will continue operating during deployment and no outage is expected.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: support@ripple.com
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
## Full Release Notes
|
||||
|
||||
The `rippled` 0.40.0 release includes Suspended Payments, a new transaction type on the Ripple network that functions similar to an escrow service, which permits users to lock XRP until a cryptographic condition is met or it expires. Ripple expects Suspended Payments to be enabled via an [Amendment named “SusPay”](https://ripple.com/build/amendments/#suspay) on Tuesday, 2017-01-17.
|
||||
The `rippled` 0.40.0 release includes Suspended Payments, a new transaction type on the Ripple network that functions similar to an escrow service, which permits users to lock XRP until a cryptographic condition is met or it expires. Ripple expects Suspended Payments to be enabled via an [Amendment named “SusPay”](/resources/known-amendments.md#suspay) on Tuesday, 2017-01-17.
|
||||
|
||||
You can [update to the new version](https://ripple.com/build/rippled-setup/#updating-rippled) on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please [compile the new version from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
You can [update to the new version](/docs/infrastructure/installation/update-rippled-automatically-on-linux) on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please [compile the new version from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md).
|
||||
|
||||
**New and Updated Features**
|
||||
|
||||
Previously, Ripple [announced](https://developers.ripple.com/blog/2016/rippled-0.33.0.html) the introduction of Payment Channels during the release of rippled version 0.33.0, which permit scalable, off-ledger checkpoints of high volume, low value payments flowing in a single direction. This was the first step in a multi-phase effort to make RCL more scalable and to support [Interledger Protocol](https://interledger.org/interledger.pdf) (ILP). Ripple expects Payment Channels to be enabled via an [Amendment called PayChan](https://ripple.com/build/amendments/#paychan) on a future date to be determined.
|
||||
Previously, Ripple [announced](/blog/2016/rippled-0.33.0.md) the introduction of Payment Channels during the release of rippled version 0.33.0, which permit scalable, off-ledger checkpoints of high volume, low value payments flowing in a single direction. This was the first step in a multi-phase effort to make RCL more scalable and to support [Interledger Protocol](https://interledger.org/interledger.pdf) (ILP). Ripple expects Payment Channels to be enabled via an [Amendment called PayChan](/resources/known-amendments.md#paychan) on a future date to be determined.
|
||||
|
||||
In the second phase towards making RCL more scalable and compatible with ILP, Ripple is introducing Suspended Payments, a new transaction type on the Ripple network that functions similar to an escrow service, which permits users to cryptographically escrow XRP on RCL with an expiration date. Ripple expects Suspended Payments to be enabled via an [Amendment named “SusPay”](https://ripple.com/build/amendments/#suspay) on Tuesday, 2017-01-17.
|
||||
In the second phase towards making RCL more scalable and compatible with ILP, Ripple is introducing Suspended Payments, a new transaction type on the Ripple network that functions similar to an escrow service, which permits users to cryptographically escrow XRP on RCL with an expiration date. Ripple expects Suspended Payments to be enabled via an [Amendment named “SusPay”](/resources/known-amendments.md#suspay) on Tuesday, 2017-01-17.
|
||||
|
||||
A Suspended Payment can be created, which deducts the funds from the sending account. It can then be either fulfilled or canceled. It can only be fulfilled if the fulfillment transaction makes it into a ledger with a CloseTime lower than the expiry date of the transaction. It can be canceled with a transaction that makes it into a ledger with a CloseTime greater than the expiry date of the transaction.
|
||||
|
||||
In the third phase towards making RCL more scalable and compatible with ILP, Ripple plans to introduce additional library support for crypto-conditions, which are distributable event descriptions written in a standard format that describe how to recognize a fulfillment message without saying exactly what the fulfillment is. Fulfillments are cryptographically verifiable messages that prove an event occurred. If you transmit a fulfillment, then everyone who has the condition can agree that the condition has been met. Fulfillment requires the submission of a signature that matches the condition (message hash and public key). This format supports multiple algorithms, including different hash functions and cryptographic signing schemes. Crypto-conditions can be nested in multiple levels, with each level possibly having multiple signatures.
|
||||
|
||||
Lastly, we do not have an update on the [previously announced](https://developers.ripple.com/blog/2016/rippled-0.33.0.html) changes to the hash tree structure that rippled uses to represent a ledger, called [SHAMapV2](https://ripple.com/build/amendments/#shamapv2). This will require brief scheduled allowable downtime while the changes to the hash tree structure are propagated by the network. We will keep the community updated as we progress towards this date (TBA).
|
||||
Lastly, we do not have an update on the [previously announced](/blog/2016/rippled-0.33.0.md) changes to the hash tree structure that rippled uses to represent a ledger, called [SHAMapV2](/resources/known-amendments.md#shamapv2). This will require brief scheduled allowable downtime while the changes to the hash tree structure are propagated by the network. We will keep the community updated as we progress towards this date (TBA).
|
||||
|
||||
* Consensus refactor [(#1874)](https://github.com/ripple/rippled/pull/1874)
|
||||
|
||||
|
||||
@@ -35,6 +35,6 @@ Please refer to the Test Net page for information on generating new test net cre
|
||||
### Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* The Ripple Dev Blog: <https://developers.ripple.com/blog/>
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* XRP Chat: <http://www.xrpchat.com>
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -10,15 +10,15 @@ markdown:
|
||||
---
|
||||
# TrustSetAuth is Now Available
|
||||
|
||||
As [predicted previously](https://developers.ripple.com/blog/2016/trustsetauth-reminder.html), TrustSetAuth became available on the Ripple Consensus Ledger this afternoon (PDT) in ledger 22,721,281 ([2016-07-19T15:10](https://xrpcharts.ripple.com/#/transactions/0E589DE43C38AED63B64FF3DA87D349A038F1821212D370E403EB304C76D70DF)).
|
||||
As [predicted previously](/blog/2016/trustsetauth-reminder.md), TrustSetAuth became available on the Ripple Consensus Ledger this afternoon (PDT) in ledger 22,721,281 ([2016-07-19T15:10](https://xrpcharts.ripple.com/#/transactions/0E589DE43C38AED63B64FF3DA87D349A038F1821212D370E403EB304C76D70DF)).
|
||||
|
||||
This amendment allows pre-authorization of accounting relationships (zero-balance trust lines) when using Authorized Accounts.
|
||||
|
||||
## Action Required
|
||||
|
||||
To remain operational, all `rippled` instances running on a version earlier than 0.31.0 must be [upgraded](https://ripple.com/build/rippled-setup/#updating-rippled) to `rippled` server **[version 0.32.0](https://developers.ripple.com/blog/2016/rippled-0.32.0.html)** immediately.
|
||||
To remain operational, all `rippled` instances running on a version earlier than 0.31.0 must be [upgraded](/docs/infrastructure/installation/update-rippled-automatically-on-linux) to `rippled` server **[version 0.32.0](/blog/2016/rippled-0.32.0.md)** immediately.
|
||||
|
||||
See [Updating `rippled`](https://ripple.com/build/rippled-setup/#updating-rippled) for more information about upgrading `rippled`.
|
||||
See [Updating `rippled`](/docs/infrastructure/installation/update-rippled-automatically-on-linux) for more information about upgrading `rippled`.
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
@@ -30,10 +30,10 @@ With this amendment enabled, currency issuers can authorize other addresses to h
|
||||
|
||||
## Learn More
|
||||
|
||||
For more information, please see the TrustSetAuth documentation in the [Ripple Developer Portal](https://ripple.com/build/):
|
||||
For more information, please see the following documentation:
|
||||
|
||||
* [Authorized Accounts](https://ripple.com/build/gateway-guide/#authorized-accounts)
|
||||
* [Authorized Trust Lines](/docs/concepts/tokens/fungible-tokens/authorized-trust-lines)
|
||||
|
||||
* [Amendments](https://ripple.com/build/amendments/#trustsetauth)
|
||||
* [TrustSetAuth Amendment](/resources/known-amendments.md#trustsetauth)
|
||||
|
||||
To continue receiving updates about the rippled server, please subscribe to the Ripple Server Google Group: https://groups.google.com/forum/#!forum/ripple-server
|
||||
|
||||
@@ -18,18 +18,18 @@ With this amendment enabled, currency issuers can authorize other addresses to h
|
||||
|
||||
## Action Required ##
|
||||
|
||||
To remain operational, all `rippled` instances running on the version below 0.31.0 must be upgraded to `rippled` server **[version 0.32.0](https://developers.ripple.com/blog/2016/rippled-0.32.0.html)** by Tuesday, 2016-07-19.
|
||||
To remain operational, all `rippled` instances running on the version below 0.31.0 must be upgraded to `rippled` server **[version 0.32.0](/blog/2016/rippled-0.32.0.md)** by Tuesday, 2016-07-19.
|
||||
|
||||
## Impact of Not Upgrading ##
|
||||
|
||||
If you operate a `rippled` server on a version below 0.31.0 but do not upgrade to [version 0.32.0](https://developers.ripple.com/blog/2016/rippled-0.32.0.html) by Tuesday, 2016-07-19, then your server will not be able to synchronize with the rest of the upgraded network.
|
||||
If you operate a `rippled` server on a version below 0.31.0 but do not upgrade to [version 0.32.0](/blog/2016/rippled-0.32.0.md) by Tuesday, 2016-07-19, then your server will not be able to synchronize with the rest of the upgraded network.
|
||||
|
||||
## Learn More ##
|
||||
|
||||
For more information, please see the documentation in the Ripple Developer Portal:
|
||||
|
||||
* [Upgrading `rippled`](https://ripple.com/build/rippled-setup/#updating-rippled)
|
||||
* [Authorized Accounts](https://ripple.com/build/gateway-guide/#authorized-accounts)
|
||||
* [TrustSetAuth Amendment](https://ripple.com/build/amendments/#trustsetauth)
|
||||
* [Upgrading `rippled`](/docs/infrastructure/installation/update-rippled-automatically-on-linux)
|
||||
* [Authorized Trust Lines](/docs/concepts/tokens/fungible-tokens/authorized-trust-lines)
|
||||
* [TrustSetAuth Amendment](/resources/known-amendments.md#trustsetauth)
|
||||
|
||||
To continue receiving updates about the rippled server, please subscribe to the Ripple Server Google Group: <https://groups.google.com/forum/#!forum/ripple-server>
|
||||
|
||||
@@ -12,14 +12,14 @@ markdown:
|
||||
|
||||
This notice is for all validator operators, and may be relevant to gateways that utilize the Authorized Account feature.
|
||||
|
||||
The new [TrustSetAuth amendment](https://ripple.com/build/amendments/#trustsetauth) is open for voting now. This amendment allows pre-authorization of accounting relationships (zero-balance trust lines) when using [Authorized Accounts](https://ripple.com/build/gateway-guide/#authorized-accounts). With this amendment enabled, currency issuers can authorize other addresses to hold their issued currencies without waiting for the other addresses to take action. Without the amendment, currency holders must first create the accounting relationship with the issuer by setting a limit with a [TrustSet transaction](https://ripple.com/build/transactions/#trustset).
|
||||
The new **TrustSetAuth** amendment is open for voting now. This amendment allows pre-authorization of accounting relationships (zero-balance trust lines) when using _Authorized Trust Lines_. With this amendment enabled, currency issuers can authorize other addresses to hold their issued currencies without waiting for the other addresses to take action. Without the amendment, currency holders must first create the accounting relationship with the issuer by setting a limit with a [TrustSet transaction](/docs/references/protocol/transactions/types/trustset).
|
||||
|
||||
Ripple's validators will vote in favor of the TrustSetAuth amendment, and we expect the new feature to become active by 2016-07-19.
|
||||
|
||||
For more information, see the following articles in the Ripple Developer Center:
|
||||
For more information, see the following articles:
|
||||
|
||||
* Authorized Accounts: <https://ripple.com/build/gateway-guide/#authorized-accounts>
|
||||
* Amendments: <https://ripple.com/build/amendments/>
|
||||
* [Authorized Trust Lines](/docs/concepts/tokens/fungible-tokens/authorized-trust-lines)
|
||||
* [TrustSetAuth Amendment](/resources/known-amendments.md#trustsetauth)
|
||||
|
||||
To continue receiving updates about the rippled server, please subscribe to the Ripple Server Google Group:
|
||||
|
||||
|
||||
@@ -20,14 +20,14 @@ The Ripple Data team will be running load balancing tests on Ripple Data API sta
|
||||
|
||||
If you operate software or services that rely on the Ripple Data API, then you may experience a brief outage and / or inconsistent data, including transaction history and processed analytical data, for a period of approximately 15 mins.
|
||||
|
||||
For more information regarding the Ripple Data API, please see [Ripple Data API Documentation](https://ripple.com/build/data-api-v2/).
|
||||
For more information regarding the Ripple Data API, please see **Ripple Data API Documentation**.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: support@ripple.com
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -10,7 +10,7 @@ markdown:
|
||||
---
|
||||
# Escrow, PayChan, and fix1368 Will Be Available in 3 Days
|
||||
|
||||
A majority of `rippled` validators voted to enable the [Escrow](https://ripple.com/build/amendments/#escrow), [PayChan](https://ripple.com/build/amendments/#paychan), and [fix1368](https://ripple.com/build/amendments/#fix1368) Amendments, which are scheduled to become enabled on the network on Thursday, 2017-03-30.
|
||||
A majority of `rippled` validators voted to enable the [Escrow](/resources/known-amendments.md#escrow), [PayChan](/resources/known-amendments.md#paychan), and [fix1368](/resources/known-amendments.md#fix1368) Amendments, which are scheduled to become enabled on the network on Thursday, 2017-03-30.
|
||||
|
||||
* **Escrow** (previously called SusPay), designed for low volume, high value transactions, permits users to cryptographically escrow XRP on RCL with an expiration date using a [hashlock crypto-condition](https://interledgerjs.github.io/five-bells-condition/jsdoc/).
|
||||
|
||||
@@ -25,7 +25,7 @@ A majority of `rippled` validators voted to enable the [Escrow](https://ripple.c
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
If you operate a `rippled` server but don’t upgrade to version 0.60.0 by Thursday, 2017-03-30, when **Escrow, PayChan & fix1368** are expected to be activated via Amendment, then your server will become [amendment blocked](https://ripple.com/build/amendments/#amendment-blocked), meaning that your server:
|
||||
If you operate a `rippled` server but don’t upgrade to version 0.60.0 by Thursday, 2017-03-30, when **Escrow, PayChan & fix1368** are expected to be activated via Amendment, then your server will become [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that your server:
|
||||
|
||||
* Cannot determine the validity of a ledger
|
||||
* Cannot submit or process transactions
|
||||
@@ -35,14 +35,14 @@ If you operate a `rippled` server but don’t upgrade to version 0.60.0 by Thurs
|
||||
|
||||
If the **Escrow, PayChan & fix1368** amendments do not get approved, then your server will not become amendment blocked and should continue to operate.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -17,7 +17,7 @@ But we are also keenly aware of the need for value to also move securely and rel
|
||||
|
||||
With the release of rippled 0.70.0, and as part of our long-standing and enduring commitment to a reliable and error-free XRP Ledger, we are going further than before. We are adding code that runs automatically and in real time after each transaction completes, and examines the changes it made for correctness before the results are committed to the ledger.
|
||||
|
||||
This is the idea behind the [recently activated](https://xrpcharts.ripple.com/#/transactions/17593B03F7D3283966F3C0ACAF4984F26E9D884C9A202097DAED0523908E76C6) [EnforceInvariants amendment](https://ripple.com/build/amendments/#enforceinvariants), which will make it possible to verify that key properties of the system are not violated. The new checks—which we believe will never trigger—help protect the integrity of the XRP Ledger from bugs yet to be discovered, or even created.
|
||||
This is the idea behind the [recently activated](https://xrpcharts.ripple.com/#/transactions/17593B03F7D3283966F3C0ACAF4984F26E9D884C9A202097DAED0523908E76C6) [EnforceInvariants amendment](/resources/known-amendments.md#enforceinvariants), which will make it possible to verify that key properties of the system are not violated. The new checks—which we believe will never trigger—help protect the integrity of the XRP Ledger from bugs yet to be discovered, or even created.
|
||||
|
||||
What’s more, the process is transparent and public: problematic transactions are marked with a **tecINVARIANT_FAILED** result code and are included in the ledger. This broad exposure, coupled with Ripple’s powerful ability to step through the execution of past transactions, makes it possible to quickly identify and fix any logic flaws in the code.
|
||||
|
||||
|
||||
@@ -14,11 +14,11 @@ markdown:
|
||||
|
||||
Today, for the first time, Ripple is proud to publicly announce that in recent internal benchmark testing, across 16 geographically distributed validators, the RCL is able to sustain nearly 1000 transactions per second.
|
||||
|
||||
For even higher throughput transactions, we recently introduced [XRP payment channels](https://developers.ripple.com/blog/2016/rippled-0.33.0.html), which allow for zero-latency XRP payments. Although payment channels achieve practically infinite scalability by decoupling payment from settlement, they do so without incurring the risk typically associated with delayed settlement.
|
||||
For even higher throughput transactions, we recently introduced [XRP payment channels](/blog/2016/rippled-0.33.0.md), which allow for zero-latency XRP payments. Although payment channels achieve practically infinite scalability by decoupling payment from settlement, they do so without incurring the risk typically associated with delayed settlement.
|
||||
|
||||
Throughout 2016, the network received upgrades that seamlessly enabled new functionality and significantly improved performance. Fast ledger close times have been the hallmark of RCL since its inception and those were further improved last year. Ledgers now close, on average, every 3.5 seconds - a full 20% faster than they did a year ago.
|
||||
|
||||
The new [fee escalation code ](https://ripple.com/build/transaction-cost/)was introduced to constantly monitor network load and adjust (in near real-time) the cost of executing transactions, which makes it more difficult to overload the network and further helps to ensure the long-term health and stability of RCL.
|
||||
The new fee escalation code was introduced to constantly monitor network load and adjust (in near real-time) the cost of executing transactions, which makes it more difficult to overload the network and further helps to ensure the long-term health and stability of RCL.
|
||||
|
||||
Stability, however, goes beyond improving performance and adding new features. At Ripple we place heavy emphasis on writing code that is secure, solid and robust. This singular focus on code quality has helped the Ripple network achieve availability and reliability well beyond industry standards with no outages.
|
||||
|
||||
|
||||
@@ -20,22 +20,23 @@ The `rippled` team has released version 0.40.1, which increases SQLite database
|
||||
|
||||
If you operate a `rippled` server and have full-history of the ledger, but don’t upgrade to version 0.40.1, then your server may crash when restarted.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The md5sum for the rpm is: e876816f4ddb38bec28d158083020fa9
|
||||
|
||||
The md5sum for the source rpm is: 3ed1569bd0dbba5ff1d1ef1abfca7ed7
|
||||
|
||||
For other platforms, please [compile version 0.40.1 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.40.1 from source](https://github.com/XRPLF/rippled/tree/0.40.1/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
$ git log -1 upstream/master
|
||||
```text
|
||||
commit e91aacc9a3d2f332a93981270c3812e26189226e
|
||||
Author: Nik Bougalis <nikb@bougalis.net>
|
||||
Date: Thu Jan 5 09:38:28 2017 -0800
|
||||
|
||||
Set version to 0.40.1
|
||||
```
|
||||
|
||||
## Bug Fixes
|
||||
Increase SQLite database limits to prevent full-history servers from crashing when restarting. [(#1961)](https://github.com/ripple/rippled/commit/610e51a162a6ef06accf8733b3b35b492963a78b)
|
||||
@@ -44,11 +45,11 @@ Increase SQLite database limits to prevent full-history servers from crashing wh
|
||||
The Ripple operations team has deployed version 0.40.1 to all full-history `rippled` servers under its operational control.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -14,7 +14,7 @@ Ripple has released `rippled` version 0.50.0, which introduces several enhanceme
|
||||
|
||||
Highlights of this release include:
|
||||
|
||||
* **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 named “TickSize”](https://ripple.com/build/amendments/#ticksize) on Tuesday, 2017-02-21. See below for details.
|
||||
* **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 named “TickSize”](/resources/known-amendments.md#ticksize) on Tuesday, 2017-02-21. See below for details.
|
||||
|
||||
## Action Required
|
||||
|
||||
@@ -38,40 +38,42 @@ If you operate a `rippled` server but don’t upgrade to version 0.50.0 by Tuesd
|
||||
|
||||
If the **TickSize** amendment is vetoed or does not pass, then your server will not become amendment blocked and should continue to operate.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The md5sum for the rpm is: 82eb29f7e464e44eb24e3c891a021041
|
||||
|
||||
The md5sum for the source rpm is: 7bf25c86f018daf82c5d5f8ab621153a
|
||||
|
||||
For other platforms, please [compile version 0.50.0 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.50.0 from source](https://github.com/XRPLF/rippled/tree/0.50.0/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 77999579b535373872d8cce7ddc8b12cdcc39d84
|
||||
Author: Nik Bougalis <nikb@bougalis.net>
|
||||
Date: Thu Jan 26 13:26:03 2017 -0800
|
||||
|
||||
Set version to 0.50.0
|
||||
```
|
||||
|
||||
## Network Update
|
||||
The Ripple operations team plans to deploy version 0.50.0 to all `rippled` servers under its operational control, including private clusters, starting at 11:00 AM PDT on Friday, 2017-01-27. The deployment is expected to complete within 4 hours. The network should continue to operate during deployment and no outage is expected.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: support@ripple.com
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
## Full Release Notes
|
||||
|
||||
The `rippled` 0.50.0 release includes **TickSize**, which allows gateways to set a "tick size" for assets they issue to to help promote faster price discovery and deeper liquidity, as well as reduce transaction spam and ledger churn on RCL. Ripple expects TickSize to be enabled via an Amendment called **TickSize** on Tuesday, 2017-02-21. This feature underlines Ripple’s continued support to improving RCL and making it even better suited for settlement of global payments.
|
||||
|
||||
You can [update to the new version](https://ripple.com/build/rippled-setup/#updating-rippled) on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please [compile the new version from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
You can [update to the new version](/docs/infrastructure/installation/update-rippled-automatically-on-linux) on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please [compile the new version from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md).
|
||||
|
||||
**New and Updated Features**
|
||||
|
||||
@@ -141,8 +143,8 @@ Server administrators who wish to have different settings can configure custom g
|
||||
|
||||
## Upcoming Features
|
||||
|
||||
We expect the [previously](https://developers.ripple.com/blog/2016/rippled-0.40.0.html) announced Suspended Payments feature, which introduces new transaction types to the Ripple protocol that will permit users to cryptographically escrow XRP on RCL, to be enabled via the [“SusPay”](https://ripple.com/build/amendments/#suspay) Amendment on Tuesday, 2017-02-21.
|
||||
We expect the [previously](/blog/2016/rippled-0.40.0.md) announced Suspended Payments feature, which introduces new transaction types to the Ripple protocol that will permit users to cryptographically escrow XRP on RCL, to be enabled via the [“SusPay”](/resources/known-amendments.md#suspay) Amendment on Tuesday, 2017-02-21.
|
||||
|
||||
Also, we expect support for [crypto-conditions](https://tools.ietf.org/html/draft-thomas-crypto-conditions-02), which are signature-like structures that can be used with suspended payments to support ILP integration, to be included in the next `rippled` release scheduled for March.
|
||||
|
||||
Lastly, we do not have an update on the [previously announced](https://developers.ripple.com/blog/2016/rippled-0.33.0.html) changes to the hash tree structure that `rippled` uses to represent a ledger, called [SHAMapV2](https://ripple.com/build/amendments/#shamapv2). At the time of activation, this amendment will require brief scheduled allowable unavailability while the changes to the hash tree structure are computed by the network. We will keep the community updated as we progress towards this date (TBA).
|
||||
Lastly, we do not have an update on the [previously announced](/blog/2016/rippled-0.33.0.md) changes to the hash tree structure that `rippled` uses to represent a ledger, called [SHAMapV2](/resources/known-amendments.md#shamapv2). At the time of activation, this amendment will require brief scheduled allowable unavailability while the changes to the hash tree structure are computed by the network. We will keep the community updated as we progress towards this date (TBA).
|
||||
|
||||
@@ -21,13 +21,13 @@ The `rippled` team has released 0.50.2, which adjusts the default TLS cipher lis
|
||||
|
||||
If you operate a `rippled` server and accept secure client connections, but don’t upgrade to version 0.50.2, then your server may be unable to negotiate SSL connections.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The md5sum for the rpm is: 05cf675685158aabfc3ff6af7b1549d8
|
||||
|
||||
The md5sum for the source rpm is: 0a8c93d67e1c27726ee57693177e7745
|
||||
|
||||
For other platforms, please [compile version 0.50.2 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.50.2 from source](https://github.com/XRPLF/rippled/tree/0.50.2/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
@@ -48,11 +48,11 @@ Adjust the default cipher list and correct a flaw that would not allow an SSL ha
|
||||
The Ripple operations team has deployed a configuration-based fix to all client-facing `rippled` servers under its operational control and will not be updating to 0.50.2 at this time.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: support@ripple.com
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -34,21 +34,23 @@ If you operate a `rippled` server, but don’t upgrade to `rippled` version 0.50
|
||||
|
||||
If you operate a `rippled` validating server, but don’t upgrade to `rippled` version 0.50.3, which includes a patch for the reported exploit, then your server will validate some transactions in a payment path that bypass the blocking effect of the `NoRipple` flag.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The sha256 for the rpm is: 2ee3e7e2912b5df9e3f8f88c5f6adfa60afbb37ef08afe50f6147795c5c2abaf
|
||||
|
||||
The sha256 for the source rpm is: ada6f9ae8b8136569d28f03a43fef0f828e2c69857c81f230d17cf9f832cce0f
|
||||
|
||||
For other platforms, please [compile version 0.50.3 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.50.3 from source](https://github.com/XRPLF/rippled/tree/0.50.3/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 82de944b30afef7fb6220424b62a79156e93b321
|
||||
Author: Nik Bougalis <nikb@bougalis.net>
|
||||
Date: Mon Mar 13 15:49:21 2017 -0700
|
||||
|
||||
Set version to 0.50.3
|
||||
```
|
||||
|
||||
## Bug Fixes
|
||||
|
||||
@@ -59,11 +61,11 @@ Patch a reported exploit that would allow a combination of trust lines and order
|
||||
Ripple engineers have deployed the fix to all `rippled` validating servers under Ripple’s operational control and will not be updating client-facing `rippled` servers to 0.50.3 at this time. _(Editor's note: an earlier version of this post incorrectly stated that the fix was configuration-based. The fix was to update Ripple's validating servers to 0.50.3.)_
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -18,7 +18,7 @@ Highlights of this release include:
|
||||
|
||||
* **[Dynamic UNL Lite](https://github.com/ripple/rippled/pull/1842)**, which allows `rippled` to automatically adjust which validators it trusts based on recommended lists from trusted publishers.
|
||||
|
||||
Ripple expects Escrow, the [previously announced **Payment Channels**](https://developers.ripple.com/blog/2016/rippled-0.33.0.html), and the new [**fix1368** amendment](#fix1368-amendment) to be enabled via Amendments called [Escrow](https://ripple.com/build/amendments/#escrow), [PayChan](https://ripple.com/build/amendments/#paychan), and `fix1368`, respectively, on Thursday, 2017-03-30.
|
||||
Ripple expects Escrow, the [previously announced **Payment Channels**](/blog/2016/rippled-0.33.0.md), and the new [**fix1368** amendment](#fix1368-amendment) to be enabled via Amendments called [Escrow](/resources/known-amendments.md#escrow), [PayChan](/resources/known-amendments.md#paychan), and `fix1368`, respectively, on Thursday, 2017-03-30.
|
||||
|
||||
|
||||
## Action Required
|
||||
@@ -27,7 +27,7 @@ Ripple expects Escrow, the [previously announced **Payment Channels**](https://d
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
If you operate a `rippled` server but don’t upgrade to version 0.60.0 by Thursday, 2017-03-30, when Escrow and PayChan are expected to be activated via Amendment, then your server will become [amendment blocked](https://ripple.com/build/amendments/#amendment-blocked), meaning that your server:
|
||||
If you operate a `rippled` server but don’t upgrade to version 0.60.0 by Thursday, 2017-03-30, when Escrow and PayChan are expected to be activated via Amendment, then your server will become [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that your server:
|
||||
|
||||
* Cannot determine the validity of a ledger
|
||||
* Cannot submit or process transactions
|
||||
@@ -37,34 +37,36 @@ If you operate a `rippled` server but don’t upgrade to version 0.60.0 by Thurs
|
||||
|
||||
If the **Escrow** and **PayChan** amendments do not get approved, then your server will not become amendment blocked and should continue to operate.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The sha256 for the rpm is: 4d2acb2a40e2d18ba1737098efdca54caa823a403ce9562c83e2dd2c9e959588
|
||||
|
||||
The sha256 for the source rpm is: 3437a0202e762801869f31bf798417ebdb3717e16c4381dc0e9b02fe75d23024
|
||||
|
||||
For other platforms, please [compile version 0.60.0 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.60.0 from source](https://github.com/XRPLF/rippled/tree/0.60.0/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 0df1b09a731ba0feaa5d60046e1c7dd415f5f7ed
|
||||
Author: Nik Bougalis <nikb@bougalis.net>
|
||||
Date: Thu Mar 16 13:33:29 2017 -0700
|
||||
|
||||
Set version to 0.60.0
|
||||
```
|
||||
|
||||
## Network Update
|
||||
The Ripple operations team plans to deploy version 0.60.0 to all `rippled` servers under its operational control, including private clusters, starting at 7:00 PM PST on Thursday, 2017-03-16. The deployment is expected to complete within 4 hours. The network should continue to operate during deployment and no outage is expected.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
## Full Release Notes
|
||||
|
||||
@@ -74,11 +76,11 @@ The rippled version 0.60.0 release includes Escrow, (previously called SusPay),
|
||||
|
||||
### Payment Channels
|
||||
|
||||
The amendment for Payment Channels was originally introduced in version 0.33.0, but is now ready for Payment Channels to be enabled on the production Ripple Consensus Ledger. XRP [Payment Channels](https://ripple.com/build/amendments/#paychan) are intended for high volume, low value payments. They provide a method for scalable, intermittent, off-ledger settlement flowing in a single direction. For bidirectional payment channels, an XRP Payment Channel can be used in each direction. The recipient can claim any unpaid balance at any time before the channel closes. The owner can top off the channel as needed and must wait out a delay to close the channel to give the recipient a chance to supply any claims. The total amount paid increases monotonically as newer claims are issued.
|
||||
The amendment for Payment Channels was originally introduced in version 0.33.0, but is now ready for Payment Channels to be enabled on the production Ripple Consensus Ledger. XRP [Payment Channels](/resources/known-amendments.md#paychan) are intended for high volume, low value payments. They provide a method for scalable, intermittent, off-ledger settlement flowing in a single direction. For bidirectional payment channels, an XRP Payment Channel can be used in each direction. The recipient can claim any unpaid balance at any time before the channel closes. The owner can top off the channel as needed and must wait out a delay to close the channel to give the recipient a chance to supply any claims. The total amount paid increases monotonically as newer claims are issued.
|
||||
|
||||
### Dynamic UNL Lite
|
||||
|
||||
At the core of RCL is the [consensus process](https://ripple.com/build/ripple-ledger-consensus-process/). Through the consensus process, validating nodes agree on a specific subset of the candidate transactions to be considered for the next ledger. Consensus is an iterative process in which nodes relay proposals, or sets of candidate transactions. Nodes communicate and update proposals until a supermajority of peers agree on the same set of candidate transactions.
|
||||
At the core of RCL is the [consensus process](/docs/concepts/consensus-protocol). Through the consensus process, validating nodes agree on a specific subset of the candidate transactions to be considered for the next ledger. Consensus is an iterative process in which nodes relay proposals, or sets of candidate transactions. Nodes communicate and update proposals until a supermajority of peers agree on the same set of candidate transactions.
|
||||
|
||||
During consensus, each node evaluates proposals from a specific set of peers, called chosen validators. Chosen validators represent a subset of the network which, when taken collectively, is “trusted” not to collude in an attempt to defraud the node evaluating the proposals. This definition of “trust” does not require that each individual chosen validator is trusted. Rather, validators are chosen based on the expectation they will not collude in a coordinated effort to falsify data relayed to the network.
|
||||
|
||||
@@ -94,9 +96,9 @@ These features underline Ripple’s continued support to improving RCL by making
|
||||
|
||||
## Upcoming Features
|
||||
|
||||
We do not have an update on the [previously announced](https://developers.ripple.com/blog/2016/rippled-0.33.0.html) changes to the hash tree structure that `rippled` uses to represent a ledger, called [SHAMapV2](https://ripple.com/build/amendments/#shamapv2). At the time of activation, this amendment will require brief scheduled allowable unavailability while the changes to the hash tree structure are computed by the network. We will keep the community updated as we progress towards this date (TBA).
|
||||
We do not have an update on the [previously announced](/blog/2016/rippled-0.33.0.md) changes to the hash tree structure that `rippled` uses to represent a ledger, called [SHAMapV2](/resources/known-amendments.md#shamapv2). At the time of activation, this amendment will require brief scheduled allowable unavailability while the changes to the hash tree structure are computed by the network. We will keep the community updated as we progress towards this date (TBA).
|
||||
|
||||
You can [update to the new version](https://ripple.com/build/rippled-setup/#updating-rippled) on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please [compile the new version from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
You can [update to the new version](/docs/infrastructure/installation/update-rippled-automatically-on-linux) on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please [compile the new version from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md).
|
||||
|
||||
|
||||
## 0.60.0 Change Log
|
||||
|
||||
@@ -12,7 +12,7 @@ markdown:
|
||||
|
||||
The `rippled` team has released `rippled` version 0.60.1, which corrects a technical flaw that resulted from using 32-bit space identifiers instead of the protocol-defined 16-bit values for Escrow and Payment Channel ledger entries. `rippled` version 0.60.1 also fixes a problem where the websocket timeout timer would not be cancelled when certain errors occurred during subscription streams. **Ripple strongly recommends upgrading to `rippled` version 0.60.1 immediately.**
|
||||
|
||||
Ripple expects the [`Escrow`](https://ripple.com/build/amendments/#escrow) and [`PayChan`](https://ripple.com/build/amendments/#paychan) amendments to be enabled via [amendment vote](https://developers.ripple.com/blog/2017/escrow-paychan-fix1368-reminder.html) around 11:26 PM PDT on Thursday, 2017-03-30. There are no new features in the 0.60.1 release.
|
||||
Ripple expects the [`Escrow`](/resources/known-amendments.md#escrow) and [`PayChan`](/resources/known-amendments.md#paychan) amendments to be enabled via [amendment vote](/blog/2017/escrow-paychan-fix1368-reminder.md) around 11:26 PM PDT on Thursday, 2017-03-30. There are no new features in the 0.60.1 release.
|
||||
|
||||
## Action Required
|
||||
|
||||
@@ -24,21 +24,23 @@ Ripple expects the [`Escrow`](https://ripple.com/build/amendments/#escrow) and [
|
||||
|
||||
* If you operate a `rippled` server, but do not upgrade to version 0.60.1, then client websocket connections to your `rippled` server may continue to disconnect during subscription streams.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The sha256 for the RPM is: 6714050e9d1d232e8250be434fe6a61c44f78e41adc3c2b5f49df490ee5312ef
|
||||
|
||||
The sha256 for the source RPM is: 5bba13e93fed160a3405315e4128e891b2bc1e439ee5f7b429294003c618f0e1
|
||||
|
||||
For other platforms, please [compile version 0.60.1 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.60.1 from source](https://github.com/XRPLF/rippled/tree/0.60.1/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 0d4fe469c6b0ba47645b53930e74248ff789fe75
|
||||
Author: seelabs <scott.determan@yahoo.com>
|
||||
Date: Wed Mar 29 15:41:43 2017 -0400
|
||||
|
||||
Set version to 0.60.1
|
||||
```
|
||||
|
||||
## Bug Fixes
|
||||
|
||||
@@ -51,11 +53,11 @@ Fix a problem where the WebSocket timeout timer would not be cancelled when cert
|
||||
The Ripple technical operations team plans to deploy `rippled` version 0.60.1 to all `rippled` servers under its operational control, including private clusters, starting at 11:00 AM PDT on Thursday, 2017-03-30. The deployment is expected to complete within 4 hours. The network should continue to operate during deployment and no outage is expected.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: support@ripple.com
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -24,29 +24,31 @@ There are no changes to `rippled` with this version.
|
||||
|
||||
**If you operate a `rippled` validator server that was set up using validator-keys but don’t update to the `rippled` 0.60.2-2 RPM**, then you will be unable to sign data using your validator key.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The sha256 for the RPM is: 74e2541c1c6c06bd34d102229890bb11811701d73d99e4cfb4882d430131c067
|
||||
|
||||
The sha256 for the source RPM is: aab7f247b5cf9d3a20d4720aef2c51532bb83ee91fafe584e4fdfac77171537b
|
||||
|
||||
For other platforms, please [compile version 0.60.2-2 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.60.2 from source](https://github.com/XRPLF/rippled/tree/0.60.2/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 7cd4d7889779e6418270c8af89386194efbef24b
|
||||
Author: seelabs <scott.determan@yahoo.com>
|
||||
Date: Thu Mar 30 14:25:41 2017 -0400
|
||||
|
||||
Set version to 0.60.2
|
||||
```
|
||||
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: support@ripple.com
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -10,7 +10,7 @@ markdown:
|
||||
---
|
||||
# rippled version 0.60.2
|
||||
|
||||
The `rippled` team has released `rippled` version 0.60.2, which further strengthens handling of cases associated with a [previously patched exploit](https://developers.ripple.com/blog/2017/rippled-0.50.3.html), in which `NoRipple` flags were being bypassed by using offers. Ripple requires upgrading to `rippled` version 0.60.2 immediately. There are no new features in the 0.60.2 release. **Note**: This does not affect XRP transactions.
|
||||
The `rippled` team has released `rippled` version 0.60.2, which further strengthens handling of cases associated with a [previously patched exploit](/blog/2017/rippled-0.50.3.md), in which `NoRipple` flags were being bypassed by using offers. Ripple requires upgrading to `rippled` version 0.60.2 immediately. There are no new features in the 0.60.2 release. **Note**: This does not affect XRP transactions.
|
||||
|
||||
Ripple will be following up with a postmortem, explaining the previosuly patched exploit, the timeline of events and the actions taken in more detail at a later date.
|
||||
|
||||
@@ -20,7 +20,7 @@ Ripple will be following up with a postmortem, explaining the previosuly patched
|
||||
|
||||
**If you are an individual user**, then you should have the `NoRipple` flag enabled by default and set the trust line limit to zero on gateways that you do not trust.
|
||||
|
||||
**If you are an individual user**, and you do not have the `NoRipple` flag enabled, and you discover a negative balance owed to an unknown account, then you should [freeze](https://ripple.com/build/freeze/#individual-freeze) that individual trust line.
|
||||
**If you are an individual user**, and you do not have the `NoRipple` flag enabled, and you discover a negative balance owed to an unknown account, then you should [freeze](/docs/concepts/tokens/fungible-tokens/freezes#individual-freeze) that individual trust line.
|
||||
|
||||
|
||||
## Impact of Not Upgrading
|
||||
@@ -29,21 +29,23 @@ Ripple will be following up with a postmortem, explaining the previosuly patched
|
||||
|
||||
**If you operate a rippled validating server**, but do not upgrade to `rippled` version 0.60.2, which prevents `NoRipple` flags from being bypassed by using offers, then your server will validate some transactions in a payment path that bypass the blocking effect of the `NoRipple` flag using offers.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The sha256 for the RPM is: 3dc7412bda8986188164f0ff70ff80c351b17521e6943a876d5d3268fa07289d
|
||||
|
||||
The sha256 for the source RPM is: f189ba1a8ae2201da47008ff50d027dcf719c7001c9b350b6759db279cbb48c8
|
||||
|
||||
For other platforms, please [compile version 0.60.2 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.60.2 from source](https://github.com/XRPLF/rippled/tree/0.60.2/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 7cd4d7889779e6418270c8af89386194efbef24b
|
||||
Author: seelabs <scott.determan@yahoo.com>
|
||||
Date: Thu Mar 30 14:25:41 2017 -0400
|
||||
|
||||
Set version to 0.60.2
|
||||
```
|
||||
|
||||
|
||||
## Bug Fixes
|
||||
@@ -56,11 +58,11 @@ The Ripple technical operations team plans to deploy `rippled` version 0.60.2 to
|
||||
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: support@ripple.com
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -20,21 +20,23 @@ The `rippled` team has released `rippled` version 0.60.3, which helps to increas
|
||||
|
||||
**If you operate a rippled server**, but don’t upgrade to `rippled` version 0.60.3, then your server may experience dropped connections to other servers more frequently.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The sha256 for the RPM is: 3e9c8b421ea0ae6da7ae65524be60408f32ef2bd0bcfea1e1c9fb54eec5fc809
|
||||
|
||||
The sha256 for the source RPM is: 9848185e35a21ef41fcea334f8ad224c49e243f64b38dd9311ab898b97ab6c0a
|
||||
|
||||
For other platforms, please [compile version 0.60.3 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.60.3 from source](https://github.com/XRPLF/rippled/tree/0.60.3/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 208028a1420cc187a6b5b9e97846e8cafd54f39f
|
||||
Author: Nik Bougalis <nikb@bougalis.net>
|
||||
Date: Tue May 9 13:37:49 2017 -0700
|
||||
|
||||
Set version to 0.60.3
|
||||
```
|
||||
|
||||
## Change Log
|
||||
|
||||
@@ -46,11 +48,11 @@ The Ripple technical operations team plans to deploy `rippled` version 0.60.3 to
|
||||
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: support@ripple.com
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -14,11 +14,11 @@ Ripple has released `rippled` version 0.70.0, which introduces several enhanceme
|
||||
|
||||
Highlights of this release include:
|
||||
|
||||
* The [**FlowCross** Amendment](https://ripple.com/build/amendments/#flowcross), which streamlines offer crossing and autobrigding logic by leveraging the new “Flow” payment engine in `rippled`.
|
||||
* The [**FlowCross** Amendment](/resources/known-amendments.md#flowcross), which streamlines offer crossing and autobrigding logic by leveraging the new “Flow” payment engine in `rippled`.
|
||||
|
||||
* The [**EnforceInvariants** Amendment](https://ripple.com/build/amendments/#enforceinvariants), which safeguards the integrity of RCL by introducing code that executes after every transaction and ensures that the execution did not violate key protocol rules.
|
||||
* The [**EnforceInvariants** Amendment](/resources/known-amendments.md#enforceinvariants), which safeguards the integrity of RCL by introducing code that executes after every transaction and ensures that the execution did not violate key protocol rules.
|
||||
|
||||
* [**fix1373**](https://ripple.com/build/amendments/#fix1373), which addresses an issue that would cause payments with certain path specifications to not be properly parsed.
|
||||
* [**fix1373**](/resources/known-amendments.md#fix1373), which addresses an issue that would cause payments with certain path specifications to not be properly parsed.
|
||||
|
||||
Ripple expects the **EnforceInvariants** and **fix1373** Amendments to be enabled on Thursday, 2017-06-29. The **FlowCross** Amendment will be enabled on a future date (TBA).
|
||||
|
||||
@@ -32,7 +32,7 @@ The algorithm that determines how many threads `rippled` uses has been changed w
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
If you operate a `rippled` server but do not upgrade to version 0.70.0 by Thursday, 2017-06-29, when **EnforceInvariants** and **fix1373** are expected to be activated via Amendment, then your server will become [amendment blocked](https://ripple.com/build/amendments/#amendment-blocked), meaning that your server:
|
||||
If you operate a `rippled` server but do not upgrade to version 0.70.0 by Thursday, 2017-06-29, when **EnforceInvariants** and **fix1373** are expected to be activated via Amendment, then your server will become [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that your server:
|
||||
|
||||
* Cannot determine the validity of a ledger
|
||||
* Cannot submit or process transactions
|
||||
@@ -42,21 +42,23 @@ If you operate a `rippled` server but do not upgrade to version 0.70.0 by Thursd
|
||||
|
||||
If the **EnforceInvariants** and **fix1373** Amendments do not get approved, then your server will not become amendment blocked and should continue to operate.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The sha256 for the rpm is: 5a617bce531f39c044de535b6bda2a59371829dfc1079b67876b68c9a9748834
|
||||
|
||||
The sha256 for the source rpm is: c51212ae374f69ddc10f967409a750834f06195cb384b2af04e4fa0c3fb81a24
|
||||
|
||||
For other platforms, please [compile version 0.70.0 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.70.0 from source](https://github.com/XRPLF/rippled/tree/0.70.0/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 7b0d48281049c3fec7fafcb7ce5cea045367ae1f
|
||||
Author: Nik Bougalis <nikb@bougalis.net>
|
||||
Date: Thu Jun 15 07:34:17 2017 -0700
|
||||
|
||||
Set version to 0.70.0
|
||||
```
|
||||
|
||||
## Network Update
|
||||
The Ripple operations team plans to deploy version 0.70.0 to all `rippled` servers under its operational control, including private clusters, starting at 2:00 PM PST on Thursday, 2017-06-15. The deployment is expected to complete within 4 hours. The network should continue to operate during deployment and no outage is expected.
|
||||
@@ -64,36 +66,36 @@ The Ripple operations team plans to deploy version 0.70.0 to all `rippled` serve
|
||||
At that time, `rippled` validators under Ripple’s operational control will begin voting for the **EnforceInvariants** and **fix1737** Amendments.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
## Full Release Notes
|
||||
|
||||
### FlowCross
|
||||
|
||||
Currently, the offer crossing code in `rippled` is independent of the payment flow code in `rippled`. The introduction of the **FlowCross** Amendment ensures that the same logic that drives payments also drives offer crossing. This change streamlines the code base, improves test coverage and is expected to result in some marginal performance benefits in offer crossing. For more information, see [FlowCross](https://ripple.com/build/amendments/#flowcross).
|
||||
Currently, the offer crossing code in `rippled` is independent of the payment flow code in `rippled`. The introduction of the **FlowCross** Amendment ensures that the same logic that drives payments also drives offer crossing. This change streamlines the code base, improves test coverage and is expected to result in some marginal performance benefits in offer crossing. For more information, see [FlowCross](/resources/known-amendments.md#flowcross).
|
||||
|
||||
### EnforceInvariants
|
||||
|
||||
The introduction of the **EnforceInvariants** Amendment supplements existing safeguards of RCL integrity. Once the amendment activates, the servers will execute specialized code to check key system invariants after the execution of each transaction. If a transaction fails any of the checks, it will be considered as invalid. For more information, see [EnforceInvariants](https://ripple.com/build/amendments/#enforceinvariants).
|
||||
The introduction of the **EnforceInvariants** Amendment supplements existing safeguards of RCL integrity. Once the amendment activates, the servers will execute specialized code to check key system invariants after the execution of each transaction. If a transaction fails any of the checks, it will be considered as invalid. For more information, see [EnforceInvariants](/resources/known-amendments.md#enforceinvariants).
|
||||
|
||||
### fix1373 Amendment
|
||||
|
||||
Version 0.70.0 also introduces the fix1373 Amendment to fix a minor bug in pathfinding that causes strand creation to fail. Specifically, the issue was related to paths that contain path elements where all the path elements types are set (account, currency and issuer). The fix1373 Amendment corrects the issue that caused some strand creation to fail. For more information, see [fix1373](https://ripple.com/build/amendments/#fix1373).
|
||||
Version 0.70.0 also introduces the fix1373 Amendment to fix a minor bug in pathfinding that causes strand creation to fail. Specifically, the issue was related to paths that contain path elements where all the path elements types are set (account, currency and issuer). The fix1373 Amendment corrects the issue that caused some strand creation to fail. For more information, see [fix1373](/resources/known-amendments.md#fix1373).
|
||||
|
||||
These features underline Ripple’s continued support to improving RCL by making it more stable, secure and efficient for settlement of global payments.
|
||||
|
||||
## Upcoming Features
|
||||
|
||||
We do not have an update on the [previously announced](https://developers.ripple.com/blog/2016/rippled-0.33.0.html) changes to the hash tree structure that `rippled` uses to represent a ledger, called [SHAMapV2](https://ripple.com/build/amendments/#shamapv2). At the time of activation, this amendment will require brief scheduled allowable unavailability while the changes to the hash tree structure are computed by the network. We will keep the community updated as we progress towards this date (TBA).
|
||||
We do not have an update on the [previously announced](/blog/2016/rippled-0.33.0.md) changes to the hash tree structure that `rippled` uses to represent a ledger, called [SHAMapV2](/resources/known-amendments.md#shamapv2). At the time of activation, this amendment will require brief scheduled allowable unavailability while the changes to the hash tree structure are computed by the network. We will keep the community updated as we progress towards this date (TBA).
|
||||
|
||||
You can [update to the new version](https://ripple.com/build/rippled-setup/#updating-rippled) on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please [compile the new version from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
You can [update to the new version](/docs/infrastructure/installation/update-rippled-automatically-on-linux) on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please [compile the new version from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md).
|
||||
|
||||
|
||||
## 0.70.0 Change Log
|
||||
|
||||
@@ -26,21 +26,23 @@ This announcement now contains corrected SHA-256 values for the RPM and source R
|
||||
|
||||
* If you operate a `rippled` validator server, but do not upgrade to `rippled` version 0.70.1, then your `rippled` validator server could experience increased loss of synchronization with the network.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The SHA-256 for the `RPM` is: `23c8ec08d1ca8c8ce6c0602617c7e41b7f2fd249a1417a79a286a3faa5be08eb`
|
||||
|
||||
The SHA-256 for the source `RPM` is: `3522546989024e783cfa933218a28ee878dcc3f334749e7456cb04a9cd07d8fc`
|
||||
|
||||
For other platforms, please [compile version 0.70.1 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.70.1 from source](https://github.com/XRPLF/rippled/tree/0.70.1/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 3bfd9de6779994e5bbbba864791429e2f7360947
|
||||
Author: Nik Bougalis <nikb@bougalis.net>
|
||||
Date: Wed Jun 28 07:15:07 2017 -0700
|
||||
|
||||
Set version to 0.70.1
|
||||
```
|
||||
|
||||
## 0.70.1 Change Log
|
||||
|
||||
@@ -58,11 +60,11 @@ The first log entry should be the change setting the version:
|
||||
The Ripple technical operations team deployed `rippled` version 0.70.1 to all `rippled` servers under its operational control, including private clusters, on Sunday, 2017-07-09.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: support@ripple.com
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -22,13 +22,13 @@ There are no new features in the 0.70.2 release.
|
||||
|
||||
If you operate a `rippled` server, but do not upgrade to `rippled` version 0.70.2, then your `rippled` server could see inconsistent transaction relaying as well as transactions getting stuck in the open ledger without being passed on to validators. In this case, your server may report very high transaction costs and brimming transaction queues.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The SHA-256 for the RPM is: b41f3d75bb0fcf67dcd3cd14fbf1a7029ce28442b6dcd19fff7df330c35ee3e7
|
||||
|
||||
The SHA-256 for the source RPM is: 8cae27e639ef57987238c7800127288857c6caa61d15342faf781749ce9ee7ff
|
||||
|
||||
For other platforms, please [compile version 0.70.2 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.70.2 from source](https://github.com/XRPLF/rippled/tree/0.70.2/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
@@ -51,11 +51,11 @@ Date: Tue Sep 19 14:26:06 2017 -0400
|
||||
The Ripple operations team plans to deploy version 0.70.2 to all `rippled` servers under its operational control, including private clusters, starting at 4:00 PM PT on Thursday, 2017-09-21. The deployment is expected to complete within 4 hours. The network should continue to operate during deployment and no outage is expected.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -14,7 +14,7 @@ Ripple has released `rippled` version 0.80.0, which introduces several enhanceme
|
||||
|
||||
Highlights of this release include:
|
||||
|
||||
* The **SortedDirectories** amendment sorts the entries in [`DirectoryNode` ledger objects](https://ripple.com/build/ledger-format/#directorynode). It also corrects a technical flaw that could, in some edge cases, prevent an empty intermediate page from being deleted.
|
||||
* The **SortedDirectories** amendment sorts the entries in [`DirectoryNode` ledger objects](/docs/references/protocol/ledger-data/ledger-entry-types/directorynode). It also corrects a technical flaw that could, in some edge cases, prevent an empty intermediate page from being deleted.
|
||||
|
||||
Ripple expects the **SortedDirectories** amendment to be enabled on Tuesday, 2017-11-07.
|
||||
|
||||
@@ -25,7 +25,7 @@ Ripple expects the **SortedDirectories** amendment to be enabled on Tuesday, 201
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
If you operate a `rippled` server but do not upgrade to version 0.80.0 by Tuesday, 2017-11-07, when the **SortedDirectories** Amendment is expected to be activated, then your server will become [amendment blocked](https://ripple.com/build/amendments/#amendment-blocked), meaning that your server:
|
||||
If you operate a `rippled` server but do not upgrade to version 0.80.0 by Tuesday, 2017-11-07, when the **SortedDirectories** Amendment is expected to be activated, then your server will become [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that your server:
|
||||
|
||||
* Cannot determine the validity of a ledger
|
||||
* Cannot submit or process transactions
|
||||
@@ -39,13 +39,13 @@ If the **SortedDirectories** amendment does not get approved, then your `rippled
|
||||
|
||||
**If you operate a `rippled` server that uses RocksDB as its data store**, then we recommend removing the RocksDB `file_size_mb` parameter from your `rippled.cfg` config file.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The sha256 for the rpm is: 0f67e8fdc9c555921534b6944ca418df007cee0705ab9e2fc5423963848b2935
|
||||
|
||||
The sha256 for the source rpm is: 9c6f5074e1ec3ce6ced27c0da243bb7ed19a32a8bedf2d68809ec37845f42c1b
|
||||
|
||||
For other platforms, please [compile version 0.80.0 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.80.0 from source](https://github.com/XRPLF/rippled/tree/0.80.0/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
@@ -63,14 +63,14 @@ The Ripple operations team plans to deploy version 0.80.0 to all `rippled` serve
|
||||
At that time, `rippled` validators under Ripple’s operational control will begin voting for the **SortedDirectories** amendment.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
## Full Release Notes
|
||||
|
||||
@@ -81,11 +81,11 @@ The **SortedDirectories** amendment addresses two distinct issues: First, it cor
|
||||
|
||||
## Upcoming Features
|
||||
|
||||
The [previously announced](https://developers.ripple.com/blog/2017/rippled-0.70.0.html) FlowCross Amendment will be enabled on a future date (TBA).
|
||||
The [previously announced](/blog/2017/rippled-0.70.0.md) FlowCross Amendment will be enabled on a future date (TBA).
|
||||
|
||||
We do not have an update on the [previously announced](https://developers.ripple.com/blog/2016/rippled-0.33.0.html) changes to the hash tree structure that `rippled` uses to represent a ledger, called [SHAMapV2](https://ripple.com/build/amendments/#shamapv2). At the time of activation, this amendment will require brief scheduled allowable unavailability while the changes to the hash tree structure are computed by the network. We will keep the community updated as we progress towards this date (TBA).
|
||||
We do not have an update on the [previously announced](/blog/2016/rippled-0.33.0.md) changes to the hash tree structure that `rippled` uses to represent a ledger, called [SHAMapV2](/resources/known-amendments.md#shamapv2). At the time of activation, this amendment will require brief scheduled allowable unavailability while the changes to the hash tree structure are computed by the network. We will keep the community updated as we progress towards this date (TBA).
|
||||
|
||||
You can [update to the new version](https://ripple.com/build/rippled-setup/#updating-rippled) on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please [compile the new version from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
You can [update to the new version](/docs/infrastructure/installation/update-rippled-automatically-on-linux) on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please [compile the new version from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md).
|
||||
|
||||
|
||||
## 0.80.0 Change Log
|
||||
|
||||
@@ -25,13 +25,13 @@ If you operate a `rippled` server, then you should upgrade to 0.80.2 immediately
|
||||
|
||||
* **If you operate a `rippled` server**, but do not upgrade to rippled version 0.80.2, then your `rippled` server will use more resources than necessary and may periodically drop transactions and fall out of sync with the network.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The SHA-256 for the RPM is: `a0f431a55a241770d7496b240e4d2c638f2cadd4126ee621c5ed980b8174223c`
|
||||
|
||||
The SHA-256 for the source RPM is: `d25bda2c384c67e48fe6c29250c07039d33c6ed5d280ad19fc246469213fe251`
|
||||
|
||||
For other platforms, please [compile version 0.80.2 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.80.2 from source](https://github.com/XRPLF/rippled/tree/0.80.2/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
@@ -47,14 +47,14 @@ Date: Thu Dec 14 15:30:20 2017 -0800
|
||||
The Ripple technical operations team will deploy `rippled` version 0.80.2 to all production `rippled` servers under its operational control, on Friday, 12/15/2017.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
|
||||
## 0.80.2 Change Log
|
||||
|
||||
@@ -12,27 +12,28 @@ markdown:
|
||||
|
||||
This notice is for all validator operators, and may be useful for gateways that intend to use tick sizes.
|
||||
|
||||
A majority of trusted validators [voted to enable the TickSize amendment](https://developers.ripple.com/blog/2017/ticksize-voting.html), which is scheduled to become active on the protocol on Tuesday, 2017-02-21. The amendment changes the way RCL offers are ranked in order books, so that currency issuers can configure how many significant digits are taken into account when ranking offers by exchange rate.
|
||||
A majority of trusted validators [voted to enable the TickSize amendment](/blog/2017/ticksize-voting), which is scheduled to become active on the protocol on Tuesday, 2017-02-21. The amendment changes the way RCL offers are ranked in order books, so that currency issuers can configure how many significant digits are taken into account when ranking offers by exchange rate.
|
||||
|
||||
For a detailed look into the TickSize feature, see the [original TickSize announcement](https://developers.ripple.com/blog/2017/ticksize-voting.html).
|
||||
For a detailed look into the TickSize feature, see the [original TickSize announcement](/blog/2017/ticksize-voting).
|
||||
|
||||
|
||||
## Action Required
|
||||
|
||||
1. **If you operate a `rippled` server and accept secure client connections**, then you should upgrade to `rippled` version 0.50.2 immediately. If you operate a `rippled` server but do not accept secure client connections, then you should upgrade to version 0.50.0 by Tuesday, 2017-02-21, for service continuity.
|
||||
|
||||
2. **If you are a gateway issuer**, then please review [documentation](https://ripple.com/build/transactions/#offer-preference) for the TickSize amendment to determine what tick size is appropriate for your issuing asset.
|
||||
2. **If you are a gateway issuer**, then please review documentation for the TickSize amendment to determine what tick size is appropriate for your issuing asset.
|
||||
|
||||
3. **If you are a market maker** and have algorithmic trading bots, then please review [documentation](https://ripple.com/build/transactions/#offer-preference) for the TickSize amendment to update your trading system to check the tick size for a given issuer.
|
||||
3. **If you are a market maker** and have algorithmic trading bots, then please review documentation for the TickSize amendment to update your trading system to check the tick size for a given issuer.
|
||||
|
||||
4. **If you have backend software**, which constructs and submits transactions related to the issuing of assets on the Ripple network, then please review [documentation](https://ripple.com/build/transactions/#offer-preference) for the TickSize amendment to adapt it for correct usage.
|
||||
4. **If you have backend software**, which constructs and submits transactions related to the issuing of assets on the Ripple network, then please review documentation for the TickSize amendment to adapt it for correct usage.
|
||||
|
||||
|
||||
## Learn More
|
||||
|
||||
For more information, see the following articles in the [Ripple Developer Portal](https://ripple.com/build/):
|
||||
For more information, see the following articles:
|
||||
|
||||
- [Offer Preference](https://ripple.com/build/transactions/#offer-preference) - How offers are ranked with and without TickSize.
|
||||
- [AccountSet transaction](https://ripple.com/build/transactions/#accountset) - How to configure a TickSize.
|
||||
- [Tick Size](/docs/concepts/tokens/decentralized-exchange/ticksize) - Explanation of how Tick Size works.
|
||||
- [Offer Preference](/docs/concepts/tokens/decentralized-exchange/offers#offer-preference) - How offers are ranked with and without TickSize.
|
||||
- [AccountSet transaction](/docs/references/protocol/transactions/types/accountset) - How to configure a TickSize.
|
||||
|
||||
To continue receiving updates about the rippled server, please subscribe to the Ripple Server Google Group: <https://groups.google.com/forum/#!forum/ripple-server>
|
||||
|
||||
@@ -12,27 +12,28 @@ markdown:
|
||||
|
||||
This notice is for all validator operators, and may be useful for gateways that intend to use tick sizes.
|
||||
|
||||
A majority of trusted validators [voted to enable the TickSize amendment](https://developers.ripple.com/blog/2017/ticksize-voting.html), which is scheduled to become active on the protocol on Tuesday, 2017-02-21. The amendment changes the way RCL offers are ranked in order books, so that currency issuers can configure how many significant digits are taken into account when ranking offers by exchange rate.
|
||||
A majority of trusted validators [voted to enable the TickSize amendment](/blog/2017/ticksize-voting.md), which is scheduled to become active on the protocol on Tuesday, 2017-02-21. The amendment changes the way RCL offers are ranked in order books, so that currency issuers can configure how many significant digits are taken into account when ranking offers by exchange rate.
|
||||
|
||||
For a detailed look into the TickSize feature, see the [original TickSize announcement](https://developers.ripple.com/blog/2017/ticksize-voting.html).
|
||||
For a detailed look into the TickSize feature, see the [original TickSize announcement](/blog/2017/ticksize-voting.md).
|
||||
|
||||
|
||||
## Action Required
|
||||
|
||||
1. **If you operate a `rippled` server and accept secure client connections**, then you should upgrade to `rippled` version 0.50.2 immediately. If you operate a `rippled` server but do not accept secure client connections, then you should upgrade to version 0.50.0 by Tuesday, 2017-02-21, for service continuity.
|
||||
|
||||
2. **If you are a gateway issuer**, then please review [documentation](https://ripple.com/build/transactions/#offer-preference) for the TickSize amendment to determine what tick size is appropriate for your issuing asset.
|
||||
2. **If you are a gateway issuer**, then please review documentation for the TickSize amendment to determine what tick size is appropriate for your issuing asset.
|
||||
|
||||
3. **If you are a market maker** and have algorithmic trading bots, then please review [documentation](https://ripple.com/build/transactions/#offer-preference) for the TickSize amendment to update your trading system to check the tick size for a given issuer.
|
||||
3. **If you are a market maker** and have algorithmic trading bots, then please review documentation for the TickSize amendment to update your trading system to check the tick size for a given issuer.
|
||||
|
||||
4. **If you have backend software**, which constructs and submits transactions related to the issuing of assets on the Ripple network, then please review [documentation](https://ripple.com/build/transactions/#offer-preference) for the TickSize amendment to adapt it for correct usage.
|
||||
4. **If you have backend software**, which constructs and submits transactions related to the issuing of assets on the Ripple network, then please review documentation for the TickSize amendment to adapt it for correct usage.
|
||||
|
||||
|
||||
## Learn More
|
||||
|
||||
For more information, see the following articles in the [Ripple Developer Portal](https://ripple.com/build/):
|
||||
For more information, see the following articles:
|
||||
|
||||
- [Offer Preference](https://ripple.com/build/transactions/#offer-preference) - How offers are ranked with and without TickSize.
|
||||
- [AccountSet transaction](https://ripple.com/build/transactions/#accountset) - How to configure a TickSize.
|
||||
- [Tick Size](/docs/concepts/tokens/decentralized-exchange/ticksize) - Explanation of how Tick Size works.
|
||||
- [Offer Preference](/docs/concepts/tokens/decentralized-exchange/offers#offer-preference) - How offers are ranked with and without TickSize.
|
||||
- [AccountSet transaction](/docs/references/protocol/transactions/types/accountset) - How to configure a TickSize.
|
||||
|
||||
To continue receiving updates about the rippled server, please subscribe to the Ripple Server Google Group: <https://groups.google.com/forum/#!forum/ripple-server>
|
||||
|
||||
@@ -10,7 +10,7 @@ markdown:
|
||||
---
|
||||
# TickSize is Now Available
|
||||
|
||||
As [predicted previously](https://developers.ripple.com/blog/2017/ticksize-3days.html), the TickSize amendment became available on the Ripple Consensus Ledger yesterday afternoon (PST) in ledger 27841793 ([2017-02-21T23:02:52Z](https://xrpcharts.ripple.com/#/transactions/A12430E470BE5C846759EAE3C442FF03374D5D73ECE5815CF4906894B769565E)).
|
||||
As [predicted previously](/blog/2017/ticksize-3days.md), the TickSize amendment became available on the Ripple Consensus Ledger yesterday afternoon (PST) in ledger 27841793 ([2017-02-21T23:02:52Z](https://xrpcharts.ripple.com/#/transactions/A12430E470BE5C846759EAE3C442FF03374D5D73ECE5815CF4906894B769565E)).
|
||||
|
||||
The amendment changes the way RCL offers are ranked in order books, so that currency issuers can configure how many significant digits are taken into account when ranking offers by exchange rate.
|
||||
|
||||
@@ -19,16 +19,16 @@ The amendment changes the way RCL offers are ranked in order books, so that curr
|
||||
|
||||
1. **If you operate a `rippled` server and accept secure client connections**, then you should upgrade to version 0.50.2 immediately. If you operate a `rippled` server but do not accept secure client connections, then you should upgrade to version 0.50.0 or higher immediately.
|
||||
|
||||
2. **If you issue currency on the RCL**, then please review [documentation](https://ripple.com/build/transactions/#offer-preference) for the TickSize amendment to determine what tick size is appropriate for your issuing asset. If you take no action, your issued currency can still be traded using the default tick size of 15 significant digits, but Ripple strongly recommends setting a tick size between four and eight digits to provide faster price discovery and to decrease churn in the RCL order books for your currency. Ripple also recommends publishing your tick size policy to users.
|
||||
2. **If you issue currency on the RCL**, then please review documentation for the TickSize amendment to determine what tick size is appropriate for your issuing asset. If you take no action, your issued currency can still be traded using the default tick size of 15 significant digits, but Ripple strongly recommends setting a tick size between four and eight digits to provide faster price discovery and to decrease churn in the RCL order books for your currency. Ripple also recommends publishing your tick size policy to users.
|
||||
|
||||
3. **If you trade on the RCL** and have algorithmic trading bots, then please review [documentation](https://ripple.com/build/transactions/#offer-preference) for the TickSize amendment to update your trading system to check the tick size for a given issuer.
|
||||
3. **If you trade on the RCL** and have algorithmic trading bots, then please review documentation for the TickSize amendment to update your trading system to check the tick size for a given issuer.
|
||||
|
||||
4. **If you have backend software** which constructs and submits transactions related to the issuing of assets on the Ripple Consensus Ledger, then please review [documentation](https://ripple.com/build/transactions/#offer-preference) for the TickSize amendment to adapt your software for correct usage.
|
||||
4. **If you have backend software** which constructs and submits transactions related to the issuing of assets on the Ripple Consensus Ledger, then please review documentation for the TickSize amendment to adapt your software for correct usage.
|
||||
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
If you operate a `rippled` server but don’t upgrade to version 0.50.0 or higher, immediately, then your server will become [amendment blocked](https://ripple.com/build/amendments/#amendment-blocked), meaning that your server:
|
||||
If you operate a `rippled` server but don’t upgrade to version 0.50.0 or higher, immediately, then your server will become [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that your server:
|
||||
|
||||
* Cannot determine the validity of a ledger
|
||||
* Cannot submit or process transactions
|
||||
@@ -40,8 +40,8 @@ If you operate a `rippled` server but don’t upgrade to version 0.50.0 or highe
|
||||
|
||||
For more information, see the following documentation:
|
||||
|
||||
- [TickSize Voting Announcement](https://developers.ripple.com/blog/2017/ticksize-voting.html) - Introduction to TickSize and recommendations for how to use it.
|
||||
- [Offer Preference](https://ripple.com/build/transactions/#offer-preference) - How offers are ranked with and without TickSize.
|
||||
- [AccountSet transaction](https://ripple.com/build/transactions/#accountset) - How to configure a TickSize.
|
||||
- [Tick Size](/docs/concepts/tokens/decentralized-exchange/ticksize) - Explanation of how Tick Size works.
|
||||
- [Offer Preference](/docs/concepts/tokens/decentralized-exchange/offers#offer-preference) - How offers are ranked with and without TickSize.
|
||||
- [AccountSet transaction](/docs/references/protocol/transactions/types/accountset) - How to configure a TickSize.
|
||||
|
||||
To continue receiving updates about the rippled server, please subscribe to the Ripple Server Google Group: <https://groups.google.com/forum/#!forum/ripple-server>
|
||||
|
||||
@@ -10,7 +10,7 @@ markdown:
|
||||
---
|
||||
# TickSize Amendment Open for Voting
|
||||
|
||||
Previously [introduced](https://developers.ripple.com/blog/2017/rippled-0.50.0.html) in `rippled` version 0.50.0, the [TickSize amendment](https://ripple.com/build/amendments/#ticksize) to the Ripple Consensus Ledger is now open for voting. The amendment changes the way offers are ranked in the RCL's order books, so that currency issuers can configure how many significant digits are taken into account when ranking offers by exchange rate.
|
||||
Previously [introduced](/blog/2017/rippled-0.50.0.md) in `rippled` version 0.50.0, the [TickSize amendment](/resources/known-amendments.md#ticksize) to the Ripple Consensus Ledger is now open for voting. The amendment changes the way offers are ranked in the RCL's order books, so that currency issuers can configure how many significant digits are taken into account when ranking offers by exchange rate.
|
||||
|
||||
Ripple expects several benefits to result from adoption of the TickSize amendment, including faster price discovery and deeper liquidity, as well as a reduction in transaction spam and ledger churn on the RCL.
|
||||
|
||||
@@ -20,11 +20,11 @@ The introduction of TickSize demonstrates Ripple’s continued commitment to sup
|
||||
|
||||
1. **If you operate a `rippled` server and accept secure client connections**, then you should upgrade to 0.50.2 immediately. If you operate a rippled server, but do not accept secure client connections then you should upgrade to version 0.50.0 by Tuesday, 2017-02-21, for service continuity.
|
||||
|
||||
2. **If you run a gateway that issues currency on the RCL**, then please review [documentation](https://ripple.com/build/transactions/#offer-preference) for the TickSize amendment to determine what tick size is appropriate for your issuing asset.
|
||||
2. **If you run a gateway that issues currency on the RCL**, then please review documentation for the TickSize amendment to determine what tick size is appropriate for your issuing asset.
|
||||
|
||||
3. **If you trade on the RCL** and have algorithmic trading bots, then please review [documentation](https://ripple.com/build/transactions/#offer-preference) for the TickSize amendment to update your trading system to check the tick size for a given issuer.
|
||||
3. **If you trade on the RCL** and have algorithmic trading bots, then please review documentation for the TickSize amendment to update your trading system to check the tick size for a given issuer.
|
||||
|
||||
4. **If you have backend software**, which constructs and submits transactions related to the issuing of assets on the Ripple network, then please review [documentation](https://ripple.com/build/transactions/#offer-preference) for the TickSize amendment to adapt it for correct usage.
|
||||
4. **If you have backend software**, which constructs and submits transactions related to the issuing of assets on the Ripple network, then please review documentation for the TickSize amendment to adapt it for correct usage.
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
@@ -38,17 +38,17 @@ If you operate a `rippled` server but don’t upgrade to version 0.50.0 (or high
|
||||
|
||||
If the **TickSize** amendment is vetoed or does not pass, then your server will not become amendment blocked and should continue to operate.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
|
||||
## TickSize Amendment Overview
|
||||
@@ -117,8 +117,8 @@ Tick sizes of between four and eight digits are reasonable. Four digits will pro
|
||||
|
||||
## Upcoming Features
|
||||
|
||||
The [previously announced](https://developers.ripple.com/blog/2016/rippled-0.40.0.html) Suspended Payments amendment, which introduces new transaction types to the Ripple protocol that will permit users to cryptographically escrow XRP on the RCL, will be re-introduced as an amendment simply called *Escrow*, in the next release scheduled for March.
|
||||
The [previously announced](/blog/2016/rippled-0.40.0.md) Suspended Payments amendment, which introduces new transaction types to the Ripple protocol that will permit users to cryptographically escrow XRP on the RCL, will be re-introduced as an amendment simply called *Escrow*, in the next release scheduled for March.
|
||||
|
||||
Also, we expect additional support for [crypto-conditions](https://tools.ietf.org/html/draft-thomas-crypto-conditions-02), which are signature-like structures that can be used with suspended payments to support ILP integration, to be included in the next rippled release scheduled for March.
|
||||
|
||||
Lastly, we do not have an update on the [previously announced](https://developers.ripple.com/blog/2016/rippled-0.33.0.html) changes to the hash tree structure that `rippled` uses to represent a ledger, called [SHAMapV2](https://ripple.com/build/amendments/#shamapv2). At the time of activation, this amendment will require brief scheduled allowable unavailability while the changes to the hash tree structure are computed by the network. We will keep the community updated as we progress towards this date (TBA).
|
||||
Lastly, we do not have an update on the [previously announced](/blog/2016/rippled-0.33.0.md) changes to the hash tree structure that `rippled` uses to represent a ledger, called [SHAMapV2](/resources/known-amendments.md#shamapv2). At the time of activation, this amendment will require brief scheduled allowable unavailability while the changes to the hash tree structure are computed by the network. We will keep the community updated as we progress towards this date (TBA).
|
||||
|
||||
@@ -39,6 +39,6 @@ To experiment with the Ripple Consensus Ledger technology without using real mon
|
||||
### Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* The Ripple Dev Blog: <https://developers.ripple.com/blog/>
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* XRP Chat: <http://www.xrpchat.com>
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -10,7 +10,7 @@ markdown:
|
||||
---
|
||||
# Updates Coming to Data API
|
||||
|
||||
The [Data API](https://developers.ripple.com/data-api.html), which provides data to [XRP Charts](https://xrpcharts.ripple.com/) and third-party tools, is scheduled to update to **version 2.4.0** in approximately two weeks, on **2018-11-07**. This version improves the way the Data API imports and summarizes data on XRP Ledger validators.
|
||||
The Data API, which provides data to XRP Charts and third-party tools, is scheduled to update to **version 2.4.0** in approximately two weeks, on **2018-11-07**. This version improves the way the Data API imports and summarizes data on XRP Ledger validators.
|
||||
|
||||
|
||||
## Improvements
|
||||
@@ -32,10 +32,10 @@ This release contains the following breaking changes:
|
||||
- **Get Validations** (`/v2/network/validations`)
|
||||
- **Get Validator Validations** (`/v2/network/validators/{pubkey}/validations`)
|
||||
- **Format Changes.** The request and response formats of the following methods have changed.
|
||||
- **[Get Validator](https://developers.ripple.com/data-api.html#get-validator)** (`/v2/network/validators/{pubkey}`)
|
||||
- **[Get Validators](https://developers.ripple.com/data-api.html#get-validators)** (`/v2/network/validators`)
|
||||
- **[Get Daily Validator Reports](https://developers.ripple.com/data-api.html#get-daily-validator-reports)** (`/v2/network/validator_reports`)
|
||||
- **[Get Single Validator Daily Reports](https://developers.ripple.com/data-api.html#get-single-validator-reports)** (`/v2/network/validators/{pubkey}/validator_reports`)
|
||||
- **Get Validator** (`/v2/network/validators/{pubkey}`)
|
||||
- **Get Validators** (`/v2/network/validators`)
|
||||
- **Get Daily Validator Reports** (`/v2/network/validator_reports`)
|
||||
- **Get Single Validator Daily Reports** (`/v2/network/validators/{pubkey}/validator_reports`)
|
||||
|
||||
If you use any of the above API methods, you may need to make changes to use the updated API.
|
||||
|
||||
@@ -43,4 +43,4 @@ If you use any of the above API methods, you may need to make changes to use the
|
||||
|
||||
You can try out the new methods by using `http://data-staging.ripple.com` as your base URL.
|
||||
|
||||
The [API Reference documentation](https://developers.ripple.com/data-api.html) will be updated with the new formats soon.
|
||||
The API Reference documentation will be updated with the new formats soon.
|
||||
|
||||
@@ -10,7 +10,7 @@ markdown:
|
||||
---
|
||||
# The DepositAuth & fix1513 Amendments are Now Available
|
||||
|
||||
The [DepositAuth](https://ripple.com/build/deposit-authorization/) & fix1513 Amendments became available on the XRP Ledger in ledger sequence number 37,753,345 [(2018-04-06T01:44:42Z)](https://xrpcharts.ripple.com/#/transactions/902C51270B918B40CD23A622E18D48B4ABB86F0FF4E84D72D9E1907BF3BD4B25).
|
||||
The DepositAuth & fix1513 Amendments became available on the XRP Ledger in ledger sequence number 37,753,345 [(2018-04-06T01:44:42Z)](https://xrpcharts.ripple.com/#/transactions/902C51270B918B40CD23A622E18D48B4ABB86F0FF4E84D72D9E1907BF3BD4B25).
|
||||
|
||||
* The DepositAuth Amendment lets an account strictly reject any incoming money from transactions sent by other accounts.
|
||||
* The fix1513 Amendment fixes an issue where calculation switchovers were not implemented in the fee escalation queue.
|
||||
@@ -29,25 +29,25 @@ The [DepositAuth](https://ripple.com/build/deposit-authorization/) & fix1513 Ame
|
||||
* Does not vote on future amendments
|
||||
* Could rely on potentially invalid data
|
||||
|
||||
If you are using `rippled` version 0.90.0, your server is not amendment blocked but you should upgrade to [`rippled` version **0.90.1**](https://developers.ripple.com/blog/2018/rippled-0.90.1.html) or higher to get important security fixes. `rippled` version 0.90.0 may stop or restart unexpectedly.
|
||||
If you are using `rippled` version 0.90.0, your server is not amendment blocked but you should upgrade to [`rippled` version **0.90.1**](/blog/2018/rippled-0.90.1.md) or higher to get important security fixes. `rippled` version 0.90.0 may stop or restart unexpectedly.
|
||||
|
||||
For instructions on updating rippled on supported platforms, see [Updating rippled on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating rippled on supported platforms, see [Updating rippled on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
For other platforms, please compile version 0.90.1 from source. See [the `rippled` GitHub repo](https://github.com/ripple/rippled/tree/develop/Builds) for instructions by platform. For instructions building `rippled` from source on Ubuntu Linux, see [Build and Run `rippled` on Ubuntu](https://ripple.com/build/build-run-rippled-ubuntu/).
|
||||
For other platforms, please [compile version 0.90.1 from source](https://github.com/XRPLF/rippled/tree/0.90.1/Builds).
|
||||
|
||||
## Upcoming Features
|
||||
|
||||
The [previously announced](https://developers.ripple.com/blog/2018/rippled-0.90.0.html) Checks amendment has lost the support of a majority of trusted validators and is not expected to become enabled in the immediate future.
|
||||
The [previously announced](/blog/2018/rippled-0.90.0.md) Checks amendment has lost the support of a majority of trusted validators and is not expected to become enabled in the immediate future.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
To continue receiving updates about the `rippled` server, please subscribe to the Ripple Server Google Group: <https://groups.google.com/forum/#!forum/ripple-server>
|
||||
|
||||
Other resources:
|
||||
|
||||
- The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
- [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
- The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
- Ripple Technical Services: <support@ripple.com>
|
||||
- [XRP Chat](http://www.xrpchat.com/)
|
||||
|
||||
@@ -10,13 +10,13 @@ markdown:
|
||||
---
|
||||
# DepositPreauth is Now Available
|
||||
|
||||
The [DepositPreauth](https://xrpcharts.ripple.com/#/transactions/AD27403CB840AE67CADDB084BC54249D7BD1B403885819B39CCF723DC671F927) and [fix1515](https://xrpcharts.ripple.com/#/transactions/6DF60D9EC8AF3C39B173840F4D1C57F8A8AB51E7C6571483B4A5F1AA0A9AAEBF) amendments, [added in `rippled` v1.1.0](https://developers.ripple.com/blog/2018/rippled-1.1.0.html), became enabled on the XRP Ledger today, 2018-10-09.
|
||||
The [DepositPreauth](https://xrpcharts.ripple.com/#/transactions/AD27403CB840AE67CADDB084BC54249D7BD1B403885819B39CCF723DC671F927) and [fix1515](https://xrpcharts.ripple.com/#/transactions/6DF60D9EC8AF3C39B173840F4D1C57F8A8AB51E7C6571483B4A5F1AA0A9AAEBF) amendments, [added in `rippled` v1.1.0](/blog/2018/rippled-1.1.0.md), became enabled on the XRP Ledger today, 2018-10-09.
|
||||
|
||||
## Action Required
|
||||
|
||||
- If you operate a `rippled` server, you should upgrade to version 1.1.0 (or higher) immediately.
|
||||
|
||||
For instructions on upgrading `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://developers.ripple.com/update-rippled.html).
|
||||
For instructions on upgrading `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
@@ -30,7 +30,7 @@ If you operate a `rippled` server on a version older than 1.1.0, then your serve
|
||||
|
||||
## DepositPreauth Summary
|
||||
|
||||
The DepositPreauth amendment provides users of [deposit authorization](https://developers.ripple.com/depositauth.html) with a way to preauthorize specific senders so those senders are allowed to send payments directly.
|
||||
The DepositPreauth amendment provides users of [deposit authorization](/docs/concepts/accounts/depositauth) with a way to preauthorize specific senders so those senders are allowed to send payments directly.
|
||||
|
||||
The amendment adds:
|
||||
|
||||
@@ -53,11 +53,11 @@ In both cases, transaction processing can still complete by using liquidity from
|
||||
|
||||
|
||||
## Learn More
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](https://developers.ripple.com/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](/docs/), including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -10,7 +10,7 @@ markdown:
|
||||
---
|
||||
# fix1543, fix1571 & fix1623 Amendments Open for Voting
|
||||
|
||||
Previously [introduced in `rippled` version 1.0.0](https://developers.ripple.com/blog/2018/rippled-1.0.0.html), the [fix1543](https://developers.ripple.com/known-amendments.html#fix1543), [fix1571](https://developers.ripple.com/known-amendments.html#fix1571) and [fix1623](https://developers.ripple.com/known-amendments.html#fix1623) amendments are now open for voting.
|
||||
Previously [introduced in `rippled` version 1.0.0](/blog/2018/rippled-1.0.0.md), the [fix1543](/resources/known-amendments.md#fix1543), [fix1571](/resources/known-amendments.md#fix1571) and [fix1623](/resources/known-amendments.md#fix1623) amendments are now open for voting.
|
||||
|
||||
* The `fix1543` amendment enforces reserved flag ranges on escrow, payment channel, and ticket transactions.
|
||||
* The `fix1571` amendment changes the EscrowCreate transaction to require the Condition or FinishAfter field (or both) and also fixes a flaw that incorrectly prevents time-based Escrows from being finished in some circumstances.
|
||||
@@ -22,7 +22,7 @@ Previously [introduced in `rippled` version 1.0.0](https://developers.ripple.com
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
If you operate a `rippled` server but don’t upgrade to version 1.0.0 by Tuesday, 2018-06-19, when the [fix1543](https://developers.ripple.com/known-amendments.html#fix1543), [fix1571](https://developers.ripple.com/known-amendments.html#fix1571) and [fix1623](https://developers.ripple.com/known-amendments.html#fix1623) amendments are expected to become enabled on the network, then your server will become [amendment blocked](https://developers.ripple.com/amendments.html#amendment-blocked), meaning that your server:
|
||||
If you operate a `rippled` server but don’t upgrade to version 1.0.0 by Tuesday, 2018-06-19, when the [fix1543](/resources/known-amendments.md#fix1543), [fix1571](/resources/known-amendments.md#fix1571) and [fix1623](/resources/known-amendments.md#fix1623) amendments are expected to become enabled on the network, then your server will become [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that your server:
|
||||
|
||||
* Cannot determine the validity of a ledger
|
||||
* Cannot submit or process transactions
|
||||
@@ -30,16 +30,16 @@ If you operate a `rippled` server but don’t upgrade to version 1.0.0 by Tuesda
|
||||
* Does not vote on future amendments
|
||||
* Could rely on potentially invalid data
|
||||
|
||||
If the [fix1543](https://developers.ripple.com/known-amendments.html#fix1543), [fix1571](https://developers.ripple.com/known-amendments.html#fix1571) and [fix1623](https://developers.ripple.com/known-amendments.html#fix1623) amendments do not become enabled, then your server will not become amendment blocked and should continue to operate.
|
||||
If the [fix1543](/resources/known-amendments.md#fix1543), [fix1571](/resources/known-amendments.md#fix1571) and [fix1623](/resources/known-amendments.md#fix1623) amendments do not become enabled, then your server will not become amendment blocked and should continue to operate.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](https://developers.ripple.com/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](/docs/), including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
To continue receiving updates about the `rippled` server, please subscribe to the Ripple Server Google Group: <https://groups.google.com/forum/#!forum/ripple-server>
|
||||
|
||||
@@ -14,9 +14,9 @@ As previously announced, the fix1571 amendment [became enabled on the XRP Ledger
|
||||
|
||||
## Action Required
|
||||
|
||||
- If you operate a `rippled` server, you should upgrade to [version 1.0.1](https://developers.ripple.com/blog/2018/rippled-1.0.1.html) (or higher) immediately.
|
||||
- If you operate a `rippled` server, you should upgrade to [version 1.0.1](/blog/2018/rippled-1.0.1.md) (or higher) immediately.
|
||||
|
||||
For instructions on upgrading `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://developers.ripple.com/update-rippled.html).
|
||||
For instructions on upgrading `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
@@ -32,15 +32,15 @@ If you operate a `rippled` server on a version older than 1.0.0, then your serve
|
||||
|
||||
Changes Escrow to fix the following issues:
|
||||
|
||||
- Changes the [EscrowCreate transaction](https://developers.ripple.com/escrowcreate.html) to require the `Condition` or `FinishAfter` field (or both). Escrows with neither `Condition` nor `FinishAfter` that were created before this amendment can be finished by anyone at any time before their `CancelAfter` time.
|
||||
- Changes the [EscrowCreate transaction](/docs/references/protocol/transactions/types/escrowcreate) to require the `Condition` or `FinishAfter` field (or both). Escrows with neither `Condition` nor `FinishAfter` that were created before this amendment can be finished by anyone at any time before their `CancelAfter` time.
|
||||
- Fixes a flaw that incorrectly prevents time-based Escrows from being finished in some circumstances.
|
||||
|
||||
## Learn More
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](https://developers.ripple.com/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](/docs/), including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -14,7 +14,9 @@ As `rippled` servers operate, they continually witness data appended onto an eve
|
||||
|
||||
As with most blockchains, it is imperative that XRP Ledger historical data remain readily available to participating servers. Therefore, every `rippled` server shares the responsibility of storing some history. But what if keeping the full history of the XRP Ledger starts to exceed the storage facility of most participants? For example, as of this writing, the space required to store full history of the XRP Ledger is over 8 terabytes, a hefty flash sum.
|
||||
|
||||
The [history sharding](https://developers.ripple.com/history-sharding.html) feature, enabled in `rippled` version 0.90.0, addresses this issue by distributing history into segments called shards. A shard contains all of the data for a range of ledgers. Using the history sharding feature, individual `rippled` servers can contribute to storing historical data without needing to store the entire history.
|
||||
The history sharding feature, enabled in `rippled` version 0.90.0, addresses this issue by distributing history into segments called shards. A shard contains all of the data for a range of ledgers. Using the history sharding feature, individual `rippled` servers can contribute to storing historical data without needing to store the entire history.
|
||||
|
||||
> _(Update: History sharding was removed in version 2.3.0.)_
|
||||
|
||||
<!-- BREAK -->
|
||||
|
||||
@@ -24,7 +26,7 @@ Because servers that are configured with history sharding randomly select the sh
|
||||
|
||||
## Shard Store Validation
|
||||
|
||||
Beginning with `rippled` version 0.90.0, you can use the [`--validateShards`](https://developers.ripple.com/commandline-usage.html#daemon-mode-options) command to check that shard store data is valid and consistent with network history. For example:
|
||||
Beginning with `rippled` version 0.90.0, you can use the `--validateShards` command to check that shard store data is valid and consistent with network history. For example:
|
||||
|
||||
./rippled --validateShards
|
||||
|
||||
@@ -33,13 +35,13 @@ This operation verifies that all objects stored for every ledger stored in each
|
||||
|
||||
## Node Store to Shard Store
|
||||
|
||||
Beginning with `rippled` version 1.0.0, you can use the [`--nodetoshard'](https://developers.ripple.com/commandline-usage.html#daemon-mode-options) command to import the data from an existing ledger store into a shard store. For example:
|
||||
Beginning with `rippled` version 1.0.0, you can use the `--nodetoshard' command to import the data from an existing ledger store into a shard store. For example:
|
||||
|
||||
./rippled --nodetoshard
|
||||
|
||||
This command enables you to create shards based on the history you already have. The command creates shards from complete ledger ranges in the ledger store.
|
||||
|
||||
The command creates a copy of the data, so your server must have the additional disk space required by the shard maximum disk space setting ([`max_size_gb`](https://developers.ripple.com/history-sharding.html#shard-store-configuration)) in the `rippled.cfg` configuration file.
|
||||
The command creates a copy of the data, so your server must have the additional disk space required by the shard maximum disk space setting (`max_size_gb`) in the `rippled.cfg` configuration file.
|
||||
|
||||
|
||||
## Downloadable Shard Archives
|
||||
@@ -58,4 +60,3 @@ Beginning with `rippled` version 1.1.0, you can use the `download_shard` API met
|
||||
|
||||
A shard archive is a [tar](https://en.wikipedia.org/wiki/Tar_(computing)) of a complete shard directory compressed with LZ4. Downloaded archives are checked to be valid and consistent with network history before being imported.
|
||||
|
||||
For more information, see [History Sharding](https://developers.ripple.com/history-sharding.html).
|
||||
|
||||
@@ -56,14 +56,14 @@ The following changes were introduced in 1.0.0.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
[ripple-lib Documentation](https://developers.ripple.com/rippleapi-reference.html) is available in the XRP Ledger Dev Portal.
|
||||
ripple-lib Documentation is available in the XRP Ledger Dev Portal.
|
||||
|
||||
Other resources:
|
||||
|
||||
* [Full Release History](https://github.com/ripple/ripple-lib/blob/develop/HISTORY.md)
|
||||
* [GitHub Issues](https://github.com/ripple/ripple-lib/issues)
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat Forum](http://www.xrpchat.com/)
|
||||
* XRP Chat Forum _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
## Other Information
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ markdown:
|
||||
---
|
||||
# rippled Version 0.81.0
|
||||
|
||||
Ripple has released `rippled` version 0.81.0, which introduces changes that improve the scalability of the XRP Ledger and transitions the recommended validator configuration to a new hosted site, as described in [Ripple's Decentralization Strategy Update](https://developers.ripple.com/blog/2017/decent-strategy-update.html) post.
|
||||
Ripple has released `rippled` version 0.81.0, which introduces changes that improve the scalability of the XRP Ledger and transitions the recommended validator configuration to a new hosted site, as described in [Ripple's Decentralization Strategy Update](/blog/2017/decent-strategy-update.md) post.
|
||||
|
||||
Ripple strongly recommends upgrading to `rippled` version 0.81.0 immediately.
|
||||
|
||||
@@ -21,7 +21,7 @@ If you operate a `rippled` server, then you should upgrade to `rippled` version
|
||||
Ripple recommends that you:
|
||||
|
||||
* Edit your `rippled.cfg` to remove the `[validators]` section, if one is present.
|
||||
* Replace the contents of any existing `validators.txt` file with the [version included with this release](https://github.com/ripple/rippled/blob/4e8c8deeaac83d18eb62c95b7425d96e11847a41/doc/validators-example.txt#L51-L55). If you are upgrading to `rippled` version 0.81.0 [using the rippled RPM package](https://ripple.com/build/rippled-setup/#updating-rippled), then your default `validators.txt` file may automatically be updated, in which case you will not need to modify the file. The `validators.txt` file is usually in the same directory as your `rippled.cfg` file.
|
||||
* Replace the contents of any existing `validators.txt` file with the [version included with this release](https://github.com/ripple/rippled/blob/4e8c8deeaac83d18eb62c95b7425d96e11847a41/doc/validators-example.txt#L51-L55). If you are upgrading to `rippled` version 0.81.0 [using the rippled RPM package](/docs/infrastructure/installation/update-rippled-automatically-on-linux), then your default `validators.txt` file may automatically be updated, in which case you will not need to modify the file. The `validators.txt` file is usually in the same directory as your `rippled.cfg` file.
|
||||
* After starting your `rippled` server, confirm that it is configured to use the new defaults by executing:
|
||||
|
||||
`/opt/ripple/bin/rippled validators`
|
||||
@@ -52,35 +52,37 @@ The result should include the following:
|
||||
|
||||
* On Tuesday January 16, 2018, the current validator keys on all five Ripple-operated `rippled` validator servers will be replaced. **If you have been using the recommended default configuration** and do not reconfigure your `rippled` server before that time, then your `rippled` server will stop seeing validated ledgers.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The sha256 for the rpm is: 75acdf54e472875bff609fa2d1cc59524e4d8f8e885751b50aaeb85938ab3609
|
||||
|
||||
The sha256 for the source rpm is: fbc95f6168d015190b93b81f97c20979886fa2f6663e4dd15157409075db46e9
|
||||
|
||||
For other platforms, please [compile version 0.81.0 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.81.0 from source](https://github.com/XRPLF/rippled/tree/0.81.0/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 4e8c8deeaac83d18eb62c95b7425d96e11847a41
|
||||
Author: Nikolaos D. Bougalis <nikb@bougalis.net>
|
||||
Date: Wed Jan 3 14:43:42 2018 -0800
|
||||
|
||||
Set version to 0.81.0
|
||||
```
|
||||
|
||||
|
||||
## Network Update
|
||||
The Ripple technical operations team will deploy `rippled` version 0.81.0 to all `rippled` servers under its operational control, Tuesday, 01/09/2018.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
|
||||
## 0.81.0 Change Log
|
||||
|
||||
@@ -27,7 +27,7 @@ If you operate a `rippled` server, you should upgrade to `rippled` version 0.90.
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
* **If you operate a `rippled` server**, but do not upgrade to `rippled` version 0.90.0 by **Thursday, 2018-03-15**, when DepositAuth and Checks are expected to be enabled via Amendment, then your rippled server will become [amendment blocked](https://ripple.com/build/amendments/#amendment-blocked), meaning that your server:
|
||||
* **If you operate a `rippled` server**, but do not upgrade to `rippled` version 0.90.0 by **Thursday, 2018-03-15**, when DepositAuth and Checks are expected to be enabled via Amendment, then your rippled server will become [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that your server:
|
||||
|
||||
* Cannot determine the validity of a ledger
|
||||
* Cannot submit or process transactions
|
||||
@@ -37,21 +37,23 @@ If you operate a `rippled` server, you should upgrade to `rippled` version 0.90.
|
||||
|
||||
If the **DepositAuth** and **Checks** Amendments do not get approved, then your `rippled` server will not become Amendment blocked and should continue to operate.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The SHA-256 for the RPM is: `7d6c6d9908289edbf38660f0ab2a233b159ac7abfe502ae774bf9af579270613`
|
||||
|
||||
The SHA-256 for the source RPM is: `faf0d669a38b7f97acd2d4b95b48a8c50a9859a6235be2ed289d10c6c5f96a1f`
|
||||
|
||||
For other platforms, please compile version 0.90.0 from source. See the [`rippled` source tree](https://github.com/ripple/rippled/tree/develop/Builds) for instructions by platform. For instructions building `rippled` from source on Ubuntu Linux, see [Build and Run `rippled` on Ubuntu](https://ripple.com/build/build-run-rippled-ubuntu/).
|
||||
For other platforms, please [compile version 0.90.0 from source](https://github.com/XRPLF/rippled/tree/0.90.0/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 6230204e425f6aef6ec1c0def0bdd1257e1c4c7f
|
||||
Author: Nikolaos D. Bougalis <nikb@bougalis.net>
|
||||
Date: Tue Feb 20 14:12:03 2018 -0800
|
||||
|
||||
Set version to 0.90.0
|
||||
```
|
||||
|
||||
## Action Recommended: Configure History Shards
|
||||
|
||||
@@ -85,14 +87,14 @@ Other compatible versions differ by platform. Boost 1.58.0 is compatible on Linu
|
||||
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
## Full Release Notes
|
||||
|
||||
@@ -104,11 +106,11 @@ If an Escrow has a Destination with the DepositAuth flag set, then the correspon
|
||||
|
||||
As an exception, accounts with DepositAuth enabled can receive XRP payment transactions for small amounts of XRP (equal or less than the minimum account reserve) if their current XRP balance is below the account reserve.
|
||||
|
||||
For more information, see <https://ripple.com/build/deposit-authorization/>
|
||||
For more information, see [Deposit Authorization](/docs/concepts/accounts/depositauth).
|
||||
|
||||
### Checks
|
||||
|
||||
The Checks Amendment works similarly to personal paper checks and introduces a new ledger object type ([Check](https://ripple.com/build/ledger-format/#check)), a new transaction result code ([tecEXPIRED](https://ripple.com/build/transactions/#tec-codes)) and three new transaction types ([CheckCreate](https://ripple.com/build/transactions/#checkcreate), [CheckCash](https://ripple.com/build/transactions/#checkcash), [CheckCancel](https://ripple.com/build/transactions/#checkcancel)) to the XRP Ledger.
|
||||
The Checks Amendment works similarly to personal paper checks and introduces a new ledger object type ([Check](/docs/references/protocol/ledger-data/ledger-entry-types/check)), a new transaction result code ([tecEXPIRED](/docs/references/protocol/transactions/transaction-results/tec-codes)) and three new transaction types ([CheckCreate](/docs/references/protocol/transactions/types/checkcreate), [CheckCash](/docs/references/protocol/transactions/types/checkcash), [CheckCancel](/docs/references/protocol/transactions/types/checkcancel)) to the XRP Ledger.
|
||||
|
||||
The sender signs a CheckCreate transaction to create a Check for a specific maximum amount and specifies a destination account to receive the funds. Later, the destination account can sign a CheckCash transaction to cash the Check and receive up to the specified amount. The actual movement of money only occurs when the Check is cashed, so cashing the Check may fail depending on the sender's current balance and the available liquidity. An account with the DepositAuth flag set can receive funds using a CheckCash transaction.
|
||||
|
||||
@@ -118,7 +120,7 @@ If cashing the Check fails, the Check object remains in the ledger so it may be
|
||||
|
||||
History Sharding allows `rippled` servers to distribute historical ledger data if they agree to keep particular ranges of historical ledgers. This makes it very easy for servers to confirm that they have all the data that they're supposed to have. Further, History Sharding makes it simpler to produce proof trees or ledger deltas and challenge servers to demonstrate they actually hold the data they claim to have.
|
||||
|
||||
For more information, see <https://ripple.com/build/history-sharding/>
|
||||
_(Update: History sharding was removed in [version 2.3.0](/blog/2024/rippled-2.3.0.md).)_
|
||||
|
||||
### Preferred Ledger by Branch
|
||||
|
||||
@@ -127,7 +129,7 @@ Preferred Ledger by Branch improves how a `rippled` server decides which ledger
|
||||
Preferred Ledger by Branch leverages the ancestry information of branches to account for common support across validated ledgers and their ancestors, since a validation for some ledger is also a validation for all its ancestors. To find the preferred ledger, a `rippled` server starts at the most recent validated ledger and selects the child ledger with most support based on recent validations, but only selects it if an alternate sibling ledger does not possibly have more support. This process is then repeated starting from the newly chosen ledger until no better ledger exists. Preferred Ledger by Branch is designed to be conservative, only switching when the server sees enough peer validations to know another branch won't become preferred.
|
||||
|
||||
## Upcoming Features
|
||||
The [previously announced](https://developers.ripple.com/blog/2017/rippled-0.70.0.html) **FlowCross** Amendment will be enabled on a future date (TBA).
|
||||
The [previously announced](/blog/2017/rippled-0.70.0.md) **FlowCross** Amendment will be enabled on a future date (TBA).
|
||||
|
||||
Compiling `rippled` with scons is deprecated. Starting in rippled version 1.0, the only supported build will be using CMake.
|
||||
|
||||
|
||||
@@ -24,20 +24,22 @@ If you operate a `rippled` server but do not upgrade to version 0.90.1, your ser
|
||||
|
||||
### Upgrading
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see here: [Updating rippled](https://ripple.com/build/rippled-setup/#updating-rippled)
|
||||
For instructions on updating `rippled` on supported platforms, see here: [Updating rippled](/docs/infrastructure/installation/update-rippled-automatically-on-linux)
|
||||
|
||||
The SHA-256 for the rpm is: a22aff93d3de98ac3e1d775612e75e0e81aa7e6c18187db01efed485f854bab0
|
||||
The SHA-256 for the rpm is: `a22aff93d3de98ac3e1d775612e75e0e81aa7e6c18187db01efed485f854bab0`
|
||||
|
||||
The SHA-256 for the source rpm is: abaaaba2039c8cd93218fd6a23c79b32bfb6eba92a465b7f9c0716b37fb45795
|
||||
The SHA-256 for the source rpm is: `abaaaba2039c8cd93218fd6a23c79b32bfb6eba92a465b7f9c0716b37fb45795`
|
||||
|
||||
For other platforms, please compile version 0.90.1 from source. See [rippled Builds](https://github.com/ripple/rippled/tree/master/Builds) for instructions by platform. For instructions building `rippled` from source on Ubuntu Linux, see [Build and Run `rippled` on Ubuntu](https://ripple.com/build/build-run-rippled-ubuntu/).
|
||||
For other platforms, please [build version 0.90.1 from source](https://github.com/XRPLF/rippled/tree/0.90.1/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 067dbf299c297a8361e83e2ceaf7b0822ff9a3f5
|
||||
Author: Nikolaos D. Bougalis <nikb@bougalis.net>
|
||||
Date: Tue Mar 6 16:38:02 2018 -0800
|
||||
Set version to 0.90.1
|
||||
```
|
||||
|
||||
## Network Update
|
||||
|
||||
@@ -61,13 +63,13 @@ Other compatible versions differ by platform. Boost 1.58.0 is compatible on Linu
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
|
||||
* The Ripple Dev Blog: <https://developers.ripple.com/blog/>
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
|
||||
@@ -77,7 +79,7 @@ Other resources:
|
||||
|
||||
The previously announced DepositAuth, Checks and fix1513 amendments are now open for voting on the XRP Ledger. The DepositAuth Amendment lets an account strictly reject any incoming money from transactions sent by other accounts. The Checks Amendment allows users to create a deferred payment that can be cancelled or cashed by its intended recipient. The fix1513 amendment fixes a minor bug in rounding calculations. Ripple expects the **DepositAuth**, **Checks**, and **fix1513** amendments to be enabled on Thursday, 2018-04-05.
|
||||
|
||||
The [previously announced](https://developers.ripple.com/blog/2017/rippled-0.70.0.html) **FlowCross** Amendment will be enabled on a future date (TBA).
|
||||
The [previously announced](/blog/2017/rippled-0.70.0.md) **FlowCross** Amendment will be enabled on a future date (TBA).
|
||||
|
||||
Compiling `rippled` with scons is deprecated. Starting in `rippled` version 1.0, the only supported build will be using CMake.
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ Ripple recommends that all server operators upgrade to `rippled` v1.0.0 by Thurs
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
* **If you operate a `rippled` server**, but do not upgrade to version 1.0.0 by Thursday, 2018-06-14--when **[fix1543](https://developers.ripple.com/known-amendments.html#fix1543)**, **[fix1571](https://developers.ripple.com/known-amendments.html#fix1571)** and **[fix1623](https://developers.ripple.com/known-amendments.html#fix1623)** are expected to be enabled via Amendment——then your `rippled` server will become amendment blocked. A server that is amendment blocked:
|
||||
* **If you operate a `rippled` server**, but do not upgrade to version 1.0.0 by Thursday, 2018-06-14--when **[fix1543](/resources/known-amendments.md#fix1543)**, **[fix1571](/resources/known-amendments.md#fix1571)** and **[fix1623](/resources/known-amendments.md#fix1623)** are expected to be enabled via Amendment——then your `rippled` server will become amendment blocked. A server that is amendment blocked:
|
||||
|
||||
|
||||
* Cannot determine the validity of a ledger
|
||||
@@ -35,21 +35,22 @@ If the **fix1543**, **fix1571** and **fix1623** Amendments are not enabled, then
|
||||
|
||||
## Upgrading
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled`](https://developers.ripple.com/update-rippled.html).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled`](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The SHA-256 for the RPM is: `100376fbbfdf540264097c333a76b562c742fa5800c65f3c555d16347e23cda3`
|
||||
|
||||
The SHA-256 for the source RPM is: `10f472979785db537c4d28bc5a9c71c642cfeac306557368e588d72797439eda`
|
||||
|
||||
For other platforms, please compile v1.0.0 from source. See the [`rippled` source tree](https://github.com/ripple/rippled/tree/develop/Builds) for instructions by platform. For instructions building `rippled` from source on Ubuntu Linux, see [Install `rippled` on Ubuntu](https://developers.ripple.com/install-rippled.html#installation-on-ubuntu-with-alien).
|
||||
For other platforms, please [compile v1.0.0 from source](https://github.com/XRPLF/rippled/tree/1.0.0/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit f31ca2860fb5f045b618aa05d1e76c7e2e9494ec
|
||||
Author: Nikolaos D. Bougalis <nikb@bougalis.net>
|
||||
Date: Fri May 11 10:29:41 2018 -0700
|
||||
Set version to 1.0.0
|
||||
|
||||
```
|
||||
|
||||
## Network Update
|
||||
|
||||
@@ -58,14 +59,14 @@ The Ripple technical operations team has deployed version 1.0.0 to all `rippled`
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
Related documentation is available in the [XRP Ledger Developer Portal](https://developers.ripple.com/index.html), including detailed reference information, tutorials, and web tools.
|
||||
Related documentation is available in the XRP Ledger Developer Portal, including detailed reference information, tutorials, and web tools.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
## Other Information
|
||||
|
||||
@@ -115,19 +116,19 @@ For compatibility with other Boost versions, see the following table.
|
||||
|
||||
The **XRP Ledger** is a public decentralized cryptographic ledger powered by a global network of peer-to-peer servers. The XRP Ledger is the root ledger of XRP, a digital asset designed to bridge global currencies for payments. As a software company, Ripple contributes to the open source development of the XRP Ledger, in support of the Internet of Value: a world in which money moves the way information does today.
|
||||
|
||||
For more information, see [XRP Ledger Overview](https://developers.ripple.com/xrp-ledger-overview.html).
|
||||
For more information, see [XRP Ledger Overview](/docs/introduction/what-is-the-xrp-ledger).
|
||||
|
||||
#### Consensus
|
||||
|
||||
Among the key benefits of the XRP Ledger is a fast and efficient consensus algorithm, which can settle transactions in 4 to 5 seconds, while processing at a throughput of up to 1,500 transactions per second.
|
||||
|
||||
The consensus algorithm is [censorship-resistant](https://developers.ripple.com/xrp-ledger-overview.html#censorship-resistant-transaction-processing). Because no single party decides which transactions succeed or fail, no one can "roll back" a transaction after it completes and no one has control over the consensus algorithm. Instead, individual server operators can select a list of validators that they choose to trust not to collude in an attempt to defraud the rest of the network.
|
||||
The consensus algorithm is censorship-resistant. Because no single party decides which transactions succeed or fail, no one can "roll back" a transaction after it completes and no one has control over the consensus algorithm. Instead, individual server operators can select a list of validators that they choose to trust not to collude in an attempt to defraud the rest of the network.
|
||||
|
||||
For more information on how the XRP Ledger's consensus algorithm works, see [Consensus](https://developers.ripple.com/consensus.html). For background on why the XRP Ledger uses this consensus algorithm, see [Consensus Principles and Rules](https://developers.ripple.com/consensus-principles-and-rules.html).
|
||||
For more information on how the XRP Ledger's consensus algorithm works, see [Consensus](/docs/concepts/consensus-protocol). For background on why the XRP Ledger uses this consensus algorithm, see [Consensus Principles and Rules](/docs/concepts/consensus-protocol/consensus-principles-and-rules).
|
||||
|
||||
#### Protocol Amendments
|
||||
|
||||
The XRP Ledger has integrated support for [amendments](https://developers.ripple.com/amendments.html), which allow for the introduction of new features to the decentralized XRP Ledger network without causing disruptions. Amendments work by utilizing the core consensus process of the network to approve any changes by showing continuous support before those changes go into effect.
|
||||
The XRP Ledger has integrated support for [amendments](/docs/concepts/networks-and-servers/amendments), which allow for the introduction of new features to the decentralized XRP Ledger network without causing disruptions. Amendments work by utilizing the core consensus process of the network to approve any changes by showing continuous support before those changes go into effect.
|
||||
|
||||
#### Cryptography
|
||||
|
||||
@@ -135,31 +136,30 @@ The XRP Ledger relies on industry-standard digital signature systems like ECDSA
|
||||
|
||||
For more information, see:
|
||||
|
||||
* [Cryptographic Keys](https://developers.ripple.com/cryptographic-keys.html)
|
||||
* [Multi-signing](https://developers.ripple.com/multi-signing.html)
|
||||
* [Cryptographic Keys](/docs/concepts/accounts/cryptographic-keys)
|
||||
* [Multi-signing](/docs/concepts/accounts/multi-signing)
|
||||
|
||||
#### Advanced Features
|
||||
|
||||
In addition to multi-signing, the XRP Ledger supports other advanced features, such as:
|
||||
|
||||
* [Escrow](https://developers.ripple.com/escrow.html)
|
||||
* [Checks](https://developers.ripple.com/checks.html)
|
||||
* [Deposit Authorization](https://developers.ripple.com/depositauth.html)
|
||||
* [Payment Channels](https://developers.ripple.com/payment-channels.html)
|
||||
* [Escrow]/docs/concepts/payment-types/escrow)
|
||||
* [Checks](/docs/concepts/payment-types/checks)
|
||||
* [Deposit Authorization](/docs/concepts/accounts/depositauth)
|
||||
* [Payment Channels](/docs/concepts/payment-types/payment-channels)
|
||||
* [Crypto-Conditions](https://tools.ietf.org/html/draft-thomas-crypto-conditions-04)
|
||||
|
||||
These features make it possible to implement cutting-edge financial applications or interact with the [Interledger Protocol](https://interledger.org/). This toolbox of advanced features comes with a wide range safety checks that validate all transactions against a list of invariant constraints.
|
||||
|
||||
#### Decentralized Exchange
|
||||
|
||||
The XRP Ledger also has a fully-functional accounting system for publicly tracking and trading obligations denominated in any way users want, along with a decentralized exchange built into the ledger. The XRP Ledger can settle long, cross-currency [payment paths](https://developers.ripple.com/paths.html) and [exchanges](https://developers.ripple.com/decentralized-exchange.html) of multiple currencies in atomic transactions, bridging gaps of trust with XRP.
|
||||
The XRP Ledger also has a fully-functional accounting system for publicly tracking and trading obligations denominated in any way users want, along with a decentralized exchange built into the ledger. The XRP Ledger can settle long, cross-currency [payment paths](/docs/concepts/tokens/fungible-tokens/paths) and exchanges of multiple currencies in atomic transactions, bridging gaps of trust with XRP.
|
||||
|
||||
For more information on how the decentralized exchange works, see:
|
||||
|
||||
* [On-Ledger Decentralized Exchange](https://developers.ripple.com/xrp-ledger-overview.html#on-ledger-decentralized-exchange)
|
||||
* [Decentralized Exchange](https://developers.ripple.com/decentralized-exchange.html)
|
||||
* [Offers](https://developers.ripple.com/offers.html)
|
||||
* [Become an XRP Ledger Gateway](https://developers.ripple.com/become-an-xrp-ledger-gateway.html)
|
||||
* [Decentralized Exchange](/docs/concepts/tokens/decentralized-exchange)
|
||||
* [Offers](/docs/concepts/tokens/decentralized-exchange/offers)
|
||||
* [Stablecoin Issuer](/docs/use-cases/tokenization/stablecoin-issuer)
|
||||
|
||||
#### Acknowledgements
|
||||
|
||||
|
||||
@@ -24,21 +24,23 @@ While these issues can result in a denial of service attack, none affect the int
|
||||
|
||||
## Upgrading
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled`](https://developers.ripple.com/update-rippled.html).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled`](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The SHA-256 for the RPM is: `4bfa27b0e1e1979f2bc042edb9dd11ae4119dac6be087813dadcc67572877189`
|
||||
|
||||
The SHA-256 for the source RPM is: `60279abc65476b0a96ddedcd23338ce1c6fb5481ab94fe8b8c856448044e3ebe`
|
||||
|
||||
For other platforms, please compile v1.0.1 from source. See the [`rippled` source tree](https://github.com/ripple/rippled/tree/develop/Builds) for instructions by platform. For instructions building `rippled` from source on Ubuntu Linux, see [Install `rippled` on Ubuntu](https://developers.ripple.com/install-rippled.html#installation-on-ubuntu-with-alien).
|
||||
For other platforms, please [compile v1.0.1 from source](https://github.com/XRPLF/rippled/tree/1.0.1/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 8429dd67e60ba360da591bfa905b58a35638fda1
|
||||
Author: Nik Bougalis <nikb@bougalis.net>
|
||||
Date: Mon Jun 4 16:36:22 2018 -0700
|
||||
|
||||
Set version to 1.0.1
|
||||
```
|
||||
|
||||
## Network Update
|
||||
|
||||
@@ -62,19 +64,19 @@ Other compatible versions differ by platform. Boost 1.58.0 is compatible on Linu
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
Related documentation is available in the [XRP Ledger Developer Portal](https://developers.ripple.com/index.html), including detailed reference information, tutorials, and web tools.
|
||||
Related documentation is available in the [XRP Ledger Developer Portal](/docs/), including detailed reference information, tutorials, and web tools.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
|
||||
## Upcoming Features
|
||||
|
||||
The previously [introduced](https://developers.ripple.com/blog/2018/rippled-1.0.0.html) [fix1543](https://developers.ripple.com/known-amendments.html#fix1543), [fix1571](https://developers.ripple.com/known-amendments.html#fix1571) and [fix1623](https://developers.ripple.com/known-amendments.html#fix1623) Amendments in XRP Ledger version 1.0.0 are now open for voting. Ripple expects these amendments to become enabled on Tuesday, 2018-06-19.
|
||||
The previously [introduced](/blog/2018/rippled-1.0.0.md) [fix1543](/resources/known-amendments.md#fix1543), [fix1571](/resources/known-amendments.md#fix1571) and [fix1623](/resources/known-amendments.md#fix1623) Amendments in XRP Ledger version 1.0.0 are now open for voting. Ripple expects these amendments to become enabled on Tuesday, 2018-06-19.
|
||||
|
||||
An upcoming version of `rippled` will switch to using the **Boost.Beast** library instead of the **Beast** library from the `rippled` source code. As part of this change, the minimum supported version of Boost will change to be a version incorporating Boost.Beast.
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ markdown:
|
||||
|
||||
Ripple is pleased to announce the release of **XRP Ledger (`rippled`) version 1.1.0.**
|
||||
|
||||
The XRP Ledger version 1.1.0 release includes the [DepositPreAuth](https://developers.ripple.com/known-amendments.html#depositpreauth) Amendment, which, combined with the previously released [DepositAuth](https://developers.ripple.com/known-amendments.html#depositauth) Amendment, allows users to pre-authorize incoming transactions to accounts, by whitelisting sender addresses. XRP Ledger version 1.1.0 release also includes incremental improvements to several previously released features ([fix1515](https://developers.ripple.com/known-amendments.html#fix1515) Amendment), deprecates support for the sign and sign_for commands from the rippled API and improves invariant checking for enhanced security.
|
||||
The XRP Ledger version 1.1.0 release includes the [DepositPreAuth](/resources/known-amendments.md#depositpreauth) Amendment, which, combined with the previously released [DepositAuth](/resources/known-amendments.md#depositauth) Amendment, allows users to pre-authorize incoming transactions to accounts, by whitelisting sender addresses. XRP Ledger version 1.1.0 release also includes incremental improvements to several previously released features ([fix1515](/resources/known-amendments.md#fix1515) Amendment), deprecates support for the sign and sign_for commands from the rippled API and improves invariant checking for enhanced security.
|
||||
|
||||
Ripple recommends that all server operators upgrade to XRP Ledger version 1.1.0 by Thursday, 2018-09-27, to ensure service continuity.
|
||||
|
||||
@@ -22,7 +22,7 @@ Ripple recommends that all server operators upgrade to XRP Ledger version 1.1.0
|
||||
|
||||
### Impact of Not Upgrading
|
||||
|
||||
Ripple expects the **DepositPreAuth** or **fix1515** amendments to become enabled on or after Thursday, 2018-09-27. When this happens, if you are not running release 1.1.0 or greater, your server will become [amendment blocked](https://ripple.com/build/amendments/#amendment-blocked), meaning that it:
|
||||
Ripple expects the **DepositPreAuth** or **fix1515** amendments to become enabled on or after Thursday, 2018-09-27. When this happens, if you are not running release 1.1.0 or greater, your server will become [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that it:
|
||||
|
||||
* Cannot determine the validity of a ledger;
|
||||
|
||||
@@ -38,21 +38,23 @@ If the **DepositPreAuth** and **fix1515** Amendments do not become enabled, then
|
||||
|
||||
### Upgrading
|
||||
|
||||
For instructions on updating the XRP Ledger server on supported platforms, see here: [Updating `rippled` on Supported Platforms](https://developers.ripple.com/update-rippled.html).
|
||||
For instructions on updating the XRP Ledger server on supported platforms, see here: [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
- The SHA-256 for the RPM is: `ec50f3cec7dcbea8aaa2eb9d97c3c1fc02d44ce62203557b4cd213cf1b0fe4b5`
|
||||
|
||||
- The SHA-256 for the source RPM is: `936844990e70615183681c41884ea96804ee4130d6f9ec32242fb3a16120824f`
|
||||
|
||||
For other platforms, please compile version 1.1.0 from source. See [`rippled` build instructions by platform](https://github.com/ripple/rippled/tree/master/Builds), or [Build and Run `rippled` on Ubuntu Linux](https://ripple.com/build/build-run-rippled-ubuntu/) for further instructions.
|
||||
For other platforms, please [compile version 1.1.0 from source](https://github.com/XRPLF/rippled/tree/1.1.0/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 3e22a1e9e8f2de450eded6ca4c2db6411e329b2a
|
||||
Author: Nik Bougalis <nikb@bougalis.net>
|
||||
Date: Wed Sep 5 18:34:43 2018 -0700
|
||||
|
||||
Set version to 1.1.0
|
||||
```
|
||||
|
||||
## Network Update
|
||||
|
||||
@@ -60,12 +62,12 @@ The Ripple technical operations has deployed version 1.1.0 to all XRP Ledger ser
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
Related documentation is available in the XRP Ledger Dev Portal, including detailed example API calls and web tools for API testing: [https://developers.ripple.com/](https://developers.ripple.com/)
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](/docs/), including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* The Ripple Dev Blog: <https://developers.ripple.com/blog/>
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* XRP Chat: <http://www.xrpchat.com/>
|
||||
|
||||
@@ -117,7 +119,7 @@ When compiling XRP Ledger from source, you must use a compatible version of the
|
||||
|
||||
* Deprecate the ‘sign’ and ‘sign_for’ APIs ([#2657](https://github.com/ripple/rippled/pull/2657))
|
||||
|
||||
* Use liquidity from strands that consume too many offers, which will be enabled on [fix1515](https://developers.ripple.com/known-amendments.html#fix1515) Amendment ([#2546](https://github.com/ripple/rippled/pull/2546))
|
||||
* Use liquidity from strands that consume too many offers, which will be enabled on [fix1515](/resources/known-amendments.md#fix1515) Amendment ([#2546](https://github.com/ripple/rippled/pull/2546))
|
||||
|
||||
* Fix a corner case when decoding base64 ([#2605](https://github.com/ripple/rippled/pull/2605/commits/0439dcfa7a5215cc74a8e254a28eadace6a524b7))
|
||||
|
||||
|
||||
@@ -22,13 +22,13 @@ Ripple has released `rippled` version 1.1.1, which improves handling of validato
|
||||
|
||||
## Upgrading
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled`](https://developers.ripple.com/update-rippled.html).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled`](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The SHA-256 for the RPM is: `a833fbaf988d85c985f80ad4dfd46a391cce7e884fba62b2f9b1b87aa41c3cfa`
|
||||
|
||||
The SHA-256 for the source RPM is: `a88b538fc3ee0bb5cefe3e96622faebecebcc91e5c530f74283d49c9cfff41d4`
|
||||
|
||||
For other platforms, please compile v1.1.1 from source. See the [`rippled` source tree](https://github.com/ripple/rippled/tree/develop/Builds) for instructions by platform. For instructions building `rippled` from source on Ubuntu Linux, see [Install `rippled` on Ubuntu](https://developers.ripple.com/install-rippled.html#installation-on-ubuntu-with-alien).
|
||||
For other platforms, please [compile v1.1.1 from source](https://github.com/XRPLF/rippled/tree/1.1.1/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
@@ -54,14 +54,14 @@ When compiling `rippled` from source, you must use a compatible version of the B
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
Related documentation is available in the [XRP Ledger Developer Portal](https://developers.ripple.com/), including detailed reference information, tutorials, and web tools.
|
||||
Related documentation is available in the [XRP Ledger Developer Portal](/docs/), including detailed reference information, tutorials, and web tools.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
|
||||
|
||||
@@ -74,4 +74,4 @@ Other resources:
|
||||
- Improve behavior of `rippled` servers when their latest available validator list is past its expiration (RIPD-1661):
|
||||
- Report the problem with an ERROR-level log message.
|
||||
- Stop sending validation messages for new ledgers until a non-expired validator list is available.
|
||||
- Report the validator list as `expired` in the [server_info method](https://developers.ripple.com/server_info.html) and [server_state method](https://developers.ripple.com/server_state.html).
|
||||
- Report the validator list as `expired` in the [server_info method](/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info) and [server_state method](/docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_state).
|
||||
|
||||
@@ -26,17 +26,13 @@ If you are not running release 1.1.2 or greater, then your validator server can
|
||||
|
||||
### Upgrading
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Installing rippled](https://developers.ripple.com/install-rippled.html).
|
||||
For instructions on updating `rippled` on supported platforms, see [Installation](/docs/infrastructure/installation).
|
||||
|
||||
The SHA-256 for the RPM is: `989a679bef72e827f204b394abd3d385f1baae6ad7a94eaf9b759a032bcd0f7e`
|
||||
|
||||
The SHA-256 for the source RPM is: `091b60dcf38aea4f9ec252d7b1b72d95ca4f45b3a831fbe97ce8f806f2907cae`
|
||||
|
||||
For other platforms, please compile version 1.1.2 from source.
|
||||
|
||||
- [Build and Run `rippled` on Ubuntu Linux](https://developers.ripple.com/build-run-rippled-ubuntu.html)
|
||||
- [Build and run `rippled` on macOS](https://developers.ripple.com/build-run-rippled-macos.html)
|
||||
- See <https://github.com/ripple/rippled/tree/master/Builds> for instructions by platform.
|
||||
For other platforms, please [compile version 1.1.2 from source](https://github.com/XRPLF/rippled/tree/1.1.2/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
@@ -53,7 +49,7 @@ Ripple plans to deploy version 1.1.2 to all XRP Ledger servers under its operati
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](https://developers.ripple.com/), including detailed example API calls and web tools for API testing: <https://developers.ripple.com/>
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](/docs/), including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ Ripple recommends that you:
|
||||
|
||||
* Add a `[validators_file]` section if one is not present, and add the name of your `validators.txt` file.
|
||||
|
||||
* Replace the contents of any existing `validators.txt` file with the [version included with this release](https://github.com/ripple/rippled/blob/4e8c8deeaac83d18eb62c95b7425d96e11847a41/doc/validators-example.txt#L51-L55). If you are upgrading to `rippled` version 0.81.0 [using the `rippled` RPM package](https://ripple.com/build/rippled-setup/#updating-rippled), then your default `validators.txt` file may automatically be updated, in which case you will not need to modify the file. The `validators.txt` file is usually in the same directory as your `rippled.cfg` file.
|
||||
* Replace the contents of any existing `validators.txt` file with the [version included with this release](https://github.com/ripple/rippled/blob/4e8c8deeaac83d18eb62c95b7425d96e11847a41/doc/validators-example.txt#L51-L55). If you are upgrading to `rippled` version 0.81.0 [using the `rippled` RPM package](/docs/infrastructure/installation/update-rippled-automatically-on-linux), then your default `validators.txt` file may automatically be updated, in which case you will not need to modify the file. The `validators.txt` file is usually in the same directory as your `rippled.cfg` file.
|
||||
|
||||
* After starting your `rippled` server, confirm that it is configured to use the new defaults by executing:
|
||||
|
||||
@@ -60,13 +60,13 @@ The result should include the following:
|
||||
|
||||
* On Wednesday, January 17, 2018, as described in the 0.81.0 release notes, the current validator keys on all five Ripple-operated `rippled` validator servers will be replaced. **If you have been using the recommended default configuration **and do not reconfigure your `rippled` server before that time, then your `rippled` server will stop seeing validated ledgers.
|
||||
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](https://ripple.com/build/rippled-setup/#updating-rippled).
|
||||
For instructions on updating `rippled` on supported platforms, see [Updating `rippled` on supported platforms](/docs/infrastructure/installation/update-rippled-automatically-on-linux).
|
||||
|
||||
The sha256 for the RPM is: 75acdf54e472875bff609fa2d1cc59524e4d8f8e885751b50aaeb85938ab3609
|
||||
|
||||
The sha256 for the source RPM is: fbc95f6168d015190b93b81f97c20979886fa2f6663e4dd15157409075db46e9
|
||||
|
||||
For other platforms, please [compile version 0.81.0 from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
For other platforms, please [compile version 0.81.0 from source](https://github.com/XRPLF/rippled/tree/0.81.0/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
@@ -93,14 +93,14 @@ The Ripple technical operations team deployed `rippled` version 0.81.0 to all `r
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
Related documentation is available in the [Ripple Developer Portal](https://ripple.com/build/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
|
||||
* [XRP Chat](http://www.xrpchat.com/)
|
||||
* XRP Chat _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
@@ -11,13 +11,10 @@ markdown:
|
||||
---
|
||||
# Corrections to Data API / XRP Charts Metrics for 2019-03-23
|
||||
|
||||
The [Data API][], an open API that provides data to [XRP Charts][] and third-party tools, suffered gaps in data ingestion on 2019-03-23. As a result, several [metrics on XRP Charts](https://xrpcharts.ripple.com/#/metrics), including the number of ledgers closed per day, were overcounted. **During this time, the XRP Ledger did not experience any outages.** However, the Data API's ingestion service was unable to process ledgers with transactions containing the `tecKILLED` transaction response code. `tecKILLED` is a new response code added to the XRP Ledger by amendment [fix1578](https://developers.ripple.com/known-amendments.html#fix1578) on 2019-03-23. This necessitated changes to the [ripple-binary-codec library](https://github.com/ripple/ripple-binary-codec) used by the ingestion service, but [those changes](https://github.com/ripple/ripple-binary-codec/pull/27) were only partially deployed to the ingestion service. We have since reprocessed and corrected the metrics that were affected by this problem.
|
||||
|
||||
[Data API]: https://developers.ripple.com/data-api.html
|
||||
[XRP Charts]: https://xrpcharts.ripple.com/
|
||||
The Data API, an open API that provides data to XRP Charts and third-party tools, suffered gaps in data ingestion on 2019-03-23. As a result, several metrics on XRP Charts, including the number of ledgers closed per day, were overcounted. **During this time, the XRP Ledger did not experience any outages.** However, the Data API's ingestion service was unable to process ledgers with transactions containing the `tecKILLED` transaction response code. `tecKILLED` is a new response code added to the XRP Ledger by amendment [fix1578](/resources/known-amendments.md#fix1578) on 2019-03-23. This necessitated changes to the [ripple-binary-codec library](https://github.com/ripple/ripple-binary-codec) used by the ingestion service, but [those changes](https://github.com/ripple/ripple-binary-codec/pull/27) were only partially deployed to the ingestion service. We have since reprocessed and corrected the metrics that were affected by this problem.
|
||||
|
||||
<!-- BREAK -->
|
||||
|
||||
The [Data API][] and [XRP Charts][] are public services that Ripple supports but they are not intended for large-scale production use. These services are also independent from the core XRP Ledger, which is a distributed system that is not operated by any one party.
|
||||
The Data API and XRP Charts are public services that Ripple supports but they are not intended for large-scale production use. These services are also independent from the core XRP Ledger, which is a distributed system that is not operated by any one party.
|
||||
|
||||
Although we will continue to improve our tools going forward, it is important to note that Ripple is one participant in the broader XRP Ledger ecosystem and we are excited to see the amazing tools and services that independent developers are building on the XRP Ledger.
|
||||
|
||||
@@ -10,13 +10,13 @@ markdown:
|
||||
---
|
||||
# fix1578 is Now Available
|
||||
|
||||
[As previously announced](https://developers.ripple.com/blog/2019/fix1578-expected.html), the fix1578 amendment [became enabled on the XRP Ledger](https://xrpcharts.ripple.com/#/transactions/7A80C87F59BCE6973CBDCA91E4DBDB0FC5461D3599A8BC8EAD02FA590A50005D) on 2019-03-23.
|
||||
[As previously announced](/blog/2019/fix1578-expected.md), the fix1578 amendment [became enabled on the XRP Ledger](https://xrpcharts.ripple.com/#/transactions/7A80C87F59BCE6973CBDCA91E4DBDB0FC5461D3599A8BC8EAD02FA590A50005D) on 2019-03-23.
|
||||
|
||||
## Action Required
|
||||
|
||||
- If you operate a `rippled` server, you should upgrade to version 1.2.0 (or higher) immediately. Version 1.2.2 is recommended.
|
||||
|
||||
For instructions on upgrading `rippled` on supported platforms, see [Install `rippled`](https://developers.ripple.com/install-rippled.html).
|
||||
For instructions on upgrading `rippled` on supported platforms, see [Install `rippled`](/docs/infrastructure/installation).
|
||||
|
||||
|
||||
## Impact of Not Upgrading
|
||||
@@ -33,15 +33,15 @@ If you operate a `rippled` server on a version older than 1.2.0, then your serve
|
||||
|
||||
Changes the result codes returned by two transaction types:
|
||||
|
||||
- Changes the [OfferCreate transaction](https://developers.ripple.com/offercreate.html) to return a new result code, `tecKILLED`, if the offer used the `tfFillOrKill` flag and was killed. Without this amendment, the offer is killed but the transaction result is `tesSUCCESS`.
|
||||
- Changes the [TrustSet transaction](https://developers.ripple.com/trustset.html) to fail with `tecNO_PERMISSION` if it tries to enable the [NoRipple flag](https://developers.ripple.com/rippling.html#the-noripple-flag) but cannot because the trust line has a negative balance. Without this amendment, the transaction does not enable the NoRipple flag, but the transaction result is `tesSUCCESS` nonetheless.
|
||||
- Changes the [OfferCreate transaction](/docs/references/protocol/transactions/types/offercreate.md) to return a new result code, `tecKILLED`, if the offer used the `tfFillOrKill` flag and was killed. Without this amendment, the offer is killed but the transaction result is `tesSUCCESS`.
|
||||
- Changes the [TrustSet transaction](/docs/references/protocol/transactions/types/trustset.md) to fail with `tecNO_PERMISSION` if it tries to enable the [NoRipple flag](/docs/concepts/tokens/fungible-tokens/rippling#the-no-ripple-flag) but cannot because the trust line has a negative balance. Without this amendment, the transaction does not enable the NoRipple flag, but the transaction result is `tesSUCCESS` nonetheless.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](https://developers.ripple.com/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](/docs/), including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat Forum](http://www.xrpchat.com/)
|
||||
|
||||
@@ -22,15 +22,15 @@ As long as the amendments continue to have the support of at least 80% of truste
|
||||
|
||||
Changes the result codes returned by two transaction types:
|
||||
|
||||
- Changes the [OfferCreate transaction](https://developers.ripple.com/offercreate.html) to return a new result code, `tecKILLED`, if the offer used the `tfFillOrKill` flag and was killed. Without this amendment, the offer is killed but the transaction result is `tesSUCCESS`.
|
||||
- Changes the [TrustSet transaction](https://developers.ripple.com/trustset.html) to fail with `tecNO_PERMISSION` if it tries to enable the [NoRipple flag](https://developers.ripple.com/rippling.html#the-noripple-flag) but cannot because the trust line has a negative balance. Without this amendment, the transaction does not enable the NoRipple flag, but the transaction result is `tesSUCCESS` nonetheless.
|
||||
- Changes the [OfferCreate transaction](/docs/references/protocol/transactions/types/offercreate.md) to return a new result code, `tecKILLED`, if the offer used the `tfFillOrKill` flag and was killed. Without this amendment, the offer is killed but the transaction result is `tesSUCCESS`.
|
||||
- Changes the [TrustSet transaction](/docs/references/protocol/transactions/types/trustset.md) to fail with `tecNO_PERMISSION` if it tries to enable the [NoRipple flag](/docs/concepts/tokens/fungible-tokens/rippling#the-no-ripple-flag) but cannot because the trust line has a negative balance. Without this amendment, the transaction does not enable the NoRipple flag, but the transaction result is `tesSUCCESS` nonetheless.
|
||||
|
||||
|
||||
## fixTakerDryOfferRemoval Summary
|
||||
|
||||
Fixes a bug in [auto-bridging](https://developers.ripple.com/autobridging.html) that can leave a dry offer in the XRP Ledger. A dry offer is an offer that, if crossed, cannot yield any funds.
|
||||
Fixes a bug in [auto-bridging](/docs/concepts/tokens/decentralized-exchange/autobridging) that can leave a dry offer in the XRP Ledger. A dry offer is an offer that, if crossed, cannot yield any funds.
|
||||
|
||||
Without this fix, the dry offer remains on the ledger and counts toward its owner's [reserve requirement](https://developers.ripple.com/reserves.html#owner-reserves) without providing any benefit to the owner. Another offer crossing of the right type and quality can remove the dry offer. However, if the required offer crossing type and quality are rare, it may take a while for the dry offer to be removed.
|
||||
Without this fix, the dry offer remains on the ledger and counts toward its owner's [reserve requirement](/docs/concepts/accounts/reserves#owner-reserves) without providing any benefit to the owner. Another offer crossing of the right type and quality can remove the dry offer. However, if the required offer crossing type and quality are rare, it may take a while for the dry offer to be removed.
|
||||
|
||||
With this amendment enabled, the XRP Ledger removes these dry offers when they're matched in auto-bridging.
|
||||
|
||||
@@ -53,13 +53,13 @@ If you operate a `rippled` server but don’t upgrade to version 1.2.0 (or highe
|
||||
|
||||
If the fix1578 amendment does not become enabled, then your server will not become amendment blocked until the fixTakerDryOfferRemoval amendment becomes enabled on 2019-04-02. If neither amendment becomes enabled, older server versions should continue to operate without becoming amendment blocked. However, it is still recommended that you update to [`rippled` version 1.2.2](https://github.com/ripple/rippled/releases/tag/1.2.2) or higher.
|
||||
|
||||
For instructions on upgrading `rippled` on supported platforms, see [Install `rippled`](https://developers.ripple.com/install-rippled.html).
|
||||
For instructions on upgrading `rippled` on supported platforms, see [Install `rippled`](/docs/infrastructure/installation).
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](https://developers.ripple.com/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](/docs/), including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat Forum](http://www.xrpchat.com/)
|
||||
|
||||
@@ -14,14 +14,14 @@ markdown:
|
||||
|
||||
## Action Required
|
||||
|
||||
- If you operate a `rippled` server, you should upgrade to version 1.2.0 (or higher) immediately. [Version 1.2.3](https://developers.ripple.com/blog/2019/rippled-1.2.3.html) is recommended.
|
||||
- If you operate a `rippled` server, you should upgrade to version 1.2.0 (or higher) immediately. [Version 1.2.3](/blog/2019/rippled-1.2.3.md) is recommended.
|
||||
|
||||
For instructions on upgrading `rippled` on supported platforms, see [Install `rippled`](https://developers.ripple.com/install-rippled.html).
|
||||
For instructions on upgrading `rippled` on supported platforms, see [Install `rippled`](/docs/infrastructure/installation).
|
||||
|
||||
|
||||
## Impact of Not Upgrading
|
||||
|
||||
If you operate a `rippled` server on a version older than 1.2.0, then your server has been [amendment blocked](https://developers.ripple.com/amendments.html#amendment-blocked) since 2019-03-23, when the [fix1578 amendment became enabled](https://developers.ripple.com/blog/2019/fix1578-enabled.html). If your server is amendment blocked, that means it:
|
||||
If you operate a `rippled` server on a version older than 1.2.0, then your server has been [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers) since 2019-03-23, when the [fix1578 amendment became enabled](/blog/2019/fix1578-enabled.md). If your server is amendment blocked, that means it:
|
||||
|
||||
* Cannot determine the validity of a ledger
|
||||
* Cannot submit or process transactions
|
||||
@@ -32,20 +32,20 @@ If you operate a `rippled` server on a version older than 1.2.0, then your serve
|
||||
|
||||
## fixTakerDryOfferRemoval Summary
|
||||
|
||||
Fixes a bug in [auto-bridging](http://developers.ripple.com/autobridging.html) that can leave a dry offer in the XRP Ledger. A dry offer is an offer that, if crossed, cannot yield any funds.
|
||||
Fixes a bug in [auto-bridging](/docs/concepts/tokens/decentralized-exchange/autobridging) that can leave a dry offer in the XRP Ledger. A dry offer is an offer that, if crossed, cannot yield any funds.
|
||||
|
||||
Without this fix, the dry offer remains on the ledger and counts toward its owner's [reserve requirement](http://developers.ripple.com/reserves.html#owner-reserves) without providing any benefit to the owner. Another offer crossing of the right type and quality can remove the dry offer. However, if the required offer crossing type and quality are rare, it may take a while for the dry offer to be removed.
|
||||
Without this fix, the dry offer remains on the ledger and counts toward its owner's [reserve requirement](/docs/concepts/accounts/reserves#owner-reserves) without providing any benefit to the owner. Another offer crossing of the right type and quality can remove the dry offer. However, if the required offer crossing type and quality are rare, it may take a while for the dry offer to be removed.
|
||||
|
||||
With this amendment enabled, the XRP Ledger removes these dry offers when they're matched in auto-bridging.
|
||||
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](https://developers.ripple.com/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](/docs/), including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
* [XRP Chat Forum](http://www.xrpchat.com/)
|
||||
|
||||
@@ -16,7 +16,7 @@ Here at Ripple, we've been eagerly following and contributing to the progress of
|
||||
|
||||
## Interledger is for Interoperability
|
||||
|
||||
First, some review for those who aren't familiar with Interledger: it's a protocol suite for enabling the Internet of Value. There's no Interledger coin or token, no chain of blocks with a shared set of state and balances, and no company or country who decides what you can do with it. The Interledger project is about taking a step away from the technological race of building [the best ledger](https://developers.ripple.com/xrp-ledger-overview.html), and instead bringing all ledgers together into a single interconnected network—creating an "Interledger" the same way that the Internet connected a bunch of individual networks into one massive "Internet".
|
||||
First, some review for those who aren't familiar with Interledger: it's a protocol suite for enabling the Internet of Value. There's no Interledger coin or token, no chain of blocks with a shared set of state and balances, and no company or country who decides what you can do with it. The Interledger project is about taking a step away from the technological race of building [the best ledger](/docs/introduction/what-is-the-xrp-ledger), and instead bringing all ledgers together into a single interconnected network—creating an "Interledger" the same way that the Internet connected a bunch of individual networks into one massive "Internet".
|
||||
|
||||
Ripple's own Evan Schwartz provides [a great intro to Interledger's key features and design choices](https://medium.com/xpring/interledger-how-to-interconnect-all-blockchains-and-value-networks-74f432e64543), and a more detailed look at [why Interledger is structured as a layered protocol suite](https://medium.com/xpring/layer-3-is-for-interoperability-ca387fa5f7e2).
|
||||
|
||||
@@ -26,7 +26,7 @@ When you build a blockchain-connected application or service, you get access to
|
||||
|
||||
### Production and Testnet
|
||||
|
||||
Right now, Interledger is being used in production by a small number of finance tech pioneers, including [Coil][], [Kava](https://kava.io/), [Strata](https://www.stratalabs.io/), and the [XRPTipBot](https://www.xrptipbot.com/). Thanks to these developers and the XRP Ledger's robust [payment channel](http://developers.ripple.com/payment-channels.html) functionality, it's easy to get started sending and receiving XRP through Interledger today.
|
||||
Right now, Interledger is being used in production by a small number of finance tech pioneers, including [Coil][], [Kava](https://kava.io/), [Strata](https://www.stratalabs.io/), and the [XRPTipBot](https://www.xrptipbot.com/). Thanks to these developers and the XRP Ledger's robust [payment channel](/docs/concepts/payment-types/payment-channels) functionality, it's easy to get started sending and receiving XRP through Interledger today.
|
||||
|
||||
If you're not ready to use real money yet, you can start by [building on the Interledger Testnet using the Moneyd server](https://medium.com/interledger-blog/using-moneyd-to-join-the-ilp-testnet-ba64bd42bb14). Moneyd provides a quick on-ramp as the "home router" of the Interledger, giving apps on your computer access to send and receive money. Although Moneyd can just as easily connect to the production Interledger, it is not currently designed for heavy production use, so it lacks features like budgeting that would let you give apps different spending limits and permissions levels.
|
||||
|
||||
|
||||
@@ -10,24 +10,24 @@ markdown:
|
||||
---
|
||||
# MultiSignReserve is Now Available
|
||||
|
||||
[As previously announced](https://developers.ripple.com/blog/2019/multisignreserve-expected.html), the MultiSignReserve amendment [became enabled on the XRP Ledger](https://xrpcharts.ripple.com/#/transactions/C421E1D08EFD78E6B8D06B085F52A34A681D0B51AE62A018527E1B8F54C108FB) on 2019-04-17.
|
||||
[As previously announced](/blog/2019/multisignreserve-expected.md), the MultiSignReserve amendment [became enabled on the XRP Ledger](https://xrpcharts.ripple.com/#/transactions/C421E1D08EFD78E6B8D06B085F52A34A681D0B51AE62A018527E1B8F54C108FB) on 2019-04-17.
|
||||
|
||||
## Action Recommended
|
||||
|
||||
If you are already using multi-signing, no changes are necessary to continue using it. Optionally, you can now benefit from the reduced reserve requirements by [replacing your existing SignerList](https://developers.ripple.com/set-up-multi-signing.html) with an identical or updated one.
|
||||
If you are already using multi-signing, no changes are necessary to continue using it. Optionally, you can now benefit from the reduced reserve requirements by replacing your existing SignerList with an identical or updated one.
|
||||
|
||||
If you are not using multi-signing yet, feel free to take this opportunity to [Set Up Multi-Signing](https://developers.ripple.com/set-up-multi-signing.html) with the reduced reserve requirements.
|
||||
If you are not using multi-signing yet, feel free to take this opportunity to [Set Up Multi-Signing](/docs/tutorials/how-tos/manage-account-settings/set-up-multi-signing) with the reduced reserve requirements.
|
||||
|
||||
|
||||
## MultiSignReserve Summary
|
||||
|
||||
Reduces the [owner reserve](https://developers.ripple.com/reserves.html#owner-reserves) to 5 XRP counted against your XRP Ledger account when it owns a [multi-signing](https://developers.ripple.com/multi-signing.html) SignerList, regardless of the number of signers. The reserve requirement for previously-created SignerList objects remains unchanged. To reduce the reserve requirement of SignerList objects created before this amendment was enabled, use a [SignerListSet transaction](https://developers.ripple.com/signerlistset.html) to replace the SignerList after this amendment has been enabled. (The replacement can be identical to the previous version.)
|
||||
Reduces the [owner reserve](/docs/concepts/accounts/reserves#owner-reserves) to 5 XRP counted against your XRP Ledger account when it owns a [multi-signing](/docs/concepts/accounts/multi-signing) SignerList, regardless of the number of signers. The reserve requirement for previously-created SignerList objects remains unchanged. To reduce the reserve requirement of SignerList objects created before this amendment was enabled, use a [SignerListSet transaction](/docs/references/protocol/transactions/types/signerlistset.md) to replace the SignerList after this amendment has been enabled. (The replacement can be identical to the previous version.)
|
||||
|
||||
Before this amendment, the owner reserve for a SignerList ranged from 15 to 50 XRP, depending on the number of signers in the list.
|
||||
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](https://developers.ripple.com/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](/docs/), including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
|
||||
@@ -14,21 +14,21 @@ The MultiSignReserve amendment to the XRP Ledger, introduced in [`rippled` v1.2.
|
||||
|
||||
## MultiSignReserve Summary
|
||||
|
||||
Reduces the [owner reserve](https://developers.ripple.com/reserves.html#owner-reserves) counted against your XRP Ledger account when it owns a [multi-signing](https://developers.ripple.com/multi-signing.html) SignerList.
|
||||
Reduces the [owner reserve](/docs/concepts/accounts/reserves#owner-reserves) counted against your XRP Ledger account when it owns a [multi-signing](/docs/concepts/accounts/multi-signing) SignerList.
|
||||
|
||||
Without this amendment, the owner reserve for a SignerList ranges from 15 to 50 XRP, depending on the number of signers in the list.
|
||||
|
||||
With this amendment enabled, the owner reserve for a new SignerList is 5 XRP, regardless of the number of signers. The reserve requirement for previously-created SignerList objects remains unchanged. To reduce the reserve requirement of SignerList objects created before this amendment was enabled, use a [SignerListSet transaction](https://developers.ripple.com/signerlistset.html) to replace the SignerList after this amendment has been enabled. (The replacement can be identical to the previous version.)
|
||||
With this amendment enabled, the owner reserve for a new SignerList is 5 XRP, regardless of the number of signers. The reserve requirement for previously-created SignerList objects remains unchanged. To reduce the reserve requirement of SignerList objects created before this amendment was enabled, use a [SignerListSet transaction](/docs/references/protocol/transactions/types/signerlistset.md) to replace the SignerList after this amendment has been enabled. (The replacement can be identical to the previous version.)
|
||||
|
||||
## No Action Required
|
||||
|
||||
The MultiSignReserve amendment is supported by `rippled` versions 1.2.0 and later, which have been required on the production XRP Ledger since [fix1578 became enabled](https://developers.ripple.com/blog/2019/fix1578-enabled.html) on 2019-03-23. [Version 1.2.3](https://developers.ripple.com/blog/2019/rippled-1.2.3.html) is recommended.
|
||||
The MultiSignReserve amendment is supported by `rippled` versions 1.2.0 and later, which have been required on the production XRP Ledger since [fix1578 became enabled](/blog/2019/fix1578-enabled.md) on 2019-03-23. [Version 1.2.3](/blog/2019/rippled-1.2.3.md) is recommended.
|
||||
|
||||
If you are already using multi-signing in production, no changes are necessary to continue to use multi-signing after this amendment becomes enabled. If the amendment becomes enabled, you can benefit from the lowered reserve requirement for your account's SignerList by updating or replacing the SignerList. (The replacement can be identical to the previous version.)
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](https://developers.ripple.com/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](/docs/), including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ markdown:
|
||||
|
||||
Ripple is pleased to announce the release of **XRP Ledger (`rippled`) version 1.2.0.**
|
||||
|
||||
The XRP Ledger version 1.2.0 release introduces the [MultisignReserve](https://developers.ripple.com/known-amendments.html#multisignreserve) Amendment, which reduces the reserve requirement associated with signer lists for [Multisign](https://developers.ripple.com/set-up-multi-signing.html). This release also includes incremental improvements to the code that handles offers in the decentralized exchange ([fixTakerDryOfferRemoval](https://developers.ripple.com/known-amendments.html#fixtakerdryofferremoval) and [fix1578](https://developers.ripple.com/known-amendments.html#fix1578) Amendments).
|
||||
The XRP Ledger version 1.2.0 release introduces the [MultisignReserve](/resources/known-amendments.md#multisignreserve) Amendment, which reduces the reserve requirement associated with signer lists for [Multi-signing](/docs/concepts/accounts/multi-signing). This release also includes incremental improvements to the code that handles offers in the decentralized exchange ([fixTakerDryOfferRemoval](/resources/known-amendments.md#fixtakerdryofferremoval) and [fix1578](/resources/known-amendments.md#fix1578) Amendments).
|
||||
|
||||
One of the major benefits of decentralized blockchain technologies, such as the XRP Ledger, is censorship resistance. Already highly resistant to censorship attempts, with the release of version 1.2.0 of the XRP Ledger, servers now have the ability to automatically detect transaction censorship attempts and issue warnings of increasing severity for transactions that a server believes should have been included in a closed ledger after several rounds of consensus.
|
||||
|
||||
@@ -24,7 +24,7 @@ One of the major benefits of decentralized blockchain technologies, such as the
|
||||
|
||||
### Impact of Not Upgrading
|
||||
|
||||
Ripple expects the **MultisignReserve**, **fixTakerDryOfferRemoval**, and **fix1578** amendments to become enabled no earlier than Wednesday, 2019-02-27. When this happens, if you are not running release 1.2.0 or greater, your server will become [amendment blocked](https://developers.ripple.com/amendments.html#amendment-blocked), meaning that it:
|
||||
Ripple expects the **MultisignReserve**, **fixTakerDryOfferRemoval**, and **fix1578** amendments to become enabled no earlier than Wednesday, 2019-02-27. When this happens, if you are not running release 1.2.0 or greater, your server will become [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that it:
|
||||
|
||||
* Cannot determine the validity of a ledger;
|
||||
|
||||
@@ -40,27 +40,23 @@ If the **MultisignReserve**, **fixTakerDryOfferRemoval**, and **fix1578** amendm
|
||||
|
||||
### Upgrading
|
||||
|
||||
On supported platforms, see the [instructions on updating `rippled`](https://developers.ripple.com/install-rippled.html).
|
||||
On supported platforms, see the [instructions on updating `rippled`](/docs/infrastructure/installation).
|
||||
|
||||
- The SHA-256 for the RPM is: `a6982002a5e7c3abb0078e9c986e4c28c8310ca67defa5f74a1b3581cc9bc0a4`
|
||||
|
||||
- The SHA-256 for the source RPM is: `1927e5411619cc66170730342f1a7c38f6eafae8c4246d68e24cc0ad4fd62b9e`
|
||||
|
||||
For other platforms, please compile version 1.2.0 from source.
|
||||
|
||||
* [Ubuntu Linux](https://developers.ripple.com/build-run-rippled-ubuntu.html)
|
||||
|
||||
* [macOS](https://developers.ripple.com/build-run-rippled-macos.html)
|
||||
|
||||
* [Other platforms](https://github.com/ripple/rippled/tree/master/Builds)
|
||||
For other platforms, please [compile version 1.2.0 from source](https://github.com/XRPLF/rippled/tree/1.2.0/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 7779dcdda00ea61a976cf5f387bc1f3bb4ebbfdd
|
||||
Author: Mike Ellery <mellery451@gmail.com>
|
||||
Date: Tue Feb 12 16:41:03 2019 -0800
|
||||
|
||||
Set version to 1.2.0
|
||||
```
|
||||
|
||||
## Network Update
|
||||
|
||||
@@ -68,7 +64,7 @@ The Ripple technical operations team plans to deploy version 1.2.0 to all XRP Le
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](https://developers.ripple.com/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](/docs/), including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@ Version 1.2.1 introduces several fixes including:
|
||||
|
||||
* A fix for a technical flaw that could cause a server to not properly detect that it had lost connectivity.
|
||||
|
||||
Version 1.2.1 also adds [the delivered_amount field](https://developers.ripple.com/partial-payments.html#the-delivered-amount-field) to more responses to simplify the handling of payment or check cashing transactions.
|
||||
Version 1.2.1 also adds [the delivered_amount field](/docs/concepts/payment-types/partial-payments#the-delivered_amount-field) to more responses to simplify the handling of payment or check cashing transactions.
|
||||
|
||||
<!-- BREAK -->
|
||||
|
||||
@@ -30,7 +30,7 @@ Version 1.2.1 also adds [the delivered_amount field](https://developers.ripple.c
|
||||
|
||||
### Impact of Not Upgrading
|
||||
|
||||
Ripple expects the **MultisignReserve**, **fixTakerDryOfferRemoval** and **fix1578** Amendments to become enabled no earlier than Tuesday, 2019-03-12. When this happens, if you are not running release 1.2.0 or greater, your server will become [amendment blocked](https://developers.ripple.com/amendments.html#amendment-blocked), meaning that it:
|
||||
Ripple expects the **MultisignReserve**, **fixTakerDryOfferRemoval** and **fix1578** Amendments to become enabled no earlier than Tuesday, 2019-03-12. When this happens, if you are not running release 1.2.0 or greater, your server will become [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that it:
|
||||
|
||||
* Cannot determine the validity of a ledger;
|
||||
|
||||
@@ -46,19 +46,13 @@ If the **MultisignReserve**, **fixTakerDryOfferRemoval **and** fix1578** Amendme
|
||||
|
||||
### Upgrading
|
||||
|
||||
For instructions on updating XRP Ledger on supported platforms, see here: <https://developers.ripple.com/install-rippled.html>.
|
||||
For instructions on updating XRP Ledger on supported platforms, see [Installation](/docs/infrastructure/installation).
|
||||
|
||||
The SHA-256 for the RPM is: `dafe6dcc93252be317c12637850bd1a1c38a7c8f5db25c4f281c079b4ac3db71`
|
||||
|
||||
The SHA-256 for the source RPM is: `699b4b740075ecf72d0ff0ef422e9747745552c4e17c21c28beb48fbb193ba75`
|
||||
|
||||
For other platforms, please compile version 1.2.1 from source.
|
||||
|
||||
* [Ubuntu Linux](https://developers.ripple.com/build-run-rippled-ubuntu.html)
|
||||
|
||||
* [macOS](https://developers.ripple.com/build-run-rippled-macos.html)
|
||||
|
||||
* [Other platforms](https://github.com/ripple/rippled/tree/master/Builds)
|
||||
For other platforms, please [compile version 1.2.1 from source](https://github.com/XRPLF/rippled/tree/1.2.1/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
@@ -76,15 +70,15 @@ The Ripple technical operations team plans to deploy version 1.2.1 to all XRP Le
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
Related documentation is available in the XRP Ledger Dev Portal, including detailed example API calls and web tools for API testing: [https://developers.ripple.com/](https://developers.ripple.com/)
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](/docs/), including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
|
||||
* [XRP Chat Forum](http://www.xrpchat.com/)
|
||||
* XRP Chat Forum _(Shut down. Formerly `www.xrpchat.com`)_
|
||||
|
||||
## Other Information
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ Version 1.2.2 corrects a technical flaw in the fee escalation engine which could
|
||||
|
||||
If you operate a rippled server, but do not upgrade to 1.2.2 as soon as possible, then your server may experience restarts or outages.
|
||||
|
||||
Additionally, the **MultisignReserve**, **fixTakerDryOfferRemoval** and **fix1578** Amendments are expected to become enabled no earlier than Wednesday, 2019-03-20. When this happens, if you are not running [release 1.2.0](https://developers.ripple.com/blog/2019/rippled-1.2.0.html) or greater, your server will become [amendment blocked](https://developers.ripple.com/amendments.html#amendment-blocked), meaning that it:
|
||||
Additionally, the **MultisignReserve**, **fixTakerDryOfferRemoval** and **fix1578** Amendments are expected to become enabled no earlier than Wednesday, 2019-03-20. When this happens, if you are not running [release 1.2.0](/blog/2019/rippled-1.2.0.md) or greater, your server will become [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that it:
|
||||
|
||||
* Cannot determine the validity of a ledger;
|
||||
|
||||
@@ -40,27 +40,23 @@ If the **MultisignReserve**, **fixTakerDryOfferRemoval** and **fix1578** Amendme
|
||||
|
||||
### Upgrading
|
||||
|
||||
For instructions on updating XRP Ledger on supported platforms, see here: [Install `rippled`](https://developers.ripple.com/install-rippled.html)
|
||||
For instructions on updating XRP Ledger on supported platforms, see here: [Install `rippled`](/docs/infrastructure/installation)
|
||||
|
||||
The SHA-256 for the RPM is: `e846e864c273593fcfbc9b1f21c7f2cf236454fd88ab8624446f446e9df0a447`
|
||||
|
||||
The SHA-256 for the source RPM is: `c8a67054d81fc5d7dfba5b4ebe630f44507886da418c5ba6fb7a245e9d78cd01`
|
||||
|
||||
For other platforms, please compile version 1.2.2 from source.
|
||||
|
||||
* [Ubuntu Linux](https://developers.ripple.com/build-run-rippled-ubuntu.html)
|
||||
|
||||
* [macOS](https://developers.ripple.com/build-run-rippled-macos.html)
|
||||
|
||||
* [Other platforms](https://github.com/ripple/rippled/tree/master/Builds)
|
||||
For other platforms, please [compile version 1.2.2 from source](https://github.com/XRPLF/rippled/tree/1.2.2/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 0ebed961424d9757f5d26ce7e8b3e5e8d83eb239
|
||||
Author: seelabs <scott.determan@yahoo.com>
|
||||
Date: Mon Mar 4 11:45:12 2019 -0500
|
||||
|
||||
Set version to 1.2.2
|
||||
```
|
||||
|
||||
## Network Update
|
||||
|
||||
@@ -68,13 +64,13 @@ The Ripple technical operations team plans to deploy version 1.2.2 to all XRP Le
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](https://developers.ripple.com/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](/docs/), including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ If you operate an XRP Ledger server, then you should **upgrade to version 1.2.3
|
||||
|
||||
If you operate a rippled server, but do not upgrade to 1.2.3 immediately, then your server may experience restarts or outages.
|
||||
|
||||
Additionally, if you are not already running [release 1.2.0](https://developers.ripple.com/blog/2019/rippled-1.2.0.html) or greater, then your server is [amendment blocked](https://developers.ripple.com/amendments.html#amendment-blocked), meaning that it:
|
||||
Additionally, if you are not already running [release 1.2.0](/blog/2019/rippled-1.2.0.md) or greater, then your server is [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that it:
|
||||
|
||||
* Cannot determine the validity of a ledger;
|
||||
|
||||
@@ -38,27 +38,23 @@ Additionally, if you are not already running [release 1.2.0](https://developers.
|
||||
|
||||
### Upgrading
|
||||
|
||||
For instructions on updating XRP Ledger on supported platforms, see [Install rippled](https://developers.ripple.com/install-rippled.html).
|
||||
For instructions on updating XRP Ledger on supported platforms, see [Install `rippled`](/docs/infrastructure/installation).
|
||||
|
||||
The SHA-256 for the RPM is: `8e6c5727c359d0c1d8a7235a149b18ddbad63d18de127b9370c335b1e4bc6775`
|
||||
|
||||
The SHA-256 for the source RPM is: `b2664e7e47af0ceefbea3619505f37426f026146690a13565f381c8cb7ca25a6`
|
||||
|
||||
For other platforms, please compile version 1.2.3 from source.
|
||||
|
||||
* [Ubuntu Linux](https://developers.ripple.com/build-run-rippled-ubuntu.html)
|
||||
|
||||
* [macOS](https://developers.ripple.com/build-run-rippled-macos.html)
|
||||
|
||||
* [Other platforms](https://github.com/ripple/rippled/tree/master/Builds)
|
||||
For other platforms, please [compile version 1.2.3 from source](https://github.com/XRPLF/rippled/tree/1.2.3/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 0329ee236ffe2d7658bbdd1d970bb2af6337a941
|
||||
Author: seelabs <scott.determan@yahoo.com>
|
||||
Date: Thu Mar 28 16:38:43 2019 -0400
|
||||
|
||||
Set version to 1.2.3
|
||||
```
|
||||
|
||||
## Network Update
|
||||
|
||||
@@ -66,17 +62,17 @@ The Ripple technical operations team plans to deploy version 1.2.3 to all XRP Le
|
||||
|
||||
## Known Issues
|
||||
|
||||
Version 1.2.3 has a bug that can cause the server to stop checking for updates to its configured validator list sites. If this happens, your server may lose sync with the network when its current validator list file expires. You can restore sync by restarting the rippled service. (This issue is related to the issues fixed in the [version 1.1.1 release](https://developers.ripple.com/blog/2018/rippled-1.1.1.html).) A fix for this issue is forthcoming.
|
||||
Version 1.2.3 has a bug that can cause the server to stop checking for updates to its configured validator list sites. If this happens, your server may lose sync with the network when its current validator list file expires. You can restore sync by restarting the rippled service. (This issue is related to the issues fixed in the [version 1.1.1 release](/blog/2018/rippled-1.1.1.md).) A fix for this issue is forthcoming.
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](https://developers.ripple.com/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](/docs/), including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ If you operate an XRP Ledger server, then you should **upgrade to version 1.2.4
|
||||
|
||||
If you operate a rippled server, but do not upgrade to 1.2.4 immediately, then your server may experience restarts or outages and may be unable to retrieve updated validator lists from the publishers that you have configured.
|
||||
|
||||
Additionally, if you are not already running [release 1.2.0](https://developers.ripple.com/blog/2019/rippled-1.2.0.html) or greater, then your server is [amendment blocked](https://developers.ripple.com/amendments.html#amendment-blocked), meaning that it:
|
||||
Additionally, if you are not already running [release 1.2.0](/blog/2019/rippled-1.2.0.md) or greater, then your server is [amendment blocked](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), meaning that it:
|
||||
|
||||
* Cannot determine the validity of a ledger;
|
||||
|
||||
@@ -38,27 +38,22 @@ Additionally, if you are not already running [release 1.2.0](https://developers.
|
||||
|
||||
### Upgrading
|
||||
|
||||
For instructions on updating XRP Ledger on supported platforms, see [Install rippled](https://developers.ripple.com/install-rippled.html).
|
||||
For instructions on updating XRP Ledger on supported platforms, see [Install `rippled`](/docs/infrastructure/installation).
|
||||
|
||||
The SHA-256 for the RPM is: `63f33ca0fbd089a4d1bf5ca4f5c925087bb33209ccc0f29eba04a8e5de0c501a`
|
||||
|
||||
The SHA-256 for the source RPM is: `9b38ee937d19c57d6461d7ed47ae477893ed7d9e23bfc4d867291d5e3b86b7cb`
|
||||
|
||||
For other platforms, please compile version 1.2.4 from source.
|
||||
|
||||
* [Ubuntu Linux](https://developers.ripple.com/build-run-rippled-ubuntu.html)
|
||||
|
||||
* [macOS](https://developers.ripple.com/build-run-rippled-macos.html)
|
||||
|
||||
* [Other platforms](https://github.com/ripple/rippled/tree/master/Builds)
|
||||
For other platforms, please [compile version 1.2.4 from source](https://github.com/XRPLF/rippled/tree/1.2.4/Builds).
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 834f545498c0ff8fe22eb4648fe4534dea2ab965
|
||||
Author: Nik Bougalis <nikb@bougalis.net>
|
||||
Date: Mon Apr 15 12:38:52 2019 -0700
|
||||
Set version to 1.2.4
|
||||
|
||||
```
|
||||
|
||||
## Network Update
|
||||
|
||||
@@ -67,13 +62,13 @@ The Ripple technical operations has deployed version 1.2.4 to all XRP Ledger ser
|
||||
|
||||
## Learn, ask questions, and discuss
|
||||
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](https://developers.ripple.com/), including detailed example API calls and web tools for API testing.
|
||||
Related documentation is available in the [XRP Ledger Dev Portal](/docs/), including detailed example API calls and web tools for API testing.
|
||||
|
||||
Other resources:
|
||||
|
||||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||||
|
||||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||||
* The Ripple Dev Blog _(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))_
|
||||
|
||||
* Ripple Technical Services: <support@ripple.com>
|
||||
|
||||
|
||||
@@ -51,7 +51,7 @@ For other platforms, please compile version 1.4.0 from source.
|
||||
|
||||
* [Build on macOS](https://xrpl.org/build-run-rippled-macos.html)
|
||||
|
||||
* [Build on other platforms](https://github.com/ripple/rippled/tree/master/Builds)
|
||||
* [Build on other platforms](https://github.com/XRPLF/rippled/blob/master/BUILD.md)
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ The primary mission of the C++ team at Ripple is to contribute to `rippled`, the
|
||||
|
||||
As a team, our primary focus is on ensuring that the codebase is solid, that the code is robust and that it is well-suited to be the core of the next-generation of financial infrastructure, one which allows value to not only move as fast and as efficiently as information does today, but to move securely as well.
|
||||
|
||||
In an [earlier blog post](https://developers.ripple.com/blog/2017/invariant-checking.html), I noted that our existing software development and quality assurance process—honed over several years—places heavy emphasis on correctness and security. I highlighted our use of automated tests and specialized tooling (such as static analyzers) but I also alluded to the human element as well: our rigorous and public code reviews and regular security audits of the codebase by specialists. I’d like to take the opportunity to discuss those practices in greater detail.
|
||||
In an [earlier blog post](/blog/2017/invariant-checking.md), I noted that our existing software development and quality assurance process—honed over several years—places heavy emphasis on correctness and security. I highlighted our use of automated tests and specialized tooling (such as static analyzers) but I also alluded to the human element as well: our rigorous and public code reviews and regular security audits of the codebase by specialists. I’d like to take the opportunity to discuss those practices in greater detail.
|
||||
|
||||
<!-- BREAK -->
|
||||
|
||||
|
||||
@@ -53,7 +53,7 @@ For other platforms, please compile version 1.5.0 from source.
|
||||
|
||||
* [Build on macOS](https://xrpl.org/build-run-rippled-macos.html)
|
||||
|
||||
* [Build on other platforms](https://github.com/ripple/rippled/tree/master/Builds)
|
||||
* [Build on other platforms](https://github.com/XRPLF/rippled/blob/master/BUILD.md)
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
|
||||
@@ -41,7 +41,7 @@ For other platforms, please compile version 1.6.0 from source.
|
||||
|
||||
* [Build on macOS](https://xrpl.org/build-run-rippled-macos.html)
|
||||
|
||||
* [Build on other platforms](https://github.com/ripple/rippled/tree/master/Builds)
|
||||
* [Build on other platforms](https://github.com/XRPLF/rippled/blob/master/BUILD.md)
|
||||
|
||||
The first log entry should be the change setting the version:
|
||||
|
||||
|
||||
@@ -72,7 +72,7 @@ On supported platforms, see the [instructions on updating rippled](https://xrpl.
|
||||
| [RPM for Red Hat / CentOS (x86-64)](https://repos.ripple.com/repos/rippled-rpm/stable/rippled-1.7.0-1.el7.x86_64.rpm) | `da32137d460c6c2ce5b7035d82b637f71138fa92564f7ab1fdf04d1e59be8f2a` |
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_1.7.0-1_amd64.deb) | `1920881caab4fac02a4a99a67bb4f2746b89f7b99f2c28e83832039a2dd5d8a5` |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit c0a0b79d2d483b318ce1d82e526bd53df83a4a2c
|
||||
|
||||
@@ -34,7 +34,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [RPM for Red Hat / CentOS (x86-64)](https://repos.ripple.com/repos/rippled-rpm/stable/rippled-1.7.2-1.el7.x86_64.rpm) | `fbdc7a442b1cbcb04cacda40fc3eb0b6178329b5bf9ba3084b4728a0ed2d9b26` |
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_1.7.2-1_amd64.deb) | `71767ee966b3520796d03ffbdc14ddeeb44876097b897df0ff71b2da3e69e633` |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 34ee4ca0cb59037e840f7d454114701b534f0afa
|
||||
|
||||
@@ -31,7 +31,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [RPM for Red Hat / CentOS (x86-64)](https://repos.ripple.com/repos/rippled-rpm/stable/rippled-1.7.3-1.el7.x86_64.rpm) | `d994543be11edeb9c1256cd7e35c6bd7f5b53f23f97b8bdf380302b24269d47e` |
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_1.7.3-1_amd64.deb) | `5d13b32ac00796a50266030de5de40e85c310c762a88e72d435e5c8c2e30becb` |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 96bbabbd2ece106779bb544aa0e4ce174e99fdf6
|
||||
|
||||
@@ -36,7 +36,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [RPM for Red Hat / CentOS (x86-64)](https://repos.ripple.com/repos/rippled-rpm/stable/rippled-1.8.1-1.el7.x86_64.rpm) | `be092bcb02f8118121f6303ede4f109601f797cd02a1ddaf237604fd54e0237b` |
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_1.8.1-1_amd64.deb) | `b95772f59cfcd0fb2318ad908ab00421bcbd46c430c12371c0fc9d6003ed06b3` |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit fbedfb25aefc609aff2c6090b19c419c224a8ab2
|
||||
|
||||
@@ -29,7 +29,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [RPM for Red Hat / CentOS (x86-64)](https://repos.ripple.com/repos/rippled-rpm/stable/rippled-1.8.4-1.el7.x86_64.rpm) | `b47fae21505a8dfe88ffc315d6bebb5fb5204bc74a9b8439bb9b8d1b8ffe45ee` |
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_1.8.4-1_amd64.deb) | `e7f642a4b7f4790c99a0e92d4d48d167ed33b030363a79d1d5f9404cb0fef31c` |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit d49b4862244d9359c046bd04d48237591516cb6a
|
||||
|
||||
@@ -27,7 +27,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [RPM for Red Hat / CentOS (x86-64)](https://repos.ripple.com/repos/rippled-rpm/stable/rippled-1.8.5-1.el7.x86_64.rpm) | `c3a84dbf7c4b253f86a85369bf8ab92198cbc8b42c37dd17b62c88b7b5b986bf` |
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_1.8.5-1_amd64.deb) | `b63b786de318677a8b179c2712466846f5541566a10c66763b6d9b0ac9738154` |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 72377e7bf25c4eaee5174186d2db3c6b4210946f
|
||||
|
||||
@@ -24,7 +24,7 @@ For more information about NFTs on the XRP Ledger, see [NFT Conceptual Overview]
|
||||
|
||||
## Install / Upgrade
|
||||
|
||||
On supported platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds).
|
||||
On supported platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md).
|
||||
|
||||
The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [RPM for Red Hat / CentOS (x86-64)](https://repos.ripple.com/repos/rippled-rpm/stable/rippled-1.9.1-1.el7.x86_64.rpm) | `c7885668f1cc47a86a12b73a37f1b060ed9cb08acb9d512804cbea23dd08ea2f` |
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_1.9.1-1_amd64.deb) | `5e233e89e61271d2a6c0a282d303a9726896c20d64886b22f698598982fe399b` |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit e32bc674aa2a035ea0f05fe43d2f301b203f1827
|
||||
|
||||
@@ -36,7 +36,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [RPM for Red Hat / CentOS (x86-64)](https://repos.ripple.com/repos/rippled-rpm/stable/rippled-1.9.2-1.el7.x86_64.rpm) | `a377802fd25f92d8be8cca9b63a0e9b586e9fc52527ed17e73608bf6a96a6ac4` |
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_1.9.2-1_amd64.deb) | `d558bf5f769a20d2e6c639fb814f4f05e9650385f0f1a182a2a219c56c889624` |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit e5275b857752c2d6078cb8774edbb7e60f179d72
|
||||
|
||||
@@ -29,7 +29,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [RPM for Red Hat / CentOS (x86-64)](https://repos.ripple.com/repos/rippled-rpm/stable/rippled-1.9.3-1.el7.x86_64.rpm) | `fc8cc3bbcff02291ce5ce5a466e1b4a3f54c1515befed36dcad92ceae69dafa9` |
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_1.9.3-1_amd64.deb) | `516195120cbb8ca68e1c596a69b0b9fe1ac7e0898dcc697d6289396fadae142d` |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 47dec467ea659c1b64c7b5f4eb8a1bfa9759ff91
|
||||
|
||||
@@ -38,7 +38,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [RPM for Red Hat / CentOS (x86-64)](https://repos.ripple.com/repos/rippled-rpm/stable/rippled-1.9.4-1.el7.x86_64.rpm) | `fa6bbcda7781c6b3680e56849566f27d46df4cce16b1d9ff6432262f634f2970` |
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_1.9.4-1_amd64.deb) | `2d23b897bc0bd235f2f74cd52eab8d0ac52b416c0294a02112385192285c0169` |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit ba3c0e51455a88d76d90b996f20c0f102ac3f5a0
|
||||
|
||||
@@ -33,7 +33,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [RPM for Red Hat / CentOS (x86-64)](https://repos.ripple.com/repos/rippled-rpm/stable/rippled-1.10.0-1.el7.x86_64.rpm) | `568ee33b4560be0505a0be0966f9ca1f477444a60c2632eff8ab71864c6b020b` |
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_1.10.0-1_amd64.deb) | `5015efad92743a57cfdba573cf968b740b2418360034c6c6e8d3a514d60b6a89` |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 07f047b1e260e5b937af28e8f8da9c360ea832b9
|
||||
|
||||
@@ -34,7 +34,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_1.11.0-1_amd64.deb) | `15fd0e7dd44b74cd8c8174db73f5cdbccfb2da1624db9b91c559dff62e651d4f` |
|
||||
| [Portable Builds (Linux x86-64)](https://github.com/XRPLF/rippled-portable-builds) | (Use signature verification) |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 264280edd79b7f764536e02459f33f66a59c0531
|
||||
|
||||
@@ -39,7 +39,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_1.12.0-1_amd64.deb) | `cf7b7b2130b8255d8c13fc18b3a4a0ec251d88386b69ec2e60c34b31df310f91` |
|
||||
| [Portable Builds (Linux x86-64)](https://github.com/XRPLF/rippled-portable-builds) | (Use signature verification) |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 89780c8e4fd4d140fcb912cf2d0c01c1b260539e
|
||||
|
||||
@@ -40,7 +40,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_2.0.0-1_amd64.deb) | `69568c467a5291b441ce6f1385bd20cdfaf02e4496ca9043441fdb842d9975dc` |
|
||||
| [Portable Builds (Linux x86-64)](https://github.com/XRPLF/rippled-portable-builds) | (Use signature verification) |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 2b0313d60c4226cc98ad39fe8eb659deca48f32a
|
||||
|
||||
@@ -32,7 +32,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_2.0.1-1_amd64.deb) | `55b2e15776d57f8eb405d73fa796fbb5e94b0d4ef350dece4baa675a1fb73cd6` |
|
||||
| [Portable Builds (Linux x86-64)](https://github.com/XRPLF/rippled-portable-builds) | (Use signature verification) |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 22cdb5728b7eb563f6798dbd1f15c88fa1894e7c
|
||||
|
||||
@@ -32,7 +32,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_2.1.1-1_amd64.deb) | `dee7759d8562c8cc1f98fef4645c3e9c29030b0f1eb4adc4346bcb44e11b22de` |
|
||||
| [Portable Builds (Linux x86-64)](https://github.com/XRPLF/rippled-portable-builds) | (Use signature verification) |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 2d1854f354ff8bb2b5671fd51252c5acd837c433
|
||||
|
||||
@@ -34,7 +34,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_2.2.0-1_amd64.deb) | `1bd26cea8e289e40368542eb370cec95b42905855f9ada8ece361a43134834c9` |
|
||||
| [Portable Builds (Linux x86-64)](https://github.com/XRPLF/rippled-portable-builds) | (Use signature verification) |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 2df635693d54b8c17c428faf6ef99da2f14a9382
|
||||
|
||||
@@ -35,7 +35,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_2.2.1-1_amd64.deb) | `f696e6898ad64e73d75bb9a1f50fb325b9675b168ffaeeacfce53fbd9e35bbee` |
|
||||
| [Portable Builds (Linux x86-64)](https://github.com/XRPLF/rippled-portable-builds) | (Use signature verification) |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit e6ef0fc26cb8d4db25075eaa1fe21fcc7f984751
|
||||
|
||||
@@ -35,7 +35,7 @@ On supported platforms, see the [instructions on installing or updating `rippled
|
||||
| [DEB for Ubuntu / Debian (x86-64)](https://repos.ripple.com/repos/rippled-deb/pool/stable/rippled_2.2.2-1_amd64.deb) | `9e0734966089d9cfde40d1a3551ae1e219faaadfe9fdc69eb900c6cb5024d658` |
|
||||
| [Portable Builds (Linux x86-64)](https://github.com/XRPLF/rippled-portable-builds) | (Use signature verification) |
|
||||
|
||||
For other platforms, please [build from source](https://github.com/ripple/rippled/tree/master/Builds). The most recent commit in the git log should be the change setting the version:
|
||||
For other platforms, please [build from source](https://github.com/XRPLF/rippled/blob/master/BUILD.md). The most recent commit in the git log should be the change setting the version:
|
||||
|
||||
```text
|
||||
commit 85214bdf811e1ff11a02977211fe59b07619b856
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user