# The Flow Amendment Will Soon Be Available

A majority of `rippled` validators voted to enable the [Flow Amendment](/resources/known-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](/docs/concepts/networks-and-servers/amendments#amendment-blocked-servers), 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](/docs/infrastructure/installation/update-rippled-automatically-on-linux).

For other platforms, please [compile version 0.33.0-hf1 from source](https://github.com/XRPLF/rippled/blob/0.33.0-hf1/Builds).

## Learn, ask questions, and discuss

Related documentation is available in the Ripple Developer Portal, 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 *(Replaced with [xrpl.org/blog](https://xrpl.org/blog/))*
* Ripple Technical Services: support@ripple.com
* XRP Chat *(Shut down. Formerly `www.xrpchat.com`)*