Plugin info
Maintenance & Compatibility
Maintenance score
Possibly abandoned • Last updated 1345 days ago • 2 reviews
Is NFT Login abandoned?
Possibly abandoned (last update 1345 days ago).
Compatibility
Similar & Alternatives
Explore plugins with similar tags, and compare key metrics like downloads, ratings, updates, support, and WP/PHP compatibility.
Description
NFT Login requires users to verify NFT ownership in order to register and login to your site.
Use this plugin to create exclusive content for any NFT collection. Make a discussion board or e-commerce site just for CryptoPunks
or Bored Ape Yacht Club holders or any other NFT collection.
Features
* Require NFT verification to register or login to your site
* Lock content on specific posts or pages until the user verifies NFT
Installation
- Install and activate the plugin
- Go to NFT Login Plugin settings page in the WordPress admin dashboard
- Enter the Token Name and NFT Contract Address
Frequently Asked Questions
Any NFT collection on Ethereum or Polygon. All you need is the public contract address which is easily findable on sites like Etherscan or OpenSea
No. All you need is the contract address. WP admin users can login as normal without verifying ownership.
All NFT collections have a smart contract which created the items in the collection. The contract address is the blockchain address of the smart contract.
Search for the collection on OpenSea. Select any item from the collection. For example CryptoPunk #8666.
Expand the details section to find the Contract Address for CryptoPunks is 0xb47e3cd837dDF8e4c57F05d70Ab865de6e193BBB.
Check the box under NFT Content Protection in the post/page metadata
Yes! Add a support topic or contact me.
Review feed
Changelog
1.0.0
Initial release
1.1.0
Content locking
Configuration option for registration and login
1.1.1
Fix bug in configuration for registration and login
1.2.0
Support for Polygon blockchain
1.2.1
Bug fix missing function
1.2.2
Php 8 bug fix
1.2.3
Removed “Verified NFT does not match registered user” check
1.2.4
Fix compatibility with non ERC721 tokens





