After many successful stories, we’re now entering completely new waters. Omnisea is proud to become the first truly permissionless NFT Drops Launchpad on Sui Mainnet to give Creators access to this groundbreaking technology.

In this article, we’ll guide you on how to create your Drop on Sui, what are the key differences from creating NFTs on EVM networks, and why we think this moment marks a true change for non-fungible tokens.

1. On Sui, every created object is NFT and can belong to someone.

2. Sui is blazingly fast, scalable, and cheap to use - both for Creators and Collectors.

3. We use the hybrid approach for Sui NFTs’ metadata - not only does every token contain a link to the IPFS but more importantly it can store all metadata, image URL, attributes, name, description, etc., completely on-chain!

4. Omnisea managed to stay fully permissionless. So far, protocols on Sui for the NFT creation were closed. Creators needed to reach a platform, submit the application form, and either deploy the NFT contract or the platform itself would do that in a highly manual process. Omnisea gives you a no-code solution that you can use without asking to conduct a Drop.

5. Due to the on-chain metadata specifics, for Sui we don’t support the “Import from IPFS” feature. IPFS is only a secondary way for Sui collections to store metadata. Using the “Add files” and “Import metadata from .json files“ features, you’re able not only to deploy your files to IPFS from your device, but also save this produced metadata on-chain.

6. On-chain metadata will be the fuel for further NFTs utilities, use cases, and ultimately adoption. For instance, Web3 games implementing Sui NFTs “know” each token’s properties. So far, smart contracts (Solidity-based) couldn’t read NFT’s metadata on-chain. Now it’s possible.

7. This is our Mainnet Beta stage for Sui. During this period, we’ll be grateful for any received feedback and understanding that a lot will still improve. For instance, there’s currently no official standard for non-fungible tokens (like ERC721 on Ethereum) - we follow the best practices and combine what’s new with the well-known naming convention, but we cannot guarantee 100% compatibility with other existing protocols.

8. We chose the Ethos Wallet as the main wallet. It not only gives you an amazing wallet experience but also aggregates more Sui wallets - Martian, Suiet, Surf, and the default Sui wallet extension. You can see your minted NFTs directly in your wallet!

1. Get your Sui wallet.

2. Enter omnisea.org/create and Connect your wallet. Make sure you’ve switched it to the Mainnet network.

3. Set the collection’s basic information - name, avatar and background image, price, start, and end date, etc.

4. As described above, the “Import from IPFS” feature is unavailable for Sui due to the on-chain metadata specifics. Therefore, click on “Add files” and select the tokens’ images from your device.

5. Optional: If you intend to add more metadata, especially attributes, use the “Import metadata from .json files“ button and batch-select all your standard metadata .json files starting with 0.json. If your collection counts 1000 tokens, you need 1000 files and (if using this optional feature) 0-999.json files containing your metadata. Here’s an example of a valid metadata .json file with attributes:

   { "name": "ABC 1", "attributes": [{ "trait_type": "Background", "value": "Red" }, { "trait_type": "Wings", "value": "Angel Wings" }, { "trait_type": "Body", "value": "Orange Calm" } ] }

   The attributes array includes the attributes. Each attribute object is required to have the name under the trait_type property and its value under the value property. If you’re not familiar with that, we recommend some testing - for example, Add 3 images and after that 3 .json files (0.json, 1.json, 2.json; 0 is first because the first token ID is always 0) with the abovementioned structure.

6. Click “Launch” and confirm the transaction with your wallet. After success, you’ll be redirected to your Profile Page where you will see your created collection and access Settings where you’ll be able to, for example, set Whitelist and premint.

Now, it’s everything you had to do to enable your NFTs minting. Note, that each collection is by default non-revealed. So, let’s now explain how to put your metadata on-chain, and thus, how to reveal your tokens.

1. In your Profile Page, go to the created collection’s Settings.

2. You’ll see here 3 useful tabs - Whitelist, Reveal, and Pre-mint. Click on the Reveal tab.

3. Everything is quite simple here except the fact that revealing all your tokens by putting all their metadata on-chain at once is not possible due to the payload size limit of a single Sui transaction. We need to perform this operation in batches, in a few transactions.

