ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-12-06 01:07:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2556 from XRPLF/amm-flag-updates

Browse Source 
AMM Flag Updates
This commit is contained in:
oeggert
2024-05-06 13:15:16 -07:00
committed by GitHub
parent f0153301dc 8ee8f2b72d
commit 067ec1d084
4 changed files with 16 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
docs/references/protocol/ledger-data/ledger-entry-types/ripplestate.md
View File

@@ -73,6 +73,7 @@ In addition to the [common fields](../common-fields.md), {% code-page-name /%} e
| Flag Name | Hex Value | Decimal Value | Corresponding [TrustSet Flag](../../transactions/types/trustset.md#trustset-flags) | Description |
|-------------------|--------------|---------------|-----------------|---------|
| `lsfAMMNode` | `0x01000000` | 16777216 | (None) | This entry consumed AMM liquidity to complete a [`Payment`](../../transactions/types/payment.md) transaction. |
| `lsfLowReserve` | `0x00010000` | 65536 | (None) | This entry [contributes to the low account's owner reserve](#ripplestate-reserve). |
| `lsfHighReserve` | `0x00020000` | 131072 | (None) | This entry [contributes to the high account's owner reserve](#ripplestate-reserve). |
| `lsfLowAuth` | `0x00040000` | 262144 | `tfSetAuth` | The low account has authorized the high account to hold tokens issued by the low account. |

2
docs/references/protocol/transactions/types/payment.md
View File

@@ -88,7 +88,7 @@ For more information, see [Accounts](../../../../concepts/accounts/index.md#crea
## Paths
If present, the `Paths` field must contain a _path set_ - an array of path arrays. Each individual path represents one way value can flow from the sender to receiver through various intermediary accounts and order books. A single transaction can potentially use multiple paths, for example if the transaction exchanges currency using several different order books to achieve the best rate.
If present, the `Paths` field must contain a _path set_ - an array of path arrays. Each individual path represents one way value can flow from the sender to receiver through various intermediary accounts, order books, and automated market makers. A single transaction can potentially use multiple paths, for example if the transaction exchanges currency using several different order books to achieve the best rate.
You must omit the `Paths` field for direct payments, including: