Does an NFT Need a Sale Listing Before Its Owner Accepts a Collection Offer?

An existing sale listing is not a prerequisite for accepting a native V2 collection bid. The owner supplies a taker ask against the buyer's signed maker bid. Eligibility, ownership and transfer permissions still apply. A separate fixed-price listing does not supply missing authorization for this acceptance.

Can a Buyer Change a Collection offer's Price After Signing?

Changing the price requires a new signed order because the signature binds the original terms. Publishing a replacement does not automatically invalidate the earlier bid. Cancellation withdraws the old order. Sharing an order nonce makes the bids mutually exclusive after a successful fill, while either can execute beforehand if its other conditions remain valid.

Is the Displayed WETH Bid the seller's Final Payment?

The displayed bid price is the purchase amount before settlement allocates applicable trading fees. Native V2 deducts protocol fees and any applicable creator fee from that amount, leaving the seller's proceeds. The seller's Ethereum transaction fee is a separate ETH expense and does not become part of the WETH payment.

What Expiry Limit Applies to a Collection Offer Submitted Through the V2 API?

The documented single-order V2 API limits the end time to no more than 180 days beyond the current time at submission. This is an order-intake restriction for that API, not an acceptance deadline shared by every possible protocol route. The signed end time determines when that particular offer stops being executable.

Will Adding WETH Back to a Wallet Reactivate Its Earlier Collection Bids?

Restoring WETH can make an earlier bid executable again if insufficient funding was its only blocker. The signature can remain usable within its validity window, provided allowances, nonces and other execution conditions remain valid. Moving funds away does not perform nonce cancellation, so it does not permanently withdraw an unwanted collection bid.

Looksrare

Looksrare collection offers let sellers choose the NFT for a buyer's WETH bid

Last updated 11 Oct 2026

Looksrare collection offers let a buyer propose a WETH price for an eligible NFT from a selected collection. An owner chooses the token when accepting the bid, so the buyer leaves that choice open within the order's eligibility rules. The basic V2 collection strategy fills once, with any ERC-1155 quantity set in the order. Settlement requires sufficient buyer funding, seller ownership and transfer permissions, together with valid signed terms. The NFT changes hands only when the acceptance transaction succeeds.

Offering a Price Across a Collection

A collection bid suits a purchase where collection membership matters more than a particular token ID, because an eligible owner can supply the NFT. A token-specific offer binds the purchase to the chosen item. The collection-wide price therefore expresses what the buyer will pay for any eligible item, without selecting its appearance or rarity. For ERC-721, the basic strategy buys one NFT. For ERC-1155, it fills the signed quantity of one token ID at the order's total price.

The Signed V2 Order and Its Permissions

A native V2 collection offer is a maker bid: the buyer authorizes purchase terms before a seller accepts them on-chain. V2 maker orders use EIP-712 typed-data signatures. The signed data identifies the collection contract, payment currency, price and validity window. It also includes the signer, token standard, quantity and nonce fields. These fields give the exchange specific terms to enforce. The collection contract address identifies the eligible assets, so a familiar collection name alone does not establish what the order covers.

The basic collection strategy uses strategyId 1. The seller supplies the actual token ID through the taker order's additional parameters, allowing the same bid to match different eligible items.

WETH spending approval gives the exchange permission to collect the payment when the order executes. The buyer needs both a sufficient balance and sufficient allowance. An allowance does not reserve WETH for a particular collection bid, and signing the offer does not move its payment into escrow. Funds remain in the buyer's wallet until settlement. Consequently, other spending can leave an outstanding bid without enough funding. The distinction between approval and payment also explains why an already approved wallet can sign further offers without repeating an unchanged allowance transaction.

Sellers authorize the NFT side through the V2 TransferManager. The NFT owner must permit that manager to transfer the relevant assets and must also authorize the exchange to use the manager. Existing permissions can satisfy these requirements while they remain active. A WETH approval from the buyer cannot substitute for the seller's NFT permissions. Using collection-wide NFT approval extends permission beyond the single item under consideration, so the operator address and permission scope deserve attention before authorization.

The signed start and end times define the execution window. Nonce cancellation can disable an outstanding bid even when its signature and original expiry remain unchanged.

Why Do Collection Offers Use WETH While Transactions Need ETH?

The documented single-order V2 API requires WETH for collection bids, while ETH pays Ethereum transaction fees for the account submitting an on-chain action. WETH means Wrapped Ether, an ERC-20 form of ETH supporting spending allowances. Native ETH in the wallet does not satisfy a WETH bid's balance requirement. Signing the maker bid does not itself consume gas. Wrapping funds, granting approvals, cancelling orders and submitting an acceptance can require transactions. The seller needs ETH for an acceptance they submit directly.

From WETH Bid to Settled Sale

A native V2 collection-bid sale joins the buyer's signed offer to the seller's selected NFT through the following process. Existing active approvals can satisfy the permission requirements without new approval transactions. The exchange checks the order and performs its transfers within the acceptance transaction. A successful fill of the basic V2 collection strategy invalidates the buyer's order nonce. That bid then stops being executable against the collection's other items.

