ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-29 08:05:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update/remove legacy links

Browse Source
This commit is contained in:
mDuo13
2025-05-08 17:01:48 -07:00
parent cd44b8e1d5
commit 4ba07466e1
101 changed files with 628 additions and 612 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
blog/2019/fix1578-enabled.md
View File

@@ -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/)