Files
xrpl-dev-portal/content/blog/2016/trustsetauth-voting.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.3 KiB

The TrustSetAuth Amendment Is Open For Voting

This notice is for all validator operators, and may be relevant to gateways that utilize the Authorized Account feature.

The new TrustSetAuth amendment is open for voting now. This amendment allows pre-authorization of accounting relationships (zero-balance trust lines) when using Authorized Accounts. With this amendment enabled, currency issuers can authorize other addresses to hold their issued currencies without waiting for the other addresses to take action. Without the amendment, currency holders must first create the accounting relationship with the issuer by setting a limit with a TrustSet transaction.

Ripple's validators will vote in favor of the TrustSetAuth amendment, and we expect the new feature to become active by 2016-07-19.

For more information, see the following articles in the Ripple Developer Center:

To continue receiving updates about the rippled server, please subscribe to the Ripple Server Google Group:

https://groups.google.com/forum/#!forum/ripple-server