Can I stake a fraction of a legacy vault token?

The V2 and V3 contracts support deposits denominated in vault-token fractions. A direct token deposit does not require a whole NFT as its input. V3 rejects a deposit unless it mints nonzero inventory shares. The first deposit must leave shares for the position after the pool permanently reserves its minimum-liquidity shares. An NFT-only interface can expose fewer inputs than the underlying token-deposit method.

What happens to a V2 withdrawal lock after another deposit?

An additional V2 deposit can extend the account’s withdrawal lock if its new unlock time is later. The xToken contract keeps the later timestamp and does not shorten an existing lock. Because the lock applies to the account’s receipt balance, it can delay burning receipts held before that additional deposit. The effective time follows the deposit route and its configured duration.

Can an approved operator collect fees from a V3 xNFT?

The direct V3 reward-collection function requires the caller to own the xNFT. Approval to transfer the position does not satisfy that ownership check. The same owner check also applies to direct withdrawal. An approval can authorize an NFT transfer under the token standard, while the staking functions impose their own caller requirement. Transfer permission and direct access to staking payouts are separate rights.

Why can direct NFT staking leave V3 WETH rewards unchanged?

Direct NFT staking does not itself create a fee payment when its ordinary mint fee is excluded. Creating a position increases inventory participation, but new WETH rewards require fee distribution to that vault’s staking pool. A newly created position starts from the current reward-accounting snapshot. It does not inherit fees attributable to earlier participation simply because it adds NFTs to the same vault.

Which V3 positions can be combined into a single position?

V3 can combine positions belonging to the same owner and the same vault after their applicable locks expire. The parent position must qualify as well as each child. Combining moves inventory shares and accounted WETH rewards into the parent; it does not combine different collections or erase an active lock. Ownership of every participating xNFT matters even when their displayed token names look similar.

Does a V3 WETH balance fund the gas for collecting it?

WETH owed inside a staking position does not automatically fund the gas for a direct collection transaction. Ordinary Ethereum execution requires gas funding before the contract transfers the reward. WETH and native ETH are distinct balances, and the direct collection function returns WETH. Having claimable rewards therefore does not by itself establish that the sending account can pay that transaction’s gas.

Who owns a V3 xNFT if the deposit specifies a different recipient?

The specified recipient receives and owns the xNFT created by a V3 deposit. Supplying the vault tokens or NFTs does not make the funding caller its owner when another recipient is selected. Subsequent direct reward collection and withdrawal follow ownership of that position. The recipient parameter therefore determines who initially controls the stake, including its accumulated fee rights and applicable withdrawal constraints.

Nftx

Nftx inventory staking rewards and legacy withdrawals across V2 and V3

Nftx inventory staking lets holders earn vault-fee rewards from a single-sided position without supplying matching ETH liquidity. V2 uses fungible staking receipts, while V3 records positions as NFTs with separate WETH rewards. These are legacy mechanisms alongside V4. Withdrawal eligibility, penalties, and NFT redemption costs follow the version and the position’s recorded terms.

A vault token balance, a staking receipt, and an NFT deposit each carry different rights. The distinction affects which asset an exit returns and which fees apply. Existing positions retain their original withdrawal rules during migration.

Bottom line: Collecting V3 WETH rewards leaves inventory shares staked, while withdrawing those shares applies the position’s own lock and penalty rules.

Participation and vault activity determine fee rewards

Only a recorded stake shares inventory-staking rewards; holding ordinary vault tokens in a wallet does not create a staking position. Rewards come from fee-generating vault activity and the allocation to inventory stakers. Each participant receives a proportional share through the staking pool’s accounting. An equal number of positions does not mean equal rewards when their underlying shares differ.

V2’s inventory-staking launch allocated 20% of vault fees to inventory stakers and 80% to liquidity stakers. These percentages described shares of collected fees. They did not promise an annual return on the deposited assets. More stake sharing an unchanged fee flow reduces the fraction attributable to an existing position. Historical annualized yield displays describe past activity and do not establish a fixed payment schedule.

