ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-20 19:55:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'amm_concept'

Browse Source
This commit is contained in:
mDuo13
2022-12-16 14:05:00 -08:00
parent e3328ddaa7 7429867ba2
commit daeabe6c9d
19 changed files with 434 additions and 53 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/references/protocol-reference/ledger-data/ledger-object-types/accountroot.ja.md
View File

@@ -61,7 +61,7 @@ labels:
{% include '_snippets/amm-disclaimer.md' %}
Automated Market Makers (AMMs) use an AccountRoot object to issue their LP Tokens and hold the assets in the AMM pool, in addition to the [AMM object][] for tracking some of the details of the AMM. The address of an AMM's associated AccountRoot is randomized so that users cannot identify and fund the address in advance of the AMM being created. Unlike normal accounts, AMM AccountRoots are created with the following settings:
[Automated Market Makers](automated-market-makers.html) (AMMs) use an AccountRoot object to issue their LP Tokens and hold the assets in the AMM pool, in addition to the [AMM object][] for tracking some of the details of the AMM. The address of an AMM's associated AccountRoot is randomized so that users cannot identify and fund the address in advance of the AMM being created. Unlike normal accounts, AMM AccountRoots are created with the following settings:
- `lsfAMM` **enabled**. This indicates that the AccountRoot is part of an AMM and is not a regular account.
- `lsfDisableMaster` **enabled** and no other means of authorizing transactions. This ensures no one can control the account directly, and it cannot send transactions.

2
content/references/protocol-reference/ledger-data/ledger-object-types/accountroot.md
View File

@@ -85,7 +85,7 @@ AccountRoot objects can have the following flag values:
{% include '_snippets/amm-disclaimer.md' %}
Automated Market Makers (AMMs) use an AccountRoot object to issue their LP Tokens and hold the assets in the AMM pool, and an [AMM object][] for tracking some of the details of the AMM. The address of an AMM's associated AccountRoot is randomized so that users cannot identify and fund the address in advance of the AMM being created. Unlike normal accounts, AMM AccountRoot objects are created with the following settings:
[Automated Market Makers](automated-market-makers.html) (AMMs) use an AccountRoot object to issue their LP Tokens and hold the assets in the AMM pool, and an [AMM object][] for tracking some of the details of the AMM. The address of an AMM's AccountRoot is randomized so that users cannot identify and fund the address in advance of the AMM being created. Unlike normal accounts, AMM AccountRoot objects are created with the following settings:
- `lsfAMM` **enabled**. This indicates that the AccountRoot is part of an AMM and is not a regular account.
- `lsfDisableMaster` **enabled** and no other means of authorizing transactions. This ensures no one can control the account directly, and it cannot send transactions.

2
content/references/protocol-reference/ledger-data/ledger-object-types/amm.md
View File

@@ -12,7 +12,7 @@ status: not_enabled
{% include '_snippets/amm-disclaimer.md' %}
The `AMM` object type describes a single Automated Market Maker (AMM) instance.
The `AMM` object type describes a single [Automated Market Maker](automated-market-makers.html) (AMM) instance.
## Example AMM JSON