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.
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 NFTokenThis field is only valid in brokered mode. It specifies the amount that the broker will keep as part of their fee for bringing the two offers together; the remaining amount will be sent to the seller of the NFToken being bought. If specified, the fee must be such that, prior to accounting for the transfer fee charged by the issuer, the amount that the seller would receive is at least as much as the amount indicated in the sell offer.
This functionality is intended to allow the owner of an NFToken to offer their token for sale to a third party broker, who may then attempt to sell the NFToken on for a larger amount, without the broker having to own the NFToken or custody funds.
Note: in brokered mode, the offers referenced by NFTokenBuyOffer and NFTokenSellOffer must both specify the same NFTokenID; that is, both must be for the same NFToken.
Optional NFTokenIdentifies the NFTokenOffer that offers to buy the NFToken.
In direct mode this field is optional, but either NFTokenSellOffer or NFTokenBuyOffer must be specified. In brokered mode, both NFTokenSellOffer and NFTokenBuyOffer must be specified.
Optional NFTokenIdentifies the NFTokenOffer that offers to sell the NFToken.
In direct mode this field is optional, but either NFTokenSellOffer or NFTokenBuyOffer must be specified. In brokered mode, both NFTokenSellOffer and NFTokenBuyOffer must be specified.
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 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
The NFTokenOfferAccept transaction is used to accept offers to buy or sell an NFToken. It can either:
To indicate direct mode, use either the
sell_offerorbuy_offerfields, but not both. To indicate brokered mode, use both thesell_offerandbuy_offerfields. If you use neithersell_offernorbuy_offer, the transaction is invalid.