V3 allows its fee distributor’s receiver allocations to change. Missing active pool liquidity can also change where distributable fees flow.

Vault inventory supplies NFTs while liquidity supports trading

The NFT vault, its fungible vault token, and the inventory-staking pool handle different assets. The vault holds deposited collectibles that other users can redeem. Staking holds claims denominated in that vault’s token. Separate trading liquidity supports exchanges between the token and a paired asset. Inventory staking avoids supplying the matching ETH side of that trading position. It still leaves the holder exposed to the collection’s market value and the staking contracts. Deposited NFTs join shared inventory, so staking does not reserve the original items for their depositor. An eventual NFT withdrawal requires items that remain available.

Legacy positions keep their original contract identity

V4 is the current development path, and its migration interface groups V2 and V3 balances as legacy positions. Existing positions continue under their original contracts. A V2 receipt remains associated with its V2 vault, even when the same collection appears in V4. A V3 position ID identifies an NFT in the V3 staking contract. Similar collection names or token symbols do not make these balances interchangeable. Withdrawal support must match the actual version and contract holding the stake. V3 has separate pause controls for depositing, increasing positions, withdrawing, and collecting rewards.

The V2 recovery interface and the old staking interface have different purposes. Replacing an interface does not itself withdraw a position, cancel its lock, or move its underlying inventory.

V2 receipts combine principal with vault-token rewards

Share value

A V2 xToken is an ERC-20 receipt for a share of its inventory-staking pool’s vault-token balance. V2 inventory-staking rewards increase the vault tokens backing existing xToken shares. The receipt count can stay unchanged while its redeemable token value grows. Withdrawal burns the chosen xToken amount and returns its proportional backing. The relevant relationship is shares withdrawn multiplied by the pool’s vault-token balance, divided by total xToken supply. Integer rounding applies to the contract calculation. A receipt balance alone therefore does not express the exact vault-token amount that an exit returns.

Account lock

V2 records an unlock timestamp against the holder’s account in the relevant xToken contract. Direct vault-token deposits and NFT staking through a zap can apply different configured durations. An active lock prevents the receipt burn required for withdrawal. The V2 withdrawal method does not offer V3’s declining early-exit penalty as an alternative. Historical descriptions of one staking route’s duration should not become a universal lock for every V2 deposit.

The basic withdrawal returns vault tokens. NFT redemption has its own vault rules, and supported unstaking integrations can combine those operations. Receiving tokens alone leaves the NFT redemption decision open.

V3 deposit forms create different withdrawal constraints

Vault-token deposits

A V3 vault-token deposit creates an ERC-721 staking position, called an xNFT, and records its inventory shares. The V3 implementation applies a hard one-hour withdrawal lock to positions created with vault tokens. Paying an early-exit penalty does not bypass that hard lock. The deposit can also request the regular configured timelock through forceTimelock. That additional choice affects the early-exit calculation and ordinary redemption-fee treatment. Both lock timestamps start from the deposit transaction.

NFT deposits

The NFT deposit method combines depositing eligible NFTs, minting vault tokens, and creating the staking position within one call. It avoids the ordinary mint fee when the staking contract has the required fee exclusion. The position takes the configured regular lock, subject to the applicable timelock-exclusion setting. This route does not acquire the hard vault-token lock merely because it internally mints tokens. Its early-exit rules follow the regular lock recorded on the position.

Additional vault tokens

V3 supports increasing a position created through the vault-token route. An increase refreshes its hard withdrawal lock and can impose a new regular lock. A position created directly with NFTs does not qualify for that increase method.

View full-size image

Can V3 fees be collected before the inventory unlocks?