4. Choose the "From Token ID” - by default, it’s 0. It’s the first token that you want to reveal (put metadata on-chain).

5. Choose the revealed tokens quantity (batch size). Let’s say, for example, 200.

6. Click on the “Reveal” button. This transaction will reveal (store) metadata of tokens with IDs from 0 to 199. Next, you can submit identical transactions (in this example, that would be From Token ID = 200). This is by far the most expensive operation because it literally saves on the Sui blockchain a lot of data. Note, that you don’t have to worry about the contents. We saved this information during the collection creation, and we’re setting the correct metadata for you - you just specify the batch size and the first token id in this batch.

7. If the metadata was set (revealed) before the token was minted, the mint transaction will automatically set the token metadata (image and attributes - if set).

8. If NFT was first minted, and you’ve revealed metadata later, Collectors are always able to perform an easy “refresh metadata” using the following method:

9. If you’ve minted NFT and it was revealed later by the Creator, you should refresh its metadata. Go to the Omnisea module via Sui Explorer and click on “refresh_token_metadata“ tab. It’ll ask you for 2 things: Omnisea internal object ID which is: 0xb43152c674130987b175098545bc4628c5269c1af57f46314b133f1f87c22940 and your NFT’s object ID that you can take from your wallet by going to the NFTs tab and clicking on your Omnisea NFT token - copy its Object ID and paste it into the second field of the refresh token metadata form. Now, confirm the transaction and your NFT metadata (image, attributes, etc.) will be updated.

It’s a bright day for us. We’re really excited about the current growth, especially during the zkSync ecosystem emergence. Sui offers us, creators, and collectors even more possibilities and a whole new world of NFTs combined with fast and cheap transactions. In the coming days, we hope for understanding and feedback - if there’s something that we’ll need to improve, we’ll do it. Remember that it’s a Beta stage so everything you do on Sui via Omnisea is new and we still evolve here. Always test your actions before making big moves, reach us via Discord support if needed, and always do your own research!

After many successful stories, we’re now entering completely new waters. Omnisea is proud to become the first truly permissionless NFT Drops Launchpad on Sui Mainnet to give Creators access to this groundbreaking technology.

In this article, we’ll guide you on how to create your Drop on Sui, what are the key differences from creating NFTs on EVM networks, and why we think this moment marks a true change for non-fungible tokens.

1. On Sui, every created object is NFT and can belong to someone.

2. Sui is blazingly fast, scalable, and cheap to use - both for Creators and Collectors.

3. We use the hybrid approach for Sui NFTs’ metadata - not only does every token contain a link to the IPFS but more importantly it can store all metadata, image URL, attributes, name, description, etc., completely on-chain!

4. Omnisea managed to stay fully permissionless. So far, protocols on Sui for the NFT creation were closed. Creators needed to reach a platform, submit the application form, and either deploy the NFT contract or the platform itself would do that in a highly manual process. Omnisea gives you a no-code solution that you can use without asking to conduct a Drop.

5. Due to the on-chain metadata specifics, for Sui we don’t support the “Import from IPFS” feature. IPFS is only a secondary way for Sui collections to store metadata. Using the “Add files” and “Import metadata from .json files“ features, you’re able not only to deploy your files to IPFS from your device, but also save this produced metadata on-chain.

6. On-chain metadata will be the fuel for further NFTs utilities, use cases, and ultimately adoption. For instance, Web3 games implementing Sui NFTs “know” each token’s properties. So far, smart contracts (Solidity-based) couldn’t read NFT’s metadata on-chain. Now it’s possible.

7. This is our Mainnet Beta stage for Sui. During this period, we’ll be grateful for any received feedback and understanding that a lot will still improve. For instance, there’s currently no official standard for non-fungible tokens (like ERC721 on Ethereum) - we follow the best practices and combine what’s new with the well-known naming convention, but we cannot guarantee 100% compatibility with other existing protocols.

8. We chose the Ethos Wallet as the main wallet. It not only gives you an amazing wallet experience but also aggregates more Sui wallets - Martian, Suiet, Surf, and the default Sui wallet extension. You can see your minted NFTs directly in your wallet!

