Looksrare fees differ by order and must be separated from network gas when comparing NFT trades

Looksrare fees are not one fixed amount. A completed NFT trade can include a protocol deduction from the execution price, a creator fee when the matched order applies one, and gas paid by the wallet that submits an on-chain transaction. Buyers should compare the displayed payment plus estimated gas, while sellers should compare the execution price with their expected proceeds. The receipt and its decoded events then replace those estimates with the recorded gas fields and settlement transfers.

In short: Compare the execution price, seller deductions, and estimated gas before submitting a transaction, then use its receipt to reconcile the final amounts.

Three Cost Layers Behind One Sale

Trade cost has three distinct layers, and they do not necessarily affect the same wallet. Keeping them separate prevents a listed price from being mistaken for a final total.

Protocol Deduction

Looksrare V2 assigns the standard, minimum total, and maximum protocol fee parameters at the execution-strategy level. An order without a creator fee uses the strategy’s minimum total fee as its protocol fee. When a creator fee applies, the protocol starts with the standard fee and raises it if the combined fees would otherwise fall below that minimum. Read the resulting deduction from the live trade details rather than inferring it from an old marketplace rate. The protocol deducts this amount during settlement before calculating the remaining sale proceeds.

Creator Payment

A creator fee may be added to the settlement allocation when the selected collection and order support one. Looksrare V2 can determine creator fee information through its royalty registry or the ERC-2981 royalty standard. The recipient may be a creator address rather than the seller. Its presence, rate, and recipient should match the details shown for the order being executed.

Network Execution

Network gas pays for computation that records an approval, purchase, offer acceptance, or cancellation. The wallet submitting that transaction pays the gas in the network’s native currency. Gas is separate from the NFT price and does not become seller revenue. Its final amount depends on gas used and the effective price per unit when the transaction executes.

Fee Rules Attached to the Selected Order

Each quote should be tied to one order, currency, source, and execution path. A collection page may display similar NFTs whose settlement rules differ, especially when listings originate from more than one marketplace. The displayed floor or card price cannot establish the deductions for every available order.

A useful comparison keeps the following fields attached to each candidate:

• The execution price and payment currency
• The order source and execution strategy
• Any protocol and creator deductions
• The wallet responsible for the on-chain action
• The estimated gas and any preceding approval transaction

Refreshing the quote can change one or more of these fields without changing the NFT itself. Use the refreshed quote for comparison because it reflects the order selected at refresh time.

Which Total Matters to Buyers and Sellers?

Buyers need the payable amount plus buyer-side charges and estimated gas, while sellers need the execution price minus seller-side deductions. A gas estimate belongs on the side that submits the transaction. These views can therefore differ even when both parties use the same sale price. Neither number should be called the final total until the settlement transaction has a receipt.

Direct and Aggregated Listing Comparison

Direct Looksrare orders execute under the applicable V2 strategy. Aggregated listings are routed through source-specific proxies, so their execution and fee terms may come from another order source. The shared interface does not make those underlying rules identical.

Compare both paths using the same dimensions: payable price, deduction allocation, creator payment, required approvals, estimated gas, and expected seller proceeds. A lower card price can lose its advantage if the associated route has a larger buyer-side charge or requires another transaction. Conversely, a higher gas estimate does not reduce seller proceeds when the buyer pays it separately.

What Can Change Before the Wallet Signature?

Order validity, fee parameters, creator terms, and the network estimate can change before submission. Another participant may fill the order, its maker may cancel it, or its validity window may end.

While the reader is inspecting quotes, no settlement transaction has been submitted, so either path can still be rejected. A refreshed checkout should still identify the intended collection, token, seller, currency, price, source, deductions, and transaction destination. Any changed field calls for a new cost comparison.

A wallet prompt marks the final review point. Its requested value, network, contract interaction, and gas settings should agree with the selected quote. An unexpected approval or different payment amount is a reason to reject the prompt and inspect the route again.

After submission, changing a page display cannot alter the transaction already sent. The observable states are then pending, successful, replaced, dropped, or reverted, depending on the wallet and network. Only a successful settlement can establish the sale amounts.

Gas Estimates and Final Network Cost

Gas estimates are provisional because network conditions and execution complexity can change. The final network charge is the gas used multiplied by the effective gas price. A wallet may also display a maximum possible charge based on its gas limit and fee settings, which is not automatically the amount ultimately consumed.

Approvals and on-chain cancellations are separate transactions, so their gas should not be folded invisibly into the sale receipt. A complete personal cost record may include those earlier actions even though the NFT purchase receipt contains only settlement gas. Off-chain order signatures do not carry the same network charge because they are not transactions.

Recorded Evidence for the Final Amount

Settlement evidence separates estimated interface values from recorded execution. The transaction hash connects the wallet action to its receipt, while decoded transfers and events explain how the execution price was distributed.

Settlement Amounts

Settlement data should account for the payment asset, NFT transfer, protocol allocation, and creator allocation that actually occurred. A quote remains useful for comparison, but the confirmed record controls reconciliation.

Buyer Payment

The buyer view combines the value sent for the purchase, any explicit buyer-side charge, and the gas paid by the submitting wallet. A simple balance change may include unrelated activity, so the transaction and its token transfers provide a cleaner boundary.

Seller Proceeds

The seller view starts with the execution price and subtracts deductions allocated to the seller. The resulting transfer should reach the order’s designated recipient. If another wallet submitted the acceptance transaction, that wallet’s gas is tracked separately from the seller’s received amount.

Network Record

A confirmed transaction receipt records execution status, gas used, and an effective gas price for the submitted transaction. Multiplying the gas used by the effective gas price gives the actual network charge. Transfer events and contract events then help distinguish the sale payment from protocol and creator allocations.

Why Can Two Similar Purchases Cost Differently?

Two purchases can differ because their orders use different sources, strategies, creator settings, currencies, or execution routes. One may require a prior token approval, while another uses an approval that the wallet already granted. Their gas estimates can also diverge when one transaction handles more items or invokes a different proxy.

Even identical execution prices do not guarantee identical wallet totals. Compare allocations and transaction requirements before treating either listing as cheaper. Use quotes to choose between listings, then use the successful receipt for the selected path to reconcile the completed expenditure.

Responding to a Cost Mismatch

A mismatch found before confirmation has the simplest remedy: reject the prompt, refresh the selected order, and compare its fields again. No settlement has occurred at that stage, so the reader can switch paths without trying to reverse a purchase.

View full-size image

A submitted transaction requires state-based diagnosis. First determine whether it is pending, replaced, reverted, or successful. A pending transaction has no final gas total, while a successful receipt fixes the executed cost. If the receipt shows success but the interface remains stale, the recorded transfers and ownership state take priority over the display.

Rebuild the quote only after identifying which input changed, such as order validity, deduction allocation, or network cost. A fresh quote whose fee lines match the intended order is stronger evidence than an old screenshot or another marketplace’s advertised rate.

What to know about Looksrare fees

Updated: Thu 17 Sep 2026