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

Remove warning about fixMasterKeyAsRegularKey

Browse Source 
This warning isn't relevant anymore given that the amendment is now enabled -> https://xrpl.org/known-amendments.html#fixmasterkeyasregularkey
This commit is contained in:
Joseph Busch
2020-01-08 00:32:59 -06:00
committed by GitHub
parent 781f5bd6e9
commit c90e70a0b2
1 changed files with 0 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -25,8 +25,6 @@ You can protect your account by assigning a regular key pair to it and using it
|:-------------|:----------|:------------------|:------------------------------|
| `RegularKey` | String | AccountID | _(Optional)_ A base-58-encoded [Address][] that indicates the regular key pair to be assigned to the account. If omitted, removes any existing regular key pair from the account. Must not match the master key pair for the address. |
**Warning:** Until the [fixMasterKeyAsRegularKey amendment][] :not_enabled: becomes enabled, it is possible to set your regular key to match your master key. If you then disable the master key, your address cannot send transactions signed with the key even though it matches the enabled regular key. As a result, you cannot send any transactions from the address unless you have [multi-signing](multi-signing.html) enabled and use that. With the amendment enabled, such "blocked" accounts can send transactions again.
## See Also
For more information about regular and master key pairs, see [Cryptographic Keys](cryptographic-keys.html).