1. Get your Sui wallet.

2. Enter omnisea.org/create and Connect your wallet. Make sure you’ve switched it to the Mainnet network.

3. Set the collection’s basic information - name, avatar and background image, price, start, and end date, etc.

4. As described above, the “Import from IPFS” feature is unavailable for Sui due to the on-chain metadata specifics. Therefore, click on “Add files” and select the tokens’ images from your device.

5. Optional: If you intend to add more metadata, especially attributes, use the “Import metadata from .json files“ button and batch-select all your standard metadata .json files starting with 0.json. If your collection counts 1000 tokens, you need 1000 files and (if using this optional feature) 0-999.json files containing your metadata. Here’s an example of a valid metadata .json file with attributes:

   { "name": "ABC 1", "attributes": [{ "trait_type": "Background", "value": "Red" }, { "trait_type": "Wings", "value": "Angel Wings" }, { "trait_type": "Body", "value": "Orange Calm" } ] }

   The attributes array includes the attributes. Each attribute object is required to have the name under the trait_type property and its value under the value property. If you’re not familiar with that, we recommend some testing - for example, Add 3 images and after that 3 .json files (0.json, 1.json, 2.json; 0 is first because the first token ID is always 0) with the abovementioned structure.

6. Click “Launch” and confirm the transaction with your wallet. After success, you’ll be redirected to your Profile Page where you will see your created collection and access Settings where you’ll be able to, for example, set Whitelist and premint.

Now, it’s everything you had to do to enable your NFTs minting. Note, that each collection is by default non-revealed. So, let’s now explain how to put your metadata on-chain, and thus, how to reveal your tokens.

1. In your Profile Page, go to the created collection’s Settings.

2. You’ll see here 3 useful tabs - Whitelist, Reveal, and Pre-mint. Click on the Reveal tab.

3. Everything is quite simple here except the fact that revealing all your tokens by putting all their metadata on-chain at once is not possible due to the payload size limit of a single Sui transaction. We need to perform this operation in batches, in a few transactions.

4. Choose the "From Token ID” - by default, it’s 0. It’s the first token that you want to reveal (put metadata on-chain).

5. Choose the revealed tokens quantity (batch size). Let’s say, for example, 200.

6. Click on the “Reveal” button. This transaction will reveal (store) metadata of tokens with IDs from 0 to 199. Next, you can submit identical transactions (in this example, that would be From Token ID = 200). This is by far the most expensive operation because it literally saves on the Sui blockchain a lot of data. Note, that you don’t have to worry about the contents. We saved this information during the collection creation, and we’re setting the correct metadata for you - you just specify the batch size and the first token id in this batch.

7. If the metadata was set (revealed) before the token was minted, the mint transaction will automatically set the token metadata (image and attributes - if set).

8. If NFT was first minted, and you’ve revealed metadata later, Collectors are always able to perform an easy “refresh metadata” using the following method:

9. If you’ve minted NFT and it was revealed later by the Creator, you should refresh its metadata. Go to the Omnisea module via Sui Explorer and click on “refresh_token_metadata“ tab. It’ll ask you for 2 things: Omnisea internal object ID which is: 0xb43152c674130987b175098545bc4628c5269c1af57f46314b133f1f87c22940 and your NFT’s object ID that you can take from your wallet by going to the NFTs tab and clicking on your Omnisea NFT token - copy its Object ID and paste it into the second field of the refresh token metadata form. Now, confirm the transaction and your NFT metadata (image, attributes, etc.) will be updated.

It’s a bright day for us. We’re really excited about the current growth, especially during the zkSync ecosystem emergence. Sui offers us, creators, and collectors even more possibilities and a whole new world of NFTs combined with fast and cheap transactions. In the coming days, we hope for understanding and feedback - if there’s something that we’ll need to improve, we’ll do it. Remember that it’s a Beta stage so everything you do on Sui via Omnisea is new and we still evolve here. Always test your actions before making big moves, reach us via Discord support if needed, and always do your own research!