The Flow Amendment is Open for Voting

Oct 7, 2016 | Ryan Young

Originally introduced in rippledversion 0.32.1, but later vetoed after a flaw was discovered in the code while testing, the new Flow Amendment is now open for voting. 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 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, 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.