V3 lets the position owner collect accrued WETH fees while the inventory remains locked, provided the collection operation is not paused. WETH is wrapped ETH held as an ERC-20 token. The direct collection function transfers that token without removing inventory shares or redeeming NFTs. Its accounting calculates fees accrued since the position’s reward snapshot, together with previously recorded fees owed. Collection then updates the snapshot and clears the paid amount. WETH rewards do not automatically purchase more vault tokens or increase the inventory position. A later withdrawal can also pay outstanding WETH fees, so reward collection and principal withdrawal have different effects.

View full-size image

What reduces a V3 withdrawal before NFT redemption?

A V3 early-exit penalty reduces the vault tokens attributable to withdrawn shares when the regular position lock remains active. Its calculation uses the withdrawn token amount, the configured penalty coefficient, and the fraction of that lock remaining. The deduction declines linearly as the recorded unlock time approaches. The penalty coefficient is an administrative setting that can affect existing positions. An old advertised percentage therefore cannot replace the effective coefficient when assessing an exit.

The deducted vault tokens remain in the staking pool and increase the backing of remaining shares. WETH fee collection follows separate accounting. After any penalty, enough whole vault tokens must remain to fund the requested NFT redemption. Each selected NFT must also be present in the vault. Newly deposited V3 inventory can carry a declining premium when redemption fees are enforced.

The direct V3 withdrawal function can redeem NFTs even for an unlocked vault-token position that never took the regular lock. Ordinary redemption fees remain chargeable for that case. Positions that took the regular lock avoid ordinary redemption fees and NFT premiums through the staking withdrawal route, subject to the contract’s required fee exclusion. NFT redemption can require ETH for fees or premiums, and the requested premium limit constrains execution. The chosen interface must support the corresponding contract route.

What reduces a V3 withdrawal before NFT redemption? (Nftx inventory staking)

View full-size image

Exit options and their blocking conditions

The same staking balance can support different exit choices, with different constraints on what leaves the contract. Reward collection leaves principal in place. Token withdrawal removes inventory shares without requiring a selected NFT. Combining withdrawal with redemption adds inventory and fee conditions. Migration concerns the recovered legacy vault tokens, not an automatic conversion of their staking receipt.

Exit option	Blocking condition or remaining limit
V2 withdrawal to vault tokens	An active xToken account lock blocks the required receipt burn.
V3 collection of WETH rewards	Requires the position owner; leaves inventory shares and their locks in place.
V3 withdrawal to vault tokens	The hard token-deposit lock blocks exit; an active regular lock can reduce the token return.
V3 withdrawal with NFT redemption	Requires available NFTs, sufficient post-penalty tokens, and any payable fees or premiums.
Legacy vault-token migration into V4	Requires Ethereum Mainnet, recovered legacy tokens, and a registered V4 collection; staking receipts are not the migration input.

Share balances and claimable fees use different units

A V3 position’s share balance measures ownership of pooled vault tokens, while its WETH balance measures claimable fee rewards. Those quantities should remain separate when reading a position. The vault-token amount attributable to shares follows the staking contract’s token balance and that vault’s total shares. A changing share value can reflect token penalties retained in the pool without any change to WETH rewards. Conversely, accumulating WETH does not itself increase the inventory-share count. Comparing a share count directly with an NFT count can therefore misstate the withdrawable inventory.

The contract’s pricePerShareVToken read expresses vault-token backing per share. Its wethBalance read calculates the position’s claimable WETH. Neither figure measures the eventual ETH proceeds from selling withdrawn inventory.

Recorded withdrawals and the assets that arrive

V3’s Withdraw event reports removed shares, a calculated vault-token amount, and WETH paid. When the transaction also redeems NFTs, some of that calculated token amount funds redemption. The event’s token field therefore does not necessarily equal an ERC-20 transfer arriving in the wallet. The received NFTs and any residual vault tokens describe the actual inventory payout. The WETH field describes the reward payment separately. A display that adds all these figures together can count the redeemed inventory twice.

