fix1571 is Now Available

2018-6-21 00:04

As previously announced, the fix1571 amendment became enabled on the XRP Ledger on 2018-06-19. Furthermore, the fix1623 amendment is expected to become enabled on 2018-06-20, followed by the fix1543 amendment on 2018-06-21.

Action Required If you operate a rippled server, you should upgrade to version 1.0.1 (or higher) immediately.

For instructions on upgrading rippled on supported platforms, see Updating rippled on supported platforms.

Impact of Not Upgrading

If you operate a rippled server on a version older than 1.0.0, then your server is now amendment blocked, 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 Could rely on potentially invalid data fix1571 Summary

Changes Escrow to fix the following issues:

Changes the EscrowCreate transaction 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, including detailed example API calls and web tools for API testing.

Other resources:

The Ripple Forum The Ripple Dev Blog Ripple Technical Services: [email protected] XRP Chat

The post fix1571 is Now Available appeared first on Ripple.

origin »

Version (V) на Currencies.ru

$ 0 (+0.00%)
Объем 24H $0
Изменеия 24h: 0.00 %, 7d: 0.00 %
Cегодня L: $0 - H: $0
Капитализация $0 Rank 99999
Доступно / Всего 651.894m V

fix1571 amendment enabled available rippled higher version

Источник: ripple.com

fix1571 amendment → Результатов: 1


Партнеры Currencies.ru



Реклама на Currencies.ru

Самое свежее на Currencies.ru

The Ripple Dev Blog Has Moved

To continue seeing posts from Ripple’s developers and staff, visit the new Dev Blog location at: http://developers.ripple.com/blog/ The post The Ripple Dev Blog Has Moved appeared first on Ripple.

fixTakerDryOfferRemoval is Now Available

As previously announced, the fixTakerDryOfferRemoval amendment became enabled on the XRP Ledger on 2019-04-02. Action Required If you operate a rippled server, you should upgrade to version 1. 2.

Introducing XRP Ledger (rippled) version 1.2.3

Ripple has released version 1. 2. 3 of rippled, the reference implementation of the core XRP Ledger protocol. Version 1. 2. 3 corrects a technical flaw that could, in rare circumstances, cause the server to dereference a null pointer, which could result in the server process being terminated by the operating system.

fix1578 is Now Available

As previously announced, the fix1578 amendment became enabled on the XRP Ledger on 2019-03-23. Action Required If you operate a rippled server, you should upgrade to version 1. 2. 0 (or higher) immediately.

The fix1578 and fixTakerDryOfferRemoval Amendments are Expected

The fix1578 amendment to the XRP Ledger, introduced in rippled v1. 2. 0, has gained support from a majority of trusted validators. Currently, it is expected to become enabled on 2019-03-23. The fixTakerDryOfferRemoval amendment to the XRP Ledger has also gained support from a majority of trusted validators.

Introducing XRP Ledger (rippled) version 1.2.2

Ripple has released version 1. 2. 2 of rippled, our reference implementation of the core XRP Ledger server. Version 1. 2. 2 corrects a technical flaw in the fee escalation engine which could cause some fee metrics to be calculated incorrectly.

Introducing XRP Ledger (rippled) version 1.2.1

Ripple has released version 1. 2. 1 of rippled, our reference implementation of the core XRP Ledger server. Version 1. 2. 1 introduces several fixes including: A change in the information reported via the enhanced crawl functionality introduced in version 1.