-
Notifications
You must be signed in to change notification settings - Fork 33
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
15 changed files
with
47 additions
and
44 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,18 +1,18 @@ | ||
=== NFT Maker === | ||
Contributors: lukaskotol | ||
Donate link: https://tatum.io/ | ||
Donate link: [email protected] | ||
Tags: tatum, blockchain, nft, erc721, ethereum, celo, bsc, mint | ||
Requires at least: 5.5 | ||
Requires PHP: 7.0 | ||
Tested up to: 5.8.2 | ||
Stable tag: 2.0.25 | ||
Stable tag: 2.0.26 | ||
License: MIT | ||
License URI: https://opensource.org/licenses/MIT | ||
|
||
If you want to sell NFTs but don’t want to build an entire NFT marketplace from scratch, then [NFT Maker](https://tatum.io/) is the plugin you’ve been waiting for. | ||
If you want to sell NFTs but don’t want to build an entire NFT marketplace from scratch, then NFT Maker is the plugin you’ve been waiting for. | ||
|
||
== Description == | ||
If you want to sell NFTs but don’t want to build an entire NFT marketplace from scratch, then NFT Maker is the plugin you’ve been waiting for. Lazy Minting. WordPress integration. Free IPFS Storage, forever. | ||
If you want to sell NFTs but don’t want to build an entire NFT marketplace from scratch, then NFT Maker is the plugin you’ve been waiting for. Lazy Minting. WordPress integration. Free IPFS Storage, forever. | ||
|
||
NFT Maker supports the following blockchains: | ||
|
||
|
@@ -22,7 +22,7 @@ NFT Maker supports the following blockchains: | |
**Celo** | ||
**Harmony** | ||
|
||
NFT Maker by Tatum allows you to turn your Woocommerce store into an NFT store with a simple plugin. Just install, follow your usual WordPress product publishing flow, and tick which blockchain you’d like to mint your NFTs on. It’s so easy, you’ll be up and running in no time! | ||
NFT Maker allows you to turn your Woocommerce store into an NFT store with a simple plugin. Just install, follow your usual WordPress product publishing flow, and tick which blockchain you’d like to mint your NFTs on. It’s so easy, you’ll be up and running in no time! | ||
|
||
**Lazy Minting** | ||
Put simply, lazy minting is when an NFT is available off the blockchain and only gets minted when someone buys it. This means that you, the seller, don’t have to pay any upfront gas fees to mint your NFTs. Gas fees are only paid once the NFT is purchased and then minted on the blockchain. | ||
|
@@ -35,7 +35,7 @@ Check out our [full video tutorial on how to get started.](https://www.youtube.c | |
|
||
Here’s it works: | ||
1. Install the plugin. | ||
2. Sign up for a paid Tatum plan. The credits from your plan are used to pay for the gas fees to mint NFTs. **NFT Maker does not work with Free plans or Test API keys.** | ||
2. Sign up for a paid [Tatum plan](https://dashboard.tatum.io/). The Tatum is an external service which provides access for the blockchain infrastructure. The credits from your plan are used to pay for the gas fees to mint NFTs. **NFT Maker does not work with Free plans or Test API keys.** | ||
3. Create your NFT by uploading an image. This won’t consume any credits until someone buys it. | ||
4. When someone buys your NFT, the metadata is uploaded to IPFS, and the NFT is minted to the blockchain address provided by the customer at checkout. | ||
5. Credits to pay the gas fees for minting are deducted from your paid Tatum plan. | ||
|
@@ -57,7 +57,7 @@ This section describes how to install the Tatum plugin and get it working. | |
|
||
1. Download and install the [Woocommerce plugin](https://wordpress.org/plugins/woocommerce/) if you haven’t already. | ||
2. Click “Get your Tatum API key.” | ||
3. Login to the Tatum dashboard and purchase a paid plan. | ||
3. Login to the [Tatum dashboard](https://dashboard.tatum.io/) and purchase a paid plan. The Tatum is an external service which provides access for the blockchain infrastructure. | ||
4. When you have completed your purchase, you will be directed back to the Tatum dashboard. Next to your newly created API key, click “Show” and copy your API key. | ||
5. Now, back in the NFT Maker dashboard, paste your API key in the field labeled “Paste your API key below.” | ||
6. Okay, you’re all ready to mint NFT tokens! In the overview, you can see info about your API key. | ||
|
@@ -135,7 +135,7 @@ No, again, NFT Maker can only be used to sell NFTs created with the plugin. | |
For a complete guide on how to build the backend to an NFT marketplace from scratch, please refer to Tatum’s How to build [NFT marketplaces part 2 - Backend guide.](https://blog.tatum.io/how-to-build-nft-marketplaces-part-2-backend-899f7d804066) | ||
|
||
== Screenshots == | ||
1. Create an account in the [Tatum Dashboard](https://dashboard.tatum.io/login) and obtain paid API key. | ||
1. Create an account in the [Tatum Dashboard](https://dashboard.tatum.io/login) and obtain paid API key. The Tatum is an external service which provides access for the blockchain infrastructure. | ||
2. Install [Woocommerce plugin](https://wordpress.org/plugins/woocommerce/) if you don't have already installed it yet. | ||
3. Submit your API key. | ||
4. You are ready to mint NFT tokens! In the overview, you can see info about your API key. | ||
|
@@ -194,6 +194,9 @@ For a complete guide on how to build the backend to an NFT marketplace from scra | |
= 2.0.25 = | ||
* Added better integration for description and name to the OpenSea. Also name of the NFT in the metadata is taken from the title of the product not from the image name. | ||
|
||
= 2.0.26 = | ||
Changed author of the plugin | ||
|
||
== Upgrade Notice == | ||
|
||
= 1.0.0 = | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters