Nftx vaults: V4 deposit eligibility and floor-token claims

Nftx vaults accept a standard ERC-721 deposit when its registered collection and transfer permissions allow the NFT into the V4 Locker contract. Confirm the collection contract, token ID, current owner, and contract pause state. A plain deposit exchanges the NFT for its collection’s floor token. Depositing a rare item at floor gives up its separately priced premium. Premium listings handle that pricing differently, while selling those tokens through the collection’s pool requires initialization and available liquidity.

A plain floor deposit makes the NFT redeemable by other token holders and does not reserve it for its depositor.

Floor deposits make the NFT available for redemption

During normal vault operation, a completed floor deposit makes the NFT available for redemption by other holders of its collection token. The Locker mints one full ERC-20 collection token per deposited NFT. A holder burns one full collection token to redeem a selected floor NFT from that collection. It does not reserve the deposited item for its previous owner. The NFT’s distinctive traits remain attached to the item, but the fungible token carries no separate payment for those traits.

A premium listing sets an above-floor asking price for the NFT held in the Locker. The seller receives the premium if a buyer fills the listing. Prepaid listing tax reduces the upfront collection-token payout. After an unsold liquid listing expires, its price falls toward floor in a Dutch auction. If the NFT remains unsold at floor, it becomes available for ordinary redemption.

Collection registration comes before market readiness

A collection must exist in the selected V4 deployment before its NFTs can use the Locker’s ordinary deposit function. Registration and trading readiness describe different states.

View full-size image

The registered collection

The Locker associates the NFT collection contract with its ERC-20 collection token. A matching collection name or ticker cannot establish that relationship. Names can repeat across contracts, and an identical address on another network does not establish the same collection state. When a registered collection uses a wrapper, the wrapper contract identifies the collection that the vault accepts.

The initialized market

Collection initialization establishes the trading pool and its initial liquidity. A registered token address alone does not establish that initialization has occurred. A direct deposit mints tokens; selling those tokens additionally requires a usable market. Legacy inventory staking follows its own version’s contracts and does not establish V4 market readiness.

Can this token ID enter the V4 vault?

A standard ERC-721 token ID must identify an existing NFT in the registered collection, owned by the depositing account and transferable through the chosen flow.

An ERC-721 NFT is identified by its collection contract and token ID on a particular chain. The ownership read for that identifier determines which account can supply it. Artwork, display names, and matching identifiers from another contract cannot substitute for that ownership record. A wrapper also changes the relevant contract identity; its admission rules govern which underlying items can become wrapped NFTs.

View full-size image

Rarity alone does not make an item incompatible with the vault. It changes the choice between an ordinary floor deposit and a premium listing.

Transfer permission follows the selected deposit route

Ownership must be accompanied by authorization for the contract that transfers the NFT, and the required operator can differ between direct deposits and bundled sales.

The transfer operator

ERC-721 authorization can apply to a particular NFT or to an operator across the owner’s collection holdings. Direct Locker deposits and flows through a convenience contract can use different approval targets. An approval to another operator does not authorize either target. An ERC-20 spending allowance concerns fungible tokens; it cannot authorize transfer of an ERC-721 item.

The collection’s transfer restrictions

A collection can impose additional transfer rules despite exposing an ERC-721 interface. For enforced creator-token collections, the contracts used by the selected flow must be permitted operators. Wallet approval cannot override a collection-level restriction. That restriction may require the collection’s administrators to allow the relevant operator before the deposit becomes executable.

Deposit costs follow the operations in the transaction

A plain deposit and a bundled sale have different cost inputs because the sale adds token trading to the vault operation. The V4 Locker charges no protocol fee for a plain NFT deposit. Network execution still costs gas. Required approvals can add execution costs when they need on-chain transactions.

The gas charge depends on execution work and the network’s applicable fee mechanism. An instant sale also encounters the collection-token market’s swap fees and available liquidity. A premium listing introduces tax determined by its floor multiple (asking price in collection tokens), duration, and collection-specific settings. Those costs belong to the additional operations. A sale quote estimates the payout after trading; a deposit’s mint amount counts the collection tokens issued.

Contract custody and administrative powers

A deposited NFT sits in the Locker, whose core code is non-upgradeable, while administrative permissions still affect vault operation.

The contract owner can pause Locker activity, blocking ordinary deposits and redemptions. Authorized listing contracts also affect which NFTs count as active listings. An active listing cannot leave through ordinary floor redemption; acquiring it requires its applicable listing path.

Approved managers have powers that ordinary depositors do not. Manager-only operations can withdraw NFTs or mint collection tokens without a matching NFT deposit. Token backing therefore depends on authorized managers using those powers correctly. The one-token-per-NFT mint ratio applies to ordinary deposits; manager-only functions have separate permissions and responsibilities.

Authorized administration can change a collection token’s name and symbol. Its contract address remains more useful for identification than the displayed ticker.

A vault shutdown changes access to inventory

Where the deployment includes collection shutdown, an eligible illiquid collection can enter a wind-down process that changes how holders recover remaining value. The shutdown contract owner can execute liquidation after voting reaches quorum, provided no active listings remain and the other shutdown conditions are met. It moves the remaining inventory into liquidation and sunsets the collection. A sunset collection cannot register again through ordinary collection creation.

View full-size image

Holders claim their proportional ETH liquidation proceeds under the shutdown rules only after all NFTs assigned to liquidation have sold. The claim burns the corresponding collection tokens. A shutdown announcement, a vote, and completed liquidation describe different states. The availability of shutdown contracts also differs between deployments. A historical vault listing cannot establish that new deposits remain available after sunset.

Last updated 2026 Oct 8