Reward collection has its own CollectWethFees event. It records payment from a position without establishing that principal has left staking. A position can remain present after its inventory shares reach zero, so merely seeing an xNFT in the wallet does not prove that inventory remains staked.

A signed authorization or submitted transaction establishes no completed withdrawal. Execution status and resulting transfers distinguish completion from a rejected or pending request. A completed exit also says nothing about future staking income.

Migration begins with recovered legacy vault tokens

Moving a legacy inventory position toward V4 requires recovering its underlying vault tokens under the applicable staking rules. The Migrator Zap, available only on Ethereum Mainnet, then redeems selected legacy NFTs and deposits them into V4 within one transaction. It sends newly minted collection tokens to the specified recipient. This atomic migration operation does not itself accept an xToken receipt or a V3 xNFT as its starting asset. Legacy redemption charges remain relevant unless the migrator has the appropriate fee exclusion. V4’s ordinary deposit and redemption fee policy does not retroactively waive a V2 or V3 staking penalty.

Whole-NFT migration needs sufficient whole legacy token units and a registered replacement collection. A recovered fractional remainder cannot independently redeem an NFT. Dust escrow accepts only registered legacy-to-replacement token pairs. Only the migrator’s owner can settle dust deposits, using replacement tokens held by the contract. Until settlement, the depositor can reclaim the escrowed legacy tokens.

Questions people ask about Nftx inventory staking

Can I stake a fraction of a legacy vault token?: The V2 and V3 contracts support deposits denominated in vault-token fractions. A direct token deposit does not require a whole NFT as its input. V3 rejects a deposit unless it mints nonzero inventory shares. The first deposit must leave shares for the position after the pool permanently reserves its minimum-liquidity shares. An NFT-only interface can expose fewer inputs than the underlying token-deposit method.
What happens to a V2 withdrawal lock after another deposit?: An additional V2 deposit can extend the account’s withdrawal lock if its new unlock time is later. The xToken contract keeps the later timestamp and does not shorten an existing lock. Because the lock applies to the account’s receipt balance, it can delay burning receipts held before that additional deposit. The effective time follows the deposit route and its configured duration.
Can an approved operator collect fees from a V3 xNFT?: The direct V3 reward-collection function requires the caller to own the xNFT. Approval to transfer the position does not satisfy that ownership check. The same owner check also applies to direct withdrawal. An approval can authorize an NFT transfer under the token standard, while the staking functions impose their own caller requirement. Transfer permission and direct access to staking payouts are separate rights.
Why can direct NFT staking leave V3 WETH rewards unchanged?: Direct NFT staking does not itself create a fee payment when its ordinary mint fee is excluded. Creating a position increases inventory participation, but new WETH rewards require fee distribution to that vault’s staking pool. A newly created position starts from the current reward-accounting snapshot. It does not inherit fees attributable to earlier participation simply because it adds NFTs to the same vault.
Which V3 positions can be combined into a single position?: V3 can combine positions belonging to the same owner and the same vault after their applicable locks expire. The parent position must qualify as well as each child. Combining moves inventory shares and accounted WETH rewards into the parent; it does not combine different collections or erase an active lock. Ownership of every participating xNFT matters even when their displayed token names look similar.
Does a V3 WETH balance fund the gas for collecting it?: WETH owed inside a staking position does not automatically fund the gas for a direct collection transaction. Ordinary Ethereum execution requires gas funding before the contract transfers the reward. WETH and native ETH are distinct balances, and the direct collection function returns WETH. Having claimable rewards therefore does not by itself establish that the sending account can pay that transaction’s gas.
Who owns a V3 xNFT if the deposit specifies a different recipient?: The specified recipient receives and owns the xNFT created by a V3 deposit. Supplying the vault tokens or NFTs does not make the funding caller its owner when another recipient is selected. Subsequent direct reward collection and withdrawal follow ownership of that position. The recipient parameter therefore determines who initially controls the stake, including its accumulated fee rights and applicable withdrawal constraints.

Last updated 2026 Oct 8