If you want more content like this, please visit ripple.com.
Originally, the FlowV2 amendment was planned to replace
rippled’s payment processing engine with a more robust and efficient implementation. It was previously expected to become active on Wednesday, 2016-08-24.
FlowV2 Was Vetoed
rippled team found a flaw in FlowV2 while testing. As a result, the Ripple network has vetoed the new payment engine amendment.
A corrected version of the payment processing engine has been created and is now undergoing further testing. It is scheduled to be included in a future version of
rippled as an amendment called Flow.
This demonstrates the robustness of Ripple’s amendment process. The review period and governance code with vetoing work as intended.
No action is currently required. However, Ripple recommends that validator operators also veto the FlowV2 amendment to ensure it does not regain a majority.
To veto the amendment, add the following, single line, under the
[veto_amendments] stanza to the
rippled.cfg file on validators:
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: https://ripple.com/build/
- The Ripple Forum: https://forum.ripple.com/
- The Ripple Dev Blog: https://ripple.com/category/dev-blog/
- Ripple Technical Services: firstname.lastname@example.org
- XRP Chat: http://www.xrpchat.com
Please visit ripple.com for more information.