From WETH Bid to Settled Sale in brief
Stage	Participant and Action	Resulting State	Condition or Recovery
Set Offer Terms	The buyer chooses the collection, WETH price, quantity and validity window.	The order describes an intended purchase.	Correct the collection or terms before signing.
Prepare Payment	The buyer holds sufficient WETH and grants the exchange sufficient allowance.	The exchange can collect the signed payment during a valid fill.	ETH alone cannot cover the WETH payment.
Sign and Publish	The buyer signs the maker bid and submits it to the order book.	Accepted publication makes the signed bid discoverable through the order API.	A signature alone does not establish successful publication.
Prepare the NFT	The seller selects an eligible token and supplies the required NFT transfer permissions.	A matching taker ask identifies the asset the seller will deliver.	Acceptance requires current ownership and active transfer permissions.
Execute Acceptance	The seller submits the taker ask against the signed maker bid.	A successful transaction exchanges the NFT and WETH and consumes the bid.	An invalid match reverts; an included failed transaction can still consume gas.
Confirm the Sale	The participants inspect the transaction receipt and resulting asset transfers.	The successful execution identifies the sold token and payment recipients.	A pending transaction hash does not confirm a completed sale.

The seller receives the proceeds allocated by settlement in the bid's payment currency. Trading fees can reduce that allocation; gas remains a separate ETH expense.

Why Can a Visible Collection Offer Fail?

A visible collection offer can fail because its signed terms or required transfers no longer satisfy the exchange's checks when acceptance executes. The buyer may lack enough WETH or allowance. The seller may no longer own the NFT or may have revoked transfer permissions. The order may also be outside its validity window, cancelled or already filled. More ETH for gas cannot replace missing WETH, and an NFT approval cannot revive a consumed order.

A submitted transaction can encounter an earlier successful fill by another seller. The basic collection bid then has no remaining acceptance available.

The V2 SDK can check maker-order validity using the order and its signature. That check helps identify an invalid bid before submission, although balances and order state can change afterward. A reverted single acceptance rolls back the sale's token transfers, while earlier approval transactions remain separate. An included failure can still incur a gas charge. Funding or permission failures require the missing prerequisite before another attempt. An expired or consumed order needs a different valid offer.

Restricted Bids and Collection Routing

Proof-based collection bids restrict eligible token IDs when the selected V2 execution strategy and order interface support that variant. The proof-based collection strategy checks the offered token ID against the Merkle root included in the maker order. A Merkle proof demonstrates membership in the committed token set. This can support a set chosen for particular traits, but the proof itself verifies the token ID's inclusion. It does not independently inspect the NFT's current artwork, metadata or rarity.

The documented single-order V2 API accepts standard and basic collection strategy IDs. A proof-based integration needs a configured compatible strategy and an interface supporting its additional parameters. Filtering a display does not add restrictions to an unrestricted signed collection bid. A token-specific offer provides a simpler restriction when only one item suits the purchase.

Some collections use Seaport routing for order creation. Collection-route data identifies whether an integration should create a native V2 order or a Seaport order. Native V2 strategy IDs and TransferManager permissions describe the V2 path; Seaport orders require their own matching and authorization rules. Decide whether every eligible item suits the purchase before signing collection-wide terms.

Illustration: Looksrare collection offers: Restricted Bids and Collection Routing

Open full-size image

Looksrare collection offers: the short answers

Does an NFT Need a Sale Listing Before Its Owner Accepts a Collection Offer?: An existing sale listing is not a prerequisite for accepting a native V2 collection bid. The owner supplies a taker ask against the buyer's signed maker bid. Eligibility, ownership and transfer permissions still apply. A separate fixed-price listing does not supply missing authorization for this acceptance.
Can a Buyer Change a Collection offer's Price After Signing?: Changing the price requires a new signed order because the signature binds the original terms. Publishing a replacement does not automatically invalidate the earlier bid. Cancellation withdraws the old order. Sharing an order nonce makes the bids mutually exclusive after a successful fill, while either can execute beforehand if its other conditions remain valid.
Is the Displayed WETH Bid the seller's Final Payment?: The displayed bid price is the purchase amount before settlement allocates applicable trading fees. Native V2 deducts protocol fees and any applicable creator fee from that amount, leaving the seller's proceeds. The seller's Ethereum transaction fee is a separate ETH expense and does not become part of the WETH payment.
What Expiry Limit Applies to a Collection Offer Submitted Through the V2 API?: The documented single-order V2 API limits the end time to no more than 180 days beyond the current time at submission. This is an order-intake restriction for that API, not an acceptance deadline shared by every possible protocol route. The signed end time determines when that particular offer stops being executable.
Will Adding WETH Back to a Wallet Reactivate Its Earlier Collection Bids?: Restoring WETH can make an earlier bid executable again if insufficient funding was its only blocker. The signature can remain usable within its validity window, provided allowances, nonces and other execution conditions remain valid. Moving funds away does not perform nonce cancellation, so it does not permanently withdraw an unwanted collection bid.