mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-12-02 01:25:50 +00:00
Fix some filename/URL issues.
- Change transaction-results/transaction-results/ to not repeat itself, adding a redirect from the old URL. - Fix Japanese localization of 'tasks' not being updated to 'how-tos'. (Translated pages in this subfolder were not being shown as translated due to the mismatch.) - Fix unparsed `[base58][]` link in addresses snippet.
This commit is contained in:
@@ -1114,7 +1114,7 @@ This amendment allows addresses to have a list of signers who can authorize tran
|
||||
|
||||
Signers can be funded or unfunded addresses. Funded addresses in a signer list can sign using a regular key (if defined) or master key (unless disabled). Unfunded addresses can sign with a master key. Multi-signed transactions have the same permissions as transactions signed with a regular key.
|
||||
|
||||
An address with a SignerList can disable the master key even if a regular key is not defined. An address with a SignerList can also remove a regular key even if the master key is disabled. The `tecMASTER_DISABLED` transaction result code is renamed `tecNO_ALTERNATIVE_KEY`. The `tecNO_REGULAR_KEY` transaction result is retired and replaced with `tecNO_ALTERNATIVE_KEY`. Additionally, this amendment adds the following new [transaction result codes](../docs/references/protocol/transactions/transaction-results/transaction-results.md):
|
||||
An address with a SignerList can disable the master key even if a regular key is not defined. An address with a SignerList can also remove a regular key even if the master key is disabled. The `tecMASTER_DISABLED` transaction result code is renamed `tecNO_ALTERNATIVE_KEY`. The `tecNO_REGULAR_KEY` transaction result is retired and replaced with `tecNO_ALTERNATIVE_KEY`. Additionally, this amendment adds the following new [transaction result codes](../docs/references/protocol/transactions/transaction-results/index.md):
|
||||
|
||||
* `temBAD_SIGNER`
|
||||
* `temBAD_QUORUM`
|
||||
|
||||
Reference in New Issue
Block a user