The NFTokenCreateOffer transaction creates either an offer to buy an NFT the submitting account does not own, or an offer to sell an NFT the submitting account does own.
-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.
-Indicates the amount expected or offered for the Token.
The amount must be non-zero, except when this is a sell offer and the asset is XRP. This would indicate that the current owner of the token is giving it away free, either to anyone at all, or to the account identified by the Destination field.
-If present, indicates that this offer may only be accepted by the specified account. Attempts by other accounts to accept this offer MUST fail.
-Indicates the time after which the offer will no longer be valid. The value is the number of seconds since the Ripple Epoch.
-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.
-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.
-Identifies the NFTokenID of the NFToken object that the offer references.
-Indicates the AccountID of the account that owns the corresponding NFToken.
If the offer is to buy a token, this field must be present @@ -45,27 +45,27 @@ buy a token one already holds is meaningless).
present, as the owner is, implicitly, the same as Account (since an offer to sell a token one doesn't already hold is meaningless). -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