What XRP Ledger features can protect my account (regular keys, multi-signing, disabling the master key)?

The full answer

What do the cited sources say about regular keys, multi-signing and the master key?

The official XRP Ledger documentation describes all three. It says an account can have any combination of authorization methods enabled, including multi-signing, a master key pair and a regular key pair [2]. A regular key pair is assigned to an account with a SetRegularKey transaction [5]. Multi-signing is set up with a SignerListSet transaction, which sets the total weight needed for a quorum and the list of signers with their individual weights [3]. Before the master key pair can be disabled, the account must have another way of authorizing transactions, either a regular key pair or a multi-signing list [4]. The documentation also describes keeping a multi-signing list as a backup plan while the account owner normally uses a regular key for their transactions [2].

How do I set up a regular key step by step, and test it before disabling the master key?

The XRP Ledger documentation sets out the steps. A new key pair is assigned to the account as its regular key pair with a SetRegularKey transaction [5]. To test the key, the documentation says to send any type of transaction signed with the regular key pair; its sample code sends an AccountSet transaction with no parameters, which does nothing besides use a sequence number and burn the transaction cost [5]. It says that, to avoid losing control of the account, it is important to test the regular key before taking any additional steps such as disabling the master key pair [5]. The master key pair is disabled by sending an AccountSet transaction with the SetFlag value set to asfDisableMaster, and unlike most transactions this one must be signed with the master key pair [4]. The account_info method can then confirm the change through the disableMasterKey field of the account flags [4]. The related question of signing on a device that never touches the internet is covered on What is air-gapped signing, and do I need it?.

Which consumer wallets support these features?

This was not verified as of September 30, 2026. No wallet maker’s documentation on regular keys, multi-signing or master-key settings has been checked. How to judge a wallet’s own claims is covered on Which wallet is best for XRP, and how do I choose one without getting a fake or flawed one?.

What related signing feature has been proposed but is not live?

One proposal touches the same problem of who can sign for an account. Jake Claver wrote on August 28, 2026 that PermissionDelegationV1_1 would let an account grant narrowly scoped signing authority to another account without handing over full control [1]. In the same piece he reported that PermissionDelegationV1_1, introduced in the 3.3.0 release, was not enabled on mainnet [1]. Claver also reported that one of the six amendments in the 3.3.0 release, a maintenance fix named fixCleanup3_3_0, reached the 80 percent validator threshold on August 28, 2026 and was scheduled to activate on September 11.

The ledger’s amendment process explains why. Claver wrote that an amendment needs support from at least 80 percent of trusted validators, continuously, for two weeks [1]. He also wrote that shipping in a release does not mean a feature is live, and that independent validators, not the company that wrote the code, decide the gap between the two [1]. Crypto.news reported that, under XRPL’s official amendment rules, installing software containing an amendment only gives a server the code needed to understand the proposed rules, and validators separately choose whether to vote for activation. It also reported that a default-no setting means running the software does not itself cast an affirmative amendment vote when an operator has not configured another choice. No later status for this amendment is known from the cited sources as of September 30, 2026. The wider approval process is explained on How do XRP Ledger upgrades (amendments) get approved, and who decides?.

What could go wrong with account-level controls, and where is that covered?

The XRP Ledger documentation warns that, due to the decentralized nature of the XRP Ledger, there is no one who can restore access to an account if something goes wrong [4]. The wider case against relying on any single safeguard, including losses caused by a holder’s own mistakes, is set out on Can I lose my XRP without anyone hacking me?. Whether shared signing can help a family reach an account after a death is taken up on What happens to my XRP when I die?. Whether any account setting would have changed the outcome of the September 2026 wallet drain is examined on What happened with the D’CENT wallet hack, and am I affected?.