The unique address of the transaction sender.
Optional AccountHash value identifying another transaction. If provided, this transaction is only valid if the sending account's previously-sent transaction matches the provided hash.
The definition for one of the assets in the AMM's pool.
The definition for the other asset in the AMM's pool.
Optional FeeInteger 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.
Optional FlagsSet of bit-flags for this transaction.
Optional LastHighest 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.
Optional MemosAdditional arbitrary information used to identify this transaction.
Optional NetworkIDThe network id of the transaction.
Optional SequenceThe 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.
Optional SignersArray of objects that represent a multi-signature which authorizes this transaction.
Optional SigningHex 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.
Optional SourceArbitrary 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.
Optional TicketThe 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 proposed fee to vote for, in units of 1/100,000; a value of 1 is equivalent to 0.001%. The maximum value is 1000, indicating a 1% fee.
The type of transaction. Valid types include: Payment, OfferCreate,
TrustSet, and many others.
Optional TxnThe signature that verifies this transaction as originating from the account it says it is from.
Generated using TypeDoc
Vote on the trading fee for an Automated Market Maker (AMM) instance.
Up to 8 accounts can vote in proportion to the amount of the AMM's LP Tokens they hold. Each new vote re-calculates the AMM's trading fee based on a weighted average of the votes.