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

inc'd feedback

Browse Source
This commit is contained in:
Jennifer Hasegawa
2019-01-29 09:56:40 -08:00
parent 64cbef142d
commit e9c0937eef
3 changed files with 11 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -45,7 +45,7 @@ A `SignerList` object has the following fields:
| Name | JSON Type | Internal Type | Description |
|:--------------------|:----------|:--------------|:---------------------------|
| `LedgerEntryType` | String | UInt16 | The value `0x0053`, mapped to the string `SignerList`, indicates that this object is a SignerList object. |
| `Flags` | Number | UInt32 | A bit-map of boolean flags. Without the [MultiSignReserve amendment](known-amendments.html#multisignreserve), no flags are defined for the SignerList type, so this value is always 0. With the [MultiSignReserve amendment](known-amendments.html#multisignreserve) enabled, a flag is defined for the SignerList type, so this value can be bit-map of a boolean flag enabled for this account. |
| `Flags` | Number | UInt32 | A bit-map of Boolean flags enabled for this SignerList. For more information, see [SignerList Flags](#signerlist-flags). |
| `PreviousTxnID` | String | Hash256 | The identifying hash of the transaction that most recently modified this object. |
| `PreviousTxnLgrSeq` | Number | UInt32 | The [index of the ledger][Ledger Index] that contains the transaction that most recently modified this object. |
| `OwnerNode` | String | UInt64 | A hint indicating which page of the owner directory links to this object, in case the directory consists of multiple pages. |
@@ -66,7 +66,7 @@ Each member of the `SignerEntries` field is an object that describes that signer
When processing a multi-signed transaction, the server dereferences the `Account` values with respect to the ledger at the time of transaction execution. If the address _does not_ correspond to a funded [AccountRoot object](accountroot.html), then only the master secret associated with that address can be used to produce a valid signature. If the account _does_ exist in the ledger, then it depends on the state of that account. If the account has a Regular Key configured, the Regular Key can be used. The account's master key can only be used if it is not disabled. A multi-signature cannot be used as part of another multi-signature.
## {{currentpage.name}} Flag
## {{currentpage.name}} Flags
_Requires the [MultiSignReserve Amendment](known-amendments.html#multisignreserve)._
@@ -74,7 +74,7 @@ SignerList objects can have the following flag value:
| Flag Name | Hex Value | Decimal Value | Description |
|:-----------------|:-----------|:--------------|:-------------------------------|
| lsfOneOwnerCount | 0x00010000 | 65536 | This flag is set by the [SignerListSet transaction](signerlistset.html) when you create a new SignerList, or replace or remove a SignerList that was created before the MultiSignReserve amendment was enabled. Setting this flag enables the XRP Ledger to lower the [`OwnerCount`](accountroot.html#accountroot-fields) and [owner reserve](reserves.html#owner-reserves) for a SignerList as provided by the MultiSignReserve amendment. For example, when you create a SignerList after the MultiSignReserve amendment is enabled, this flag is set, your `OwnerCount` is increased by 1, and your owner reserve is increased by 5 XRP. When you replace a SignerList that was created before the MultiSignReserve amendment was enabled, this flag is set, your `OwnerCount` and owner reserve for the replaced SignerList are removed, your `OwnerCount` is increased by 1, and your owner reserve is increased by 5 XRP. When you remove a SignerList that was created before the MultiSignReserve amendment was enabled, this flag is set and your `OwnerCount` and owner reserve for the SignerList you removed are removed. |
| lsfOneOwnerCount | 0x00010000 | 65536 | If this flag is enabled, this SignerList counts as one item for purposes of the [owner reserve](reserves.html#owner-reserves). Otherwise, this list counts as N+2 items, where N is the number of signers it contains. This flag is automatically enabled if you add or update a signer list after the [MultiSignReserve amendment](known-amendments.html#multisignreserve) is enabled. |
## SignerLists and Reserves
@@ -84,6 +84,8 @@ Without the [MultiSignReserve Amendment](known-amendments.html#multisignreserve)
With the [MultiSignReserve Amendment](known-amendments.html#multisignreserve) 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][].
## SignerList ID Format
The ID of a SignerList object is the SHA-512Half of the following values, concatenated in order:

2
content/references/rippled-api/transaction-formats/transaction-types/signerlistset.md
View File

@@ -51,7 +51,7 @@ You can create, update, or remove a SignerList using the master key, regular key
You cannot remove the last method of signing transactions from an account. If an account's master key is disabled (it has the [`lsfDisableMaster` flag](accountroot.html#accountroot-flags) enabled) and the account does not have a [Regular Key](cryptographic-keys.html) configured, then you cannot delete the SignerList from the account. Instead, the transaction fails with the error [`tecNO_ALTERNATIVE_KEY`](tec-codes.html).
With the [MultiSignReserve Amendment](known-amendments.html#multisignreserve) enabled, creating a SignerList, or replacing or removing a SignerList that was created before the MultiSignReserve amendment was enabled, sets the lsfOneOwnerCount flag on the SignerList object. When this flag is set, the XRP Ledger is able to lower the [`OwnerCount`](accountroot.html#accountroot-fields) and [owner reserve](reserves.html#owner-reserves) for a SignerList as provided by the MultiSignReserve amendment. For more information, see [SignerList Flag](signerlist.html#signerlist-flag).
With the [MultiSignReserve Amendment](known-amendments.html#multisignreserve) enabled, creating or replacing a SignerList enables the lsfOneOwnerCount flag on the SignerList object. When this flag is enabled, the XRP Ledger is able to lower the [`OwnerCount`](accountroot.html#accountroot-fields) and [owner reserve](reserves.html#owner-reserves) for a SignerList as provided by the MultiSignReserve amendment. For more information, see [SignerList Flag](signerlist.html#signerlist-flag).
<!--{# common link defs #}-->
{% include '_snippets/rippled-api-links.md' %}

6
content/tutorials/manage-account-settings/set-up-multi-signing.md
View File

@@ -16,7 +16,11 @@ This tutorial demonstrates how to enable multi-signing for an address.
## 1. Prepare a funded address
You need an XRP Ledger address that can send transactions, and has enough XRP available. Without the [MultiSignReserve Amendment](known-amendments.html#multisignreserve), multi-signing requires more than the usual amount of XRP for the [account reserve](reserves.html) and [transaction cost](transaction-cost.html), increasing with the number of signers and signatures you use. With the [MultiSignReserve Amendment](known-amendments.html#multisignreserve) enabled, multi-signing requires 5 XRP for the account reserve, regardless of the number of signers and signatures you use.
You need an XRP Ledger address that can send transactions, and has enough XRP available.
Without the [MultiSignReserve Amendment](known-amendments.html#multisignreserve), multi-signing requires more than the usual amount of XRP for the [account reserve](reserves.html) and [transaction cost](transaction-cost.html), increasing with the number of signers and signatures you use.
With the [MultiSignReserve Amendment](known-amendments.html#multisignreserve) enabled, multi-signing requires 5 XRP for the account reserve, regardless of the number of signers and signatures you use. The [transaction cost](transaction-cost.html) of a multi-signed transaction is unaffected by this amendment and still increases with the number of signers and signatures you use.
If you started `rippled` in [stand-alone mode](rippled-server-modes.html#reasons-to-run-a-rippled-server-in-stand-alone-mode) with a new genesis ledger, you must: