The unique address of the transaction sender.
OptionalAccountHash value identifying another transaction. If provided, this transaction is only valid if the sending account's previously-sent transaction matches the provided hash.
OptionalAmountIndicates the amount expected for the Token.
The amount can be zero. This would indicate that the account is giving the token away free, either to anyone at all, or to the account identified by the Destination field.
OptionalDelegateThe delegate account that is sending the transaction.
OptionalDestinationIf present, indicates that this offer may only be accepted by the specified account. Attempts by other accounts to accept this offer MUST fail.
OptionalExpirationIndicates the time after which the offer will no longer be valid. The value is the number of seconds since the Ripple Epoch.
OptionalFeeInteger 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.
OptionalFlagsSet of bit-flags for this transaction.
OptionalIssuerIndicates the account that should be the issuer of this token. This value
is optional and should only be specified if the account executing the
transaction is not the Issuer of the NFToken object. If it is
present, the MintAccount field in the AccountRoot of the Issuer
field must match the Account, otherwise the transaction will fail.
OptionalLastHighest 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.
OptionalMemosAdditional arbitrary information used to identify this transaction.
OptionalNetworkThe network id of the transaction.
Indicates the taxon associated with this token. The taxon is generally a value chosen by the minter of the token and a given taxon may be used for multiple tokens. The implementation reserves taxon identifiers greater than or equal to 2147483648 (0x80000000). If you have no use for this field, set it to 0.
OptionalSequenceThe 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.
OptionalSignersArray of objects that represent a multi-signature which authorizes this transaction.
OptionalSigningHex 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.
OptionalSourceArbitrary 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.
OptionalTicketThe 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.
OptionalTransferSpecifies the fee charged by the issuer for secondary sales of the Token,
if such sales are allowed. Valid values for this field are between 0 and
50000 inclusive, allowing transfer rates between 0.000% and 50.000% in
increments of 0.001%. This field must NOT be present if the
tfTransferable flag is not set.
OptionalTxnThe signature that verifies this transaction as originating from the account it says it is from.
OptionalURIURI that points to the data and/or metadata associated with the NFT. This field need not be an HTTP or HTTPS URL; it could be an IPFS URI, a magnet link, immediate data encoded as an RFC2379 "data" URL, or even an opaque issuer-specific encoding. The URI is NOT checked for validity, but the field is limited to a maximum length of 256 bytes.
This field must be hex-encoded. You can use convertStringToHex to
convert this field to the proper encoding.
This field must not be an empty string. Omit it from the transaction or
set to undefined value if you do not use it.
The NFTokenMint transaction creates an NFToken object and adds it to the relevant NFTokenPage object of the minter. If the transaction is successful, the newly minted token will be owned by the minter account specified by the transaction.