V2 Testnet is here and we couldn’t be happier to begin the next chapter of Omnisea's growth and development. The last few have been great progress for us. After successful deployment on zkSync Era Mainnet, we’ve become the go-to Launchpad for the NFT Creators. Thousands of collections were created, and hundreds of thousands of tokens have been minted! We’ve also experienced a large spike of interest around our OFTv1 Governance token - OSEA. We’re grateful for all of that but we can’t and won’t stop here.

Yesterday, as promised, we launched the long-awaited V2 Testnet. The main goals of this upgrade are to create an improved, more advanced, and even more intuitive Drops Launcher, as well as to introduce ONFTs (Omnichain Non-fungible Token) powered by LayerZero. All collections created via Omnisea are automatically ONFTs able to be natively deployed and transferred between chains. We’re the first platform to allow that without having technical experience. Moreover, thanks to the UI, it’s now really easy to make your collection cross-chain and allow your Holders to the bridge. This opens every NFT to more possibilities, marketplaces, and protocols, and makes collections more accessible in general. Omnichain NFTs are also making your intellectual property secured on more than one blockchain. We understand that this is just the beginning of the Omnichain movement but we want to be at its forefront.

Launching Drops using our V1 was already simple and lately so appreciated by Creators on the zkSync blockchain. We still wanted to take it to the next level both in terms of functionalities and intuitiveness. Basically, all you need to know about the creation of NFT Drops using V2 is that the deployment process is now really basic - the only thing needed are the collection’s name, image, and tokens (uploaded using your files or imported from IPFS with an existing CID).

1. Go to the Create Page.

2. Set the abovementioned required details.

3. Use the Settings tab to access optional features available only before deployment such as Royalties, custom symbol (ticker), description (part of the contract’s metadata), etc.

4. Connect your wallet to the network on which you want to deploy your collection.

5. Launch your Drop - deploy the collection’s contract.

After successful deployment, you’ll be redirected to your Profile Page where you can see all your created collections. Click on your newest Drop to go to its Page.

As you can see, the first thing is that the red status badge at the top indicates that the “Schedule” is not yet set. Click on it or go to the Settings tab manually using the mini tabs component at the right. You’ll see all the settings available after the collection deployment - Scheduler among the others.

1. Open the Schedule card and click on the “Add new Phase“ button.

2. Set all the details of your next Phase (add phases chronological!).

3. You can set any number of Phases - each of them should have its name, price (0 means Free Mint), start date (which is automatically the end of the previous phase), the limit of mints per address, and optionally Whitelist - in case of Public phase, just don’t add any address in the Whitelist field, and it’ll be available for everyone.

In this example, we’ve created one Whitelist phase (just one address) and next, we also added a Public phase for everyone that starts a few hours after the WL.

As you can see in the picture below, the current phase is Whitelist, but the Drop Page now also indicates the upcoming phase which is Public Mint in this case.

Besides the Drop’s Schedule, you can also access more important settings such as Allocations & Payout, Custom Link (has to be unique), and soon more.

About allocations, you can now split revenue between many addresses - for example, your partners or co-creators. Provide eligible payout addresses and their respective percentages. In total, allocation percentages should sum up to 100%.

Having in mind not only the best interest of the Creators but also the Collectors’ (minters) safety, we’ve decided to redesign the payouts mechanism. Now, the proceeds won’t go directly to the Creator’s address. Instead, all transferred (paid) funds will be locked for 14 days - the Safety Period (two weeks after the Drop’s End Date). Omnisea won’t have access to these assets. Our ability is to flag the Drop in case of, for instance, violating the copyrights of a third-party artist, or committing other harmful activity, especially against the Collectors’ best interest and the collection’s value. In case of flagging, the Safety Period will be extended to 21 days. Omnisea administration can either unflag the Drop or sustain the decision and thus making the Collectors (minters) eligible for full Refunds!

Like stated in the beginning, one of the main goals of V2 is to introduce Omnichain NFTs to the masses. Omnisea was born with the idea of the unification of a fragmented NFT ecosystem (between the growing number of blockchains). ONFTs powered by LayerZero cross-chain messaging protocol are the perfect and ultimate tool to accomplish this goal.

If, and when you want, go to the ONFT Management tab and deploy your collection (ONFT) on more and more chains. In this example, we’ve created our Drop on Moonbeam and decided to deploy the collection on Avalanche.

