mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-28 15:45:50 +00:00
Update/remove legacy links
This commit is contained in:
mDuo13
@@ -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:
|
||||
|
||||
commit 7779dcdda00ea61a976cf5f387bc1f3bb4ebbfdd
|
||||
Author: Mike Ellery <mellery451@gmail.com>
|
||||
Date: Tue Feb 12 16:41:03 2019 -0800
|
||||
```text
|
||||
commit 7779dcdda00ea61a976cf5f387bc1f3bb4ebbfdd
|
||||
Author: Mike Ellery <mellery451@gmail.com>
|
||||
Date: Tue Feb 12 16:41:03 2019 -0800
|
||||
|
||||
Set version to 1.2.0
|
||||
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:
|
||||
|
||||
commit 0ebed961424d9757f5d26ce7e8b3e5e8d83eb239
|
||||
Author: seelabs <scott.determan@yahoo.com>
|
||||
Date: Mon Mar 4 11:45:12 2019 -0500
|
||||
```text
|
||||
commit 0ebed961424d9757f5d26ce7e8b3e5e8d83eb239
|
||||
Author: seelabs <scott.determan@yahoo.com>
|
||||
Date: Mon Mar 4 11:45:12 2019 -0500
|
||||
|
||||
Set version to 1.2.2
|
||||
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:
|
||||
|
||||
commit 0329ee236ffe2d7658bbdd1d970bb2af6337a941
|
||||
Author: seelabs <scott.determan@yahoo.com>
|
||||
Date: Thu Mar 28 16:38:43 2019 -0400
|
||||
```text
|
||||
commit 0329ee236ffe2d7658bbdd1d970bb2af6337a941
|
||||
Author: seelabs <scott.determan@yahoo.com>
|
||||
Date: Thu Mar 28 16:38:43 2019 -0400
|
||||
|
||||
Set version to 1.2.3
|
||||
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:
|
||||
|
||||
commit 834f545498c0ff8fe22eb4648fe4534dea2ab965
|
||||
Author: Nik Bougalis <nikb@bougalis.net>
|
||||
Date: Mon Apr 15 12:38:52 2019 -0700
|
||||
Set version to 1.2.4
|
||||
|
||||
```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 -->
|
||||
|
||||
|
||||
Reference in New Issue
Block a user