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

Fix stray amendment status icons

Browse Source
This commit is contained in:
mDuo13
2019-03-06 14:16:41 -08:00
parent 4f28ea49dd
commit fe67efe92e
5 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
content/references/rippled-api/ledger-data-formats/ledger-object-types/signerlist.md
View File

@@ -71,7 +71,7 @@ When processing a multi-signed transaction, the server dereferences the `Account
## {{currentpage.name}} Flags
_((NOT_ENABLED_ICON) Requires the [MultiSignReserve amendment][].)_
_(Requires the [MultiSignReserve amendment][] :not_enabled:.)_
SignerList objects can have the following flag value:
@@ -83,9 +83,9 @@ SignerList objects can have the following flag value:
A SignerList contributes to its owner's [reserve requirement](reserves.html).
Without the [MultiSignReserve amendment][], the SignerList itself counts as two objects, and each member of the list counts as one. As a result, the total owner reserve associated with a SignerList is anywhere from 3 times to 10 times the reserve required by a single trust line ([RippleState](ripplestate.html)) or [Offer](offer.html) object in the ledger.
Without the [MultiSignReserve amendment][] :not_enabled:, the SignerList itself counts as two objects, and each member of the list counts as one. As a result, the total owner reserve associated with a SignerList is anywhere from 3 times to 10 times the reserve required by a single trust line ([RippleState](ripplestate.html)) or [Offer](offer.html) object in the ledger.
(NOT_ENABLED_ICON) With the [MultiSignReserve amendment][] enabled, the SignerList counts as one object, regardless of how many members it has. As a result, the owner reserve associated with a SignerList is 5 XRP, regardless of how many members it has.
With the [MultiSignReserve amendment][] :not_enabled: enabled, the SignerList counts as one object, regardless of how many members it has. As a result, the owner reserve associated with a SignerList is 5 XRP, regardless of how many members it has.
The reserve requirement does not change for SignerLists created before the MultiSignReserve amendment. To take advantage of the new reserve, update the SignerList by sending a [SignerListSet transaction][].