Files
xrpl-dev-portal/content/blog/2016/flow-available.md
Amarantha Kulkarni b4489f8649 Migrate dev-blog to Redocly (#2346)
* Step 1 to migrate the blog - Add blog pages from the dev-blog repo

* Add blog-specific sidebar (& update contents)

* Add new dev reflections blog post from 01-23-2024

* Blog migration: fix markdoc errors and broken links

* Remove community pages from the sidebar

---------

Co-authored-by: mDuo13 <mduo13@gmail.com>
2024-01-31 16:10:32 -08:00

1.7 KiB
Raw Blame History

The Flow Amendment is Now Available

The Flow Amendment became available on the Ripple Consensus Ledger in ledger 24,970,753 (2016-10-21T19:47:22Z).

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, immediately, for service continuity.

Impact of Not Upgrading

If you operate a rippled server but dont upgrade to version 0.33.0 or later, immediately, 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

For instructions on updating rippled on supported platforms, see Updating rippled on supported platforms.

For other platforms, please compile version 0.33.0 from source.

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: