fix1571 is Now Available
https://ripple.com/dev-blog/fix1571-now-available/
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.
正如之前宣布的那样，修正案fix1571已于2018-06-19在XRP总账网络上启用。此外，修正案fix1623预计于2018-06-20启用，随后是修正案fix1543预计于2018-06-21启用。
Action Required
应采取的行动
If you operate a rippled server, you should upgrade to version 1.0.1 (or higher) immediately.
如果用户运行rippled服务器，应立即升级至1.0.1版本（或更高）。
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:
如果用户运行低于1.0.0版本的rippled服务器，那么用户当前的服务器将处在共识阻止状态，也就是意味着该服务器：
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
修正案fix1571摘要
Changes Escrow to fix the following issues:
Escrow变更所要修复的问题：
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.
变更在EscrowCreate交易中，要求提供Condition或FinishAfter字段（或两者）。在此修正案生效前已创建的既没有Condition字段也没有FinishAfter字段的交易，可以在CancelAfter字段设定的时间之前的任何时间完成。
Fixes a flaw that incorrectly prevents time-based Escrows from being finished in some circumstances.
修复了在某些情况下错误的阻止正在完成的基于时间的Escrow的缺陷。