The Amendments system provides a means of introducing new features to the decentralized Ripple consensus network without causing disruptions. The amendments system works by utilizing the core consensus process of the network to approve any changes by showing continuous support before those changes go into effect. An amendment normally requires 80% support for two weeks before it can apply.
When an Amendment has been enabled, it applies permanently to all ledger versions after the one that included it. You cannot disable an Amendment, unless you introduce a new Amendment to do so.
Any changes to transaction processing could cause servers to build a different ledger with the same set of transactions. If some validators (
rippled servers participating in consensus) have upgraded to a new version of the software while other validators use the old version, this could cause anything from minor inconveniences to full outages. In the minor case, a minority of servers spend more time and bandwidth fetching the actual consensus ledger because they cannot build it using the transaction processing rules they already know. In the worst case, the consensus process might be unable to validate new ledger versions because servers with different rules could not reach a consensus on the exact ledger to build.
Amendments solve this problem, so that new features can be enabled only when enough validators support those features.
Users and businesses who rely on the Ripple Consensus Ledger can also use Amendments to provide advance notice of changes in transaction processing that might affect their business. However, API changes that do not impact transaction processing or the consensus process do not need Amendments.
An amendment is a fully-functional feature or change, waiting to be enabled by the peer-to-peer network as a part of the consensus process. A
rippled server that wants to use an amendment has code for two modes: without the amendment (old behavior) and with the amendment (new behavior).
Every amendment has a unique identifying hex value and a short name. The short name is for human use, and is not used in the amendment process. Two servers can support the same amendment ID while using different names to describe it. An amendment's name is not guaranteed to be unique.
See also: Known Amendments
Every 256th ledger is called a "flag" ledger. The process of approving an amendment starts in the ledger version immediately before the flag ledger. When
rippled validator servers send validation messages for that ledger, those servers also submit votes in favor of specific amendments. If a validator does not vote in favor of an amendment, that is the same as voting against the amendment. (Fee Voting also occurs around flag ledgers.)
The flag ledger itself has no special contents. However, during that time, the servers look at the votes of the validators they trust, and decide whether to insert an
EnableAmendment pseudo-transaction into the following ledger. The flags of an EnableAmendment pseudo-transaction show what the server thinks happened:
tfGotMajorityflag means that support for the amendment has increased to at least 80% of trusted validators.
tfLostMajorityflag means that support for the amendment has decreased to less than 80% of trusted validators.
- An EnableAmendment pseudo-transaction with no flags means that support for the amendment has been enabled. (The change in transaction processing applies to every ledger after this one.)
A server only inserts the pseudo-transaction to enable an amendment if all of the following conditions are met:
- The amendment has not already been enabled.
- A previous ledger includes an EnableAmendment pseudo-transaction for this amendment with the
- The previous ledger in question is an ancestor of the current ledger.
- The previous ledger in question has a close time that is at least two weeks before the close time of the latest flag ledger.
- There are no EnableAmendment pseudo-transactions for this amendment with the
tfLostMajorityflag enabled in the consensus ledgers between the
tfGotMajoritypseudo-transaction and the current ledger.
tfLostMajority EnableAmendment pseudo-transaction could be included in the same ledger as the pseudo-transaction to enable an amendment. In this case, the pseudo-transaction with the
tfLostMajority pseudo-transaction has no effect.
Each version of
rippled is compiled with a list of known amendments and the code to implement those amendments. By default,
rippled supports known amendments and opposes unknown amendments. Operators of
rippled validators can configure their servers to explicitly support or oppose certain amendments, even if those amendments are not known to their
To become enabled, an amendment must be supported by at least 80% of trusted validators continuously for two weeks. If support for an amendment goes below 80% of trusted validators, the amendment is temporarily rejected. The two week period starts over if the amendment regains support of at least 80% of trusted validators. (This can occur if validators vote differently, or if there is a change in which validators are trusted.) An amendment can gain and lose a majority an unlimited number of times before it becomes permanently enabled. An amendment cannot be permanently rejected, but it becomes very unlikely for an amendment to become enabled if new versions of
rippled do not have the amendment in their known amendments list.
As with all aspects of the consensus process, amendment votes are only taken into account by servers that trust the validators sending those votes. At this time, Ripple (the company) recommends only trusting the 5 default validators that Ripple (the company) operates. For now, trusting only those validators is enough to coordinate with Ripple (the company) on releasing new features.
Configuring Amendment Voting
You can temporarily configure an amendment using the
feature command. To make a persistent change to your server's support for an amendment, change your server's
[veto_amendments] stanza to list amendments you do not want the server to vote for. Each line should contain one amendment's unique ID, optionally followed by the short name for the amendment. For example:
[veto_amendments] C1B8D934087225F509BEB5A8EC24447854713EE447D277F69545ABFA0E0FD490 Tickets DA1BD556B42D85EA9C84066D028D355B52416734D3283F85E216EA5DA6DB7E13 SusPay
[amendments] stanza to list amendments you want to vote for. (Even if you do not list them here, by default a server votes for all the amendments it knows how to apply.) Each line should contain one amendment's unique ID, optionally followed by the short name for the amendment. For example:
[amendments] 4C97EBA926031A7CF7D7B36FDE3ED66DDA5421192D63DE53FFB46E43B9DC8373 MultiSign 42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE FeeEscalation
When an amendment gets enabled for the network after the voting process, servers running earlier versions of
rippled that do not know about the amendment become "amendment blocked" because they no longer understand the rules of the network. Servers that are amendment blocked:
- Cannot determine the validity of a ledger
- Cannot submit or process transactions
- Do not participate in the consensus process
- Do not vote on future amendments
Becoming amendment blocked is a security feature to protect backend applications. Rather than guessing and maybe misinterpreting a ledger after new rules have applied,
rippled reports that it does not know the state of the ledger because it does not know how the amendment works.
The amendments that a
rippled server is configured to vote for or against have no impact on whether the server becomes amendment blocked. A
rippled server always follows the set of amendments enabled by the rest of the network, to the extent possible. A server only becomes amendment blocked if the enabled amendment is not included in the amendment definitions compiled into the server's source code -- in other words, if the amendment is newer than the server.
If your server is amendment blocked, you must upgrade to a new version to sync with the network.
If you want to see how
rippled behaves with an amendment enabled, before that amendment gets enabled on the production network, you can run use
rippled's configuration file to forcibly enable a feature. This is intended for development purposes only.
Because other members of the consensus network probably do not have the feature enabled, you should not use this feature while connecting to the production network. While testing with features forcibly enabled, you should run
rippled in Stand-Alone Mode.
To forcibly enable a feature, add a
[features] stanza to your
rippled.cfg file. In this stanza, add the short names of the features to enable, one per line. For example:
[features] MultiSign TrustSetAuth
The following is a comprehensive list of all known amendments and their status on the production Ripple Consensus Ledger:
Note: In many cases, an incomplete version of the code for an amendment is present in previous versions of the software. The "Introduced" version in the table above is the first stable version.
Changes the way the transaction cost applies to proposed transactions. Modifies the consensus process to prioritize transactions that pay a higher transaction cost.
This amendment introduces a fixed-size transaction queue for transactions that were not able to be included in the previous consensus round. If the
rippled servers in the consensus network are under heavy load, they queue the transactions with the lowest transaction cost for later ledgers. Each consensus round prioritizes transactions from the queue with the largest transaction cost (
Fee value), and includes as many transactions as the consensus network can process. If the transaction queue is full, transactions drop from the queue entirely, starting with the ones that have the lowest transaction cost.
While the consensus network is under heavy load, legitimate users can pay a higher transaction cost to make sure their transactions get processed. The situation persists until the entire backlog of cheap transactions is processed or discarded.
A transaction remains in the queue until one of the following happens:
- It gets applied to a validated ledger (regardless of success or failure)
- It becomes invalid (for example, the
LastLedgerSequencecauses it to expire)
- It gets dropped because there are too many transactions in the queue with a higher transaction cost.
Replaces the payment processing engine with a more robust and efficient rewrite called the Flow engine. The new version of the payment processing engine is intended to follow the same rules as the old one, but occasionally produces different results due to floating point rounding. This Amendment supersedes the FlowV2 amendment.
The Flow Engine also makes it easier to improve and expand the payment engine with further Amendments.
Introduces multi-signing as a way to authorize transactions. Creates the
SignerList ledger node type and the
SignerListSet transaction type. Adds the optional
Signers field to all transaction types. Modifies some transaction result codes.
This amendment allows addresses to have a list of signers who can authorize transactions from that address in a multi-signature. The list has a quorum and 1 to 8 weighted signers. This allows various configurations, such as "any 3-of-5" or "signature from A plus any other two signatures."
Signers can be funded or unfunded addresses. Funded addresses in a signer list can sign using a regular key (if defined) or master key (unless disabled). Unfunded addresses can sign with a master key. Multi-signed transactions have the same permissions as transactions signed with a regular key.
An address with a SignerList can disable the master key even if a regular key is not defined. An address with a SignerList can also remove a regular key even if the master key is disabled. The
tecMASTER_DISABLED transaction result code is renamed
tecNO_REGULAR_KEY transaction result is retired and replaced with
tecNO_ALTERNATIVE_KEY. Additionally, this amendment adds the following new transaction result codes:
|9178256A980A86CF3D70D0260A7DA6402AAFE43632FDBCB88037978404188871||Released but not enabled|
Fixes an inconsistency in the way transfer fees are calculated between OfferCreate and Payment transaction types. Without this amendment, the holder of the issuances pays the transfer fee if an offer is executed in offer placement, but the initial sender of a transaction pays the transfer fees for offers that are executed as part of payment processing. With this amendment, the holder of the issuances always pays the transfer fee, regardless of whether the offer is executed as part of a Payment or an OfferCreate transaction. Offer processing outside of payments is unaffected.
This Amendment requires the Flow Amendment to be enabled.
|08DE7D96082187F6E6578530258C77FAABABE4C20474BDB82F04B021F1A68647||Released but not enabled|
Creates "Payment Channels" for XRP. Payment channels are a tool for facilitating repeated, unidirectional payments or temporary credit between two parties. Ripple expects this feature to be useful for the Interledger Protocol. One party creates a Payment Channel and sets aside some XRP in that channel for a predetermined expiration. Then, through off-ledger secure communications, the sender can send "Claim" messages to the receiver. The receiver can redeem the Claim messages before the expiration, or choose not to in case the payment is not needed. The receiver can verify Claims individually without actually distributing them to the network and waiting for the consensus process to redeem them, then redeem the batched content of many small Claims later, as long as it is within the expiration.
Creates three new transaction types:
ChannelClaim. Creates a new ledger node type,
Channel. Defines an off-ledger data structure called a
Claim, used in the ChannelClaim transaction. Creates new
rippled API methods:
channel_authorize (creates a signed Claim),
channel_verify (verifies a signed Claim), and
account_channels (lists Channels associated with an account).
|C6970A8B603D8778783B61C0D445C23D1633CCFAEF0D43E7DBCD1521D34BD7C3||Released but not enabled|
Changes the hash tree structure that
rippled uses to represent a ledger. The new structure is more compact and efficient than the previous version. This affects how ledger hashes are calculated, but has no other user-facing consequences.
|DA1BD556B42D85EA9C84066D028D355B52416734D3283F85E216EA5DA6DB7E13||Released but not enabled
Enabled on TestNet
Provides "Suspended Payments" for XRP for escrow within the Ripple Consensus Ledger. Creates the
SuspendedPayment ledger node type and the new transaction types
The current version is enabled on the Ripple Test Net.
Allows pre-authorization of accounting relationships (zero-balance trust lines) when using Authorized Accounts.
With this amendment enabled, a
TrustSet transaction with
tfSetfAuth enabled can create a new
RippleState ledger node even if it keeps all the other values of the
RippleState node in their default state. The new
RippleState node has the
lsfHighAuth flag enabled, depending on whether the sender of the transaction is considered the low node or the high node. The sender of the transaction must have already enabled
lsfRequireAuth by sending an AccountSet transaction with the asfRequireAuth flag enabled.
Introduces Tickets as a way to reserve a transaction sequence number for later execution. Creates the
Ticket ledger node type and the transaction types
Caution: This amendment is still in development.