mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-24 13:45:49 +00:00
c3194d9b08
Also, adjust some formatting for Redocly (admonitions, indented code blocks, authorship lines)
44 lines
2.0 KiB
Markdown
44 lines
2.0 KiB
Markdown
---
|
||
date: 2016-10-17
|
||
labels:
|
||
- Amendments
|
||
category: 2016
|
||
theme:
|
||
markdown:
|
||
editPage:
|
||
hide: true
|
||
---
|
||
# 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.
|
||
|
||
## Action Required
|
||
|
||
**If you operate a `rippled` server, then you should upgrade to version 0.33.0 or later by Thursday, 2016-10-20, for service continuity.**
|
||
|
||
## 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:
|
||
|
||
* 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
|
||
|
||
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 other platforms, please [compile version 0.33.0-hf1 from source](https://github.com/ripple/rippled/tree/master/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.
|
||
|
||
Other resources:
|
||
|
||
* The Ripple Forum (_Disabled._ Formerly `forum.ripple.com`)
|
||
* [The Ripple Dev Blog](https://developers.ripple.com/blog/)
|
||
* Ripple Technical Services: support@ripple.com
|
||
* [XRP Chat](http://www.xrpchat.com/)
|