ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-27 23:25:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update to match style guide.

Browse Source
This commit is contained in:
Oliver Eggert
2023-01-15 20:45:23 -08:00
parent 823781b085
commit 58df747093
1 changed files with 13 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
content/references/protocol-reference/transactions/pseudo-transaction-types/enableamendment.md
View File

@@ -7,14 +7,22 @@ labels:
---
# EnableAmendment
An `EnableAmendment` [pseudo-transaction](pseudo-transaction-types.html) marks a change in status of an [amendment](amendments.html) to the XRP Ledger protocol, including:
An `EnableAmendment` pseudo-transaction marks a change in the status of a proposed amendment when it:
- A proposed amendment gained supermajority approval from validators.
- A proposed amendment lost supermajority approval.
- A proposed amendment has been enabled.
- Gains supermajority approval from validators.
- Loses supermajority approval.
- Is enabled on the XRP Ledger protocol.
**Note:** You cannot send a pseudo-transaction, but you may find one when processing ledgers.
<!-- TODO: Move to propose amendments tutorial.
A server only enables amendments when these conditions are met:
- A previous ledger includes an `EnableAmendment` pseudo-transaction with the `tfGotMajority` flag enabled.
- 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 `tfLostMajority` flag enabled in the consensus ledgers between the `tfGotMajority` pseudo-transaction and the current ledger.
-->
## Example {{currentpage.name}} JSON