Definition and scope
What Is an XRPL Regular Key? addresses a distinct part of accounts and wallet controls. Use a rotatable signing key while retaining the account's intrinsic master-key recovery path.
An XRPL account is a ledger object controlled by cryptographic authorization—not an app login. These topics explain how accounts begin, how transactions are ordered, and how master keys, regular keys, signer lists, and domain settings change operational control. Authorization changes should be rehearsed with independent recovery paths. No guide requires sharing a seed, family secret, or private key.
How it works
A RegularKey is an alternate key pair authorized by an AccountSet transaction. It can sign for the account while the master key remains a recovery authority unless master-key signing is explicitly disabled.
- RegularKey: verify this field, object, or component against the cited protocol documentation.
- AccountSet: verify this field, object, or component against the cited protocol documentation.
- master key: verify this field, object, or component against the cited protocol documentation.
- key rotation: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
Keep the master secret offline, assign a RegularKey to a controlled signing device, validate the change, and rotate the regular key if that device is retired or suspected compromised.
For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.
Open the related live demo or evidence lab →Limits, risks, and common confusion
A regular key changes signing authority, not the public address. Assigning a compromised or incorrectly recorded key can interrupt operations, and disabling the master key removes an important recovery path.
Authorization changes should be rehearsed with independent recovery paths. No guide requires sharing a seed, family secret, or private key.
Current network status
Enabled on XRPL Mainnet. The underlying protocol capability is available on XRPL Mainnet. Individual services can still impose additional rules, limits, or trust assumptions.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.