A SetRegularKey transaction assigns, changes, or removes the regular key pair associated with an account.
The unique address of the account that initiated the transaction.
Hash value identifying another transaction. If provided, this transaction is only valid if the sending account's previously-sent transaction matches the provided hash.
Integer amount of XRP, in drops, to be destroyed as a cost for distributing this transaction to the network. Some transaction types have different minimum requirements.
Set of bit-flags for this transaction.
Highest ledger index this transaction can appear in. Specifying this field places a strict upper limit on how long the transaction can wait to be validated or rejected.
Additional arbitrary information used to identify this transaction.
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.
The sequence number of the account sending the transaction. A transaction is only valid if the Sequence number is exactly 1 greater than the previous transaction from the same account. The special case 0 means the transaction is using a Ticket instead.
Array of objects that represent a multi-signature which authorizes this transaction.
Hex representation of the public key that corresponds to the private key used to sign this transaction. If an empty string, indicates a multi-signature is present in the Signers field instead.
Arbitrary integer used to identify the reason for this payment, or a sender on whose behalf this transaction is made. Conventionally, a refund should specify the initial payment's SourceTag as the refund payment's DestinationTag.
The sequence number of the ticket to use in place of a Sequence number. If this is provided, Sequence must be 0. Cannot be used with AccountTxnID.
The signature that verifies this transaction as originating from the account it says it is from.
Generated using TypeDoc