Reorg payment system basics category

content/concepts/payment-system-basics/accounts/multi-signing.md

@@ -1,6 +1,6 @@
 # Multi-Signing
 
-Multi-signing is one of three ways to authorize transactions for the XRP Ledger, alongside signing with [regular keys and master keys](cryptographic-keys.html). You can configure your address to allow any combination of the three methods to authorize transactions.
+Multi-signing in the XRP Ledger is a method of [authorizing transactions](#authorizing-transactions) for the XRP Ledger by using a combination of multiple secret keys. You can have any combination of authorization methods enabled for your address, including multi-signing, a [master key pair](concept-cryptographic-keys.html#master-key-pair), and a [regular key pair](concept-cryptographic-keys.html#regular-key-pair). (The only requirement is that _at least one_ method must be enabled.)
 
 Benefits of multi-signing include:
 
@@ -9,4 +9,23 @@ Benefits of multi-signing include:
 * You can delegate the power to send transactions from your address to a group of people, who can control your address if you are unavailable or unable to sign normally.
 * ... and more.
 
-<!--{# TODO: Expand this and add it to the dactyl-config #}-->
+## Signer Lists
+
+Before you can multi-sign, you must create a list of which addresses can sign for you.
+
+The [SignerListSet transaction][] defines which addresses can authorize transactions from your address. You can include up to 8 addresses in a SignerList. You can control how many signatures are needed, in which combinations, by using the quorum and weight values of the SignerList.
+
+## Sending Multi-Signed Transactions
+
+To successfully submit a multi-signed transaction, you must do all of the following:
+
+* The address sending the transaction (specified in the `Account` field) must own a [`SignerList` in the ledger](reference-ledger-format.html#signerlist).
+* The transaction must include the `SigningPubKey` field as an empty string.
+* The transaction must include a [`Signers` field](#signers-field) containing an array of signatures.
+* The signatures present in the `Signers` array must match signers defined in the SignerList.
+* For the provided signatures, the total `weight` associated with those signers must be equal or greater than the `quorum` for the SignerList.
+* The [transaction cost](concept-transaction-cost.html) (specified in the `Fee` field) must be at least (N+1) times the normal transaction cost, where N is the number of signatures provided.
+* All fields of the transaction must be defined before collecting signatures. You cannot [auto-fill](#auto-fillable-fields) any fields.
+* If presented in binary form, the `Signers` array must be sorted based on the numeric value of the signer addresses, with the lowest value first. (If submitted as JSON, the [submit_multisigned method][] handles this automatically.)
+
+For more information, see [How to Multi-Sign](how-to-multi-sign.html).