NFT staking lets holders lock or register their NFTs to earn rewards, such as a fungible token, points or in-game items. This guide explains the staking models, the reward math, the economic and security risks, and the cost of building an NFT staking platform.
The staking contract itself is a small piece of code, and the harder questions are where the rewards come from and what they are worth a few months after launch.
How NFT staking works: three models
Escrow staking
The holder transfers the NFT into a staking contract, which records the owner and the start time. Rewards build up until the owner withdraws, and the contract then sends the NFT back.
Escrow staking works with any existing collection, but it has three costs for the holder:
- The NFT leaves the holder's wallet and disappears from the holder's profile on marketplaces.
- Token-gated sites and apps no longer see the NFT in the holder's wallet.
- A bug in the staking contract can expose every staked NFT at once.
In-wallet lock ("soft staking")
The NFT stays in the holder's wallet, and the NFT contract has a lock flag that blocks transfers while the token is staked. Collections that plan staking from launch often use this design. ERC-5753 proposed a standard lock and unlock interface for ERC-721 tokens, but the proposal is marked Stagnant, which means work on it has stopped, so most collections write their own lock logic.
Snapshot-based rewards
The NFT stays in the wallet and nothing is locked. A server takes regular snapshots of who owns each token and calculates rewards off-chain, and holders then claim rewards on-chain with a Merkle proof. This model also works with an existing collection, but holders must trust the operator's calculation.
| Question | Escrow staking | In-wallet lock | Snapshot-based |
|---|---|---|---|
| Works with an existing collection | Yes | No. The NFT contract must support the lock. | Yes |
| NFT stays in the holder's wallet | No | Yes | Yes |
| Rewards calculated on-chain | Yes | Yes | No. Rewards are calculated off-chain and claimed with Merkle proofs. |
| Main risk | One contract holds all staked NFTs | A bug in the lock logic can block transfers | Holders trust the operator's numbers |
Some holders keep NFTs in a cold wallet, which stays offline for safety, and can still take part in snapshot-based programs through delegate.xyz. The cold wallet registers a hot wallet, an everyday online wallet, as its delegate in an on-chain registry. The project's claim contract checks the registry, so the hot wallet can claim rewards without moving the NFT.
Reward mechanics
Most NFT staking contracts use the "reward per token" accumulator from DeFi staking. The contract keeps one global counter that shows how much reward one staked NFT has earned since the program started, and the counter grows with time and with the emission rate. Each time a staker stakes, unstakes or claims, the contract saves the current counter value in that staker's record. Each staker has a weight, usually the number of NFTs they have staked. To find a staker's pending reward, the contract takes the counter's growth since the staker's last action and multiplies it by the staker's weight. The contract never loops over all stakers, so a stake, unstake or claim costs about the same gas for 10 stakers or 10,000.
Projects change the basic formula in four common ways:
- Rarity multipliers. Rarer NFTs earn more, and the contract should store the multipliers on-chain or check them with a Merkle proof, not take them from the website.
- Lock periods. Longer locks, such as 30, 90 or 180 days, earn higher rates, and some contracts charge a penalty for early exit.
- Set bonuses. Staking a specific combination of NFTs earns extra weight, which games use often.
- Rewards that are not tokens. Points, allowlist spots, in-game resources and physical goods avoid creating a tradable token.
The DeFi staking platform guide explains the accumulator math and its edge cases for fungible tokens.
The reward economics
In 2021 and 2022, many collections launched a reward token, let holders stake to earn it and promised future "utility". Emissions ran without pause, and demand for the tokens stayed low. Stakers sold their rewards, the token price fell, and staking stopped paying.
Write down the answers to these questions before you build an NFT staking platform:
- What can holders spend the rewards on, and who will buy the rewards from stakers who want to sell?
- Does the emission schedule have a cap, and what happens when emissions end?
- Does the reward come from revenue, such as marketplace fees or game income, or only from new tokens?
If the only source of rewards would be newly minted tokens, consider points or perks instead. Holders cannot sell them, so these rewards carry less risk for holders and for the project.
Security checklist
- Move NFTs with
safeTransferFrom, the ERC-721 transfer function that checks the receiver. ImplementonERC721Received, the function a contract needs to accept NFTs, and reject NFTs from collections the contract does not expect. - Update the contract's records before it sends any token out (the checks-effects-interactions order), and add reentrancy guards to the withdraw and claim functions.
- Let holders withdraw their NFTs at all times, even when rewards run out or the contract is paused. Most contracts add an emergency withdraw function that returns the NFT and cancels the pending rewards.
- Limit the reward token's mint rights to the staking contract, and set a hard supply cap.
- Put admin keys in a multisig wallet, and publish which actions the admin can take.
- Get an independent review. The smart contract audit guide explains how to scope one.
Building an NFT staking platform
- Choose the staking model and the reward type, and write down the reward economics.
- Write the staking contract, and the reward token if there is one, with audited building blocks such as OpenZeppelin Contracts.
- Build the dashboard, where holders connect a wallet, see eligible NFTs, stake, unstake, claim and see pending rewards.
- Index staking events, so the dashboard loads from an index and does not query every token on-chain.
- Get the audit, test on a testnet with real holders, then deploy to mainnet.
The figures in this section are estimates, not quotes. A staking contract for one collection with a dashboard takes one contract engineer and one frontend engineer about four to eight weeks, plus the audit. These features add time:
- Support for several collections
- Rarity proofs
- Lock tiers with penalties
- Game integration
Game studios often build staking into their game platform instead of a separate product, a design the NFT gaming platform guide covers. Projects that want NFTs to earn yield from borrowers, not from token emissions, can read the NFT lending platform guide.
What to ask a vendor
- Which audited libraries does the code use, and who audited the final version?
- Can holders always withdraw their NFTs, and when can the admin pause the contract?
- Who holds the admin keys, and does a multisig wallet hold them?
- How does the contract check rarity and multipliers on-chain?
Frequently asked questions
What is NFT staking?
NFT staking means locking an NFT in a contract, or registering it, to earn rewards over time. The rewards can be a token, points, allowlist spots or in-game items.
Can I add staking to a collection that is already minted?
Yes, with escrow staking or snapshot-based rewards. An in-wallet lock needs support in the NFT contract, which a deployed contract that cannot be upgraded usually lacks.
Do staked NFTs still receive royalties or airdrops?
Royalties go to creators, not holders, so staking does not change them. Airdrops based on wallet snapshots miss NFTs held in an escrow contract, unless the project also reads the staking contract's records.
Which chain is best for NFT staking?
Use the chain where the collection already lives, because bridging NFTs only to stake them adds risk. For new projects, low-fee networks keep frequent claims cheap.