1. Go to the ONFT Management tab.

2. Click “Add new chain”.

3. Choose the blockchain on which you want to deploy your connection.

4. Connect to this chain’s network (Avalanche Fuji in this case).

5. Click “Deploy to Avalanche“ and confirm the transaction.

Before briding tokens between these two chains, the basic security mechanism requires us to first “Connect” them - in both directions! This prevents your tokens to be minted by unauthorized contracts and accepting cross-chain messages only from the ONFT on a second chain.

1. Click on the newly added chain - Avalanche - and click on the Moonbeam icon. Confirm transaction to “set remote”.

2. Do the same in the reverse direction - connect again to the Moonbeam network, click on the Moonbeam tab, and add Avalanche to the “Connected” contracts.

Now, our collection is ready to accept cross-chain transfers.

As you can see, the third tab on the Drop Page is now available for everyone to choose - the collection’s Bridge Page.

If you’re a Holder of a token from this collection:

1. Go to the Bridge Page.

2. Connect to the (source) chain from which you want to transfer your token.

3. Choose the Token ID you want to bridge.

4. Select the Destination chain to which you want to bridge your token.

5. Click “Send to [Destination chain]” and accept both transactions - Approval, and Transfer.

The badge at the top of the Bridge Page indicates the status of the cross-chain transfer. In the picture above it’s Pending - after a few seconds the “LayerZero Scan“ button will also appear to enable checking the full transaction’s details and state monitoring. In around 2 minutes the token should be delivered to the destination chain.

The hustle won’t stop here. After just the first day of the V2 Testnet, we already saw some ONFTs created with at least a few (or even all) blockchains connected! It’s a huge indicator that shows it’s now easy and intuitive enough to manage your Omnichain collection and deploy it on more and more chains whenever you want it.

And it’s just Phase One of the V2 Testnet…

In a few weeks, we’ll introduce Phase Two, which will make it possible to transform any existing NFT Collection into ONFT. This is the final piece of the puzzle needed to unite the NFT ecosystem in the long term. We also prepare more surprises and big features to make the Omnisea Community proud and successful over time!

V2 Testnet is here and we couldn’t be happier to begin the next chapter of Omnisea's growth and development. The last few have been great progress for us. After successful deployment on zkSync Era Mainnet, we’ve become the go-to Launchpad for the NFT Creators. Thousands of collections were created, and hundreds of thousands of tokens have been minted! We’ve also experienced a large spike of interest around our OFTv1 Governance token - OSEA. We’re grateful for all of that but we can’t and won’t stop here.

Yesterday, as promised, we launched the long-awaited V2 Testnet. The main goals of this upgrade are to create an improved, more advanced, and even more intuitive Drops Launcher, as well as to introduce ONFTs (Omnichain Non-fungible Token) powered by LayerZero. All collections created via Omnisea are automatically ONFTs able to be natively deployed and transferred between chains. We’re the first platform to allow that without having technical experience. Moreover, thanks to the UI, it’s now really easy to make your collection cross-chain and allow your Holders to the bridge. This opens every NFT to more possibilities, marketplaces, and protocols, and makes collections more accessible in general. Omnichain NFTs are also making your intellectual property secured on more than one blockchain. We understand that this is just the beginning of the Omnichain movement but we want to be at its forefront.

Launching Drops using our V1 was already simple and lately so appreciated by Creators on the zkSync blockchain. We still wanted to take it to the next level both in terms of functionalities and intuitiveness. Basically, all you need to know about the creation of NFT Drops using V2 is that the deployment process is now really basic - the only thing needed are the collection’s name, image, and tokens (uploaded using your files or imported from IPFS with an existing CID).

1. Go to the Create Page.

2. Set the abovementioned required details.

3. Use the Settings tab to access optional features available only before deployment such as Royalties, custom symbol (ticker), description (part of the contract’s metadata), etc.

4. Connect your wallet to the network on which you want to deploy your collection.

5. Launch your Drop - deploy the collection’s contract.

After successful deployment, you’ll be redirected to your Profile Page where you can see all your created collections. Click on your newest Drop to go to its Page.

As you can see, the first thing is that the red status badge at the top indicates that the “Schedule” is not yet set. Click on it or go to the Settings tab manually using the mini tabs component at the right. You’ll see all the settings available after the collection deployment - Scheduler among the others.

