Features and Networks

NFT

A large number of tokens Up to 10,000 NFTs For each collection.

whitelist functionality is available and can be edited, we can add/remove.

Enforce Royalties using OpenSea's operator filter registry. It only works for supported Marketplaces.

uploading metadata automatically for your photos if you haven't done so or have no experience, this means that only pictures are enough.

NFTs counter tokens will be numbered according to the precedence of the mint. (ex: NFT1, NFT7, etc).

Marketplaces All NFT collections comply with metadata standards and are compatible with all popular marketplaces. Your community can own, sell, and trade an item the moment it’s minted.

EVM Collections appear instantly on OpenSea once people start minting NFTs from your collection.

Check Collections already created: SNFT PASS

Marketplace

The Marketplace contract allows users to list NFTs for direct sale or auction. Other users can place offers/bids or buy the NFTs for the specified amount in the listing. The marketplace can be configured to only allow certain users to list NFTs for sale, or allow any user to list NFTs for sale.

The Marketplace contract honors EIP-2981 royalty distribution and is integrated with the royalty registry.

Upgradeability The Marketplace contract is written in the EIP-7504 dynamic contracts pattern.

You could use the Marketplace contract to:

Sell NFTs on your marketplace

Create auctions where the highest bidder, after a certain period, wins the NFT

Launchpad

The NFT Drop contract is ideal when you want to release a collection of unique NFTs using the ERC721A Standard.

It allows you to define a set of conditions called claim phases in a sequence that defines when and how your users can claim an NFT from your drop; including allowlists, release dates, claim limits, and delayed reveals.

When you add NFTs to your drop contract, they are not minted at this point. You prepare everything for your users by lazy minting them so that other wallets can mint them

OpenSea Creator Earnings Supported Here's how creator earnings work on OpenSea. This contract supports OpenSea creator earnings by default; this support can be switched on and off by the contract admin, after deployment, by calling the setOperatorRestriction using the contract explorer.

Use Cases & Examples :

You could use the NFT Drop contract to:

Release a PFP Collection where each NFT has a different combination of traits

Release NFTs of your artwork, and have your community mint them for a price

Create a restricted-access NFT drop, where only a specified list of wallets can claim NFTs

NFT Stakes

This contract allows users to stake their ERC-721 NFTs and get ERC-20 tokens as staking rewards.

we set the NFT and Reward-token addresses during deployment. These can't be changed later.

Staked NFTs are stored inside the contract and rewards are calculated,

for example, the time these NFTs were staked. Project owners should maintain an adequate balance of reward tokens in the staking contract by using the deposit function to deposit reward tokens. These rewards are then transferred to stakers upon claiming.

Reward calculation at the time of claiming rewards:

rewardsPerTokenStaked = (stakingDuration * rewardsPerUnitTime) / timeUnit

Note:

Users need to approve their NFTs to the staking contract address before they can stake them

ERC20 Stakes

This contract allows users to stake their ERC-20 tokens and get ERC-20 tokens as staking rewards (different from the staked tokens). we set the Staking and Reward token addresses during deployment. These can't be changed later.

Staked tokens are stored inside the contract and rewards are calculated for the time these tokens were staked. Project owners maintain an adequate balance of reward tokens in the staking contract by using the deposit function to deposit reward tokens. These rewards are then transferred to stakers upon claiming.

Reward calculation at the time of claiming rewards:

rewardsPerTokenStaked = ((stakingDuration * rewardRatioNumerator) / rewardRatioDenominator) / timeUnit for example, if the reward ratio is 1/20, this implies that there will be 1 Reward token given out for every 20 tokens staked. The numerator and denominator of the reward ratio should be set separately (1 and 20 in this case respectively).

Note:

Users need to approve their tokens to the staking contract address before they can stake them

Available networks

Polygon PoS - Fantom - Base - Optimism - zkSync - Arbitrum - Linea - Gnosis - Klaytn - Avalanche - Taiko - Blast

You can request to launch your project on any EVM network, but with different fees, based on transaction fees.

Last updated