Class NFTokenAcceptOffer

The NFTokenOfferAccept transaction is used to accept offers to buy or sell an NFToken.
It can either:
1.
Allow one offer to be accepted.
This is called direct mode.
2.
Allow two distinct offers, one offering to buy a given NFToken and the other offering to sell the same NFToken, to be accepted in an atomic fashion.
This is called brokered mode.
To indicate direct mode, use either the sell_offer or buy_offer fields, but not both.
To indicate brokered mode, use both the sell_offer and buy_offer fields.
If you use neither sell_offer nor buy_offer, the transaction is invalid.

Inheritance
object
TransactionRequest
NFTokenAcceptOffer
Implements
Inherited Members
Namespace: Xrpl.Models.Transactions
Assembly: Xrpl.dll
Syntax
public class NFTokenAcceptOffer : TransactionRequest, ITransactionRequest, INFTokenAcceptOffer, ITransactionCommon

Constructors

| Edit this page View Source

NFTokenAcceptOffer()

Declaration
public NFTokenAcceptOffer()

Properties

| Edit this page View Source

NFTokenBrokerFee

This 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.

Declaration
[JsonConverter(typeof(CurrencyConverter))]
public Currency NFTokenBrokerFee { get; set; }
Property Value
Type Description
Currency
Remarks

The transaction itself carries no NFTokenID field - the token is whichever one both offers are for. Brokered mode also needs three distinct accounts: rippled checks the owner of each offer against the submitter separately, not as alternatives, so a broker who is also the buyer or the seller gets tecCANT_ACCEPT_OWN_NFTOKEN_OFFER. The two blocks in its preclaim read like a choice between direct and brokered mode and are not one - both run in brokered mode.

| Edit this page View Source

NFTokenBuyOffer

Identifies 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.

Declaration
public string NFTokenBuyOffer { get; set; }
Property Value
Type Description
string
| Edit this page View Source

NFTokenSellOffer

Identifies 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.

Declaration
public string NFTokenSellOffer { get; set; }
Property Value
Type Description
string

Implements

Extension Methods