1. Open the Schedule card and click on the “Add new Phase“ button.

2. Set all the details of your next Phase (add phases chronological!).

3. You can set any number of Phases - each of them should have its name, price (0 means Free Mint), start date (which is automatically the end of the previous phase), the limit of mints per address, and optionally Whitelist - in case of Public phase, just don’t add any address in the Whitelist field, and it’ll be available for everyone.

In this example, we’ve created one Whitelist phase (just one address) and next, we also added a Public phase for everyone that starts a few hours after the WL.

As you can see in the picture below, the current phase is Whitelist, but the Drop Page now also indicates the upcoming phase which is Public Mint in this case.

Besides the Drop’s Schedule, you can also access more important settings such as Allocations & Payout, Custom Link (has to be unique), and soon more.

About allocations, you can now split revenue between many addresses - for example, your partners or co-creators. Provide eligible payout addresses and their respective percentages. In total, allocation percentages should sum up to 100%.

Having in mind not only the best interest of the Creators but also the Collectors’ (minters) safety, we’ve decided to redesign the payouts mechanism. Now, the proceeds won’t go directly to the Creator’s address. Instead, all transferred (paid) funds will be locked for 14 days - the Safety Period (two weeks after the Drop’s End Date). Omnisea won’t have access to these assets. Our ability is to flag the Drop in case of, for instance, violating the copyrights of a third-party artist, or committing other harmful activity, especially against the Collectors’ best interest and the collection’s value. In case of flagging, the Safety Period will be extended to 21 days. Omnisea administration can either unflag the Drop or sustain the decision and thus making the Collectors (minters) eligible for full Refunds!

Like stated in the beginning, one of the main goals of V2 is to introduce Omnichain NFTs to the masses. Omnisea was born with the idea of the unification of a fragmented NFT ecosystem (between the growing number of blockchains). ONFTs powered by LayerZero cross-chain messaging protocol are the perfect and ultimate tool to accomplish this goal.

If, and when you want, go to the ONFT Management tab and deploy your collection (ONFT) on more and more chains. In this example, we’ve created our Drop on Moonbeam and decided to deploy the collection on Avalanche.

1. Go to the ONFT Management tab.

2. Click “Add new chain”.

3. Choose the blockchain on which you want to deploy your connection.

4. Connect to this chain’s network (Avalanche Fuji in this case).

5. Click “Deploy to Avalanche“ and confirm the transaction.

Before briding tokens between these two chains, the basic security mechanism requires us to first “Connect” them - in both directions! This prevents your tokens to be minted by unauthorized contracts and accepting cross-chain messages only from the ONFT on a second chain.

1. Click on the newly added chain - Avalanche - and click on the Moonbeam icon. Confirm transaction to “set remote”.

2. Do the same in the reverse direction - connect again to the Moonbeam network, click on the Moonbeam tab, and add Avalanche to the “Connected” contracts.

Now, our collection is ready to accept cross-chain transfers.

As you can see, the third tab on the Drop Page is now available for everyone to choose - the collection’s Bridge Page.

If you’re a Holder of a token from this collection:

1. Go to the Bridge Page.

2. Connect to the (source) chain from which you want to transfer your token.

3. Choose the Token ID you want to bridge.

4. Select the Destination chain to which you want to bridge your token.

5. Click “Send to [Destination chain]” and accept both transactions - Approval, and Transfer.

The badge at the top of the Bridge Page indicates the status of the cross-chain transfer. In the picture above it’s Pending - after a few seconds the “LayerZero Scan“ button will also appear to enable checking the full transaction’s details and state monitoring. In around 2 minutes the token should be delivered to the destination chain.

The hustle won’t stop here. After just the first day of the V2 Testnet, we already saw some ONFTs created with at least a few (or even all) blockchains connected! It’s a huge indicator that shows it’s now easy and intuitive enough to manage your Omnichain collection and deploy it on more and more chains whenever you want it.

And it’s just Phase One of the V2 Testnet…

In a few weeks, we’ll introduce Phase Two, which will make it possible to transform any existing NFT Collection into ONFT. This is the final piece of the puzzle needed to unite the NFT ecosystem in the long term. We also prepare more surprises and big features to make the Omnisea Community proud and successful over time!