How to Bridge Assets to the Quantova Network

Quantova enables secure interoperability by allowing selected external blockchain assets to be bridged and wrapped into the Quantova Network, where they execute under the Quantova Virtual Machine QVM.

Bridging converts supported external assets such as ETH, BSC, Tron, and other EVM compatible tokens into Quantova native representations. Once bridged, these assets operate entirely within Quantova’s execution environment, benefiting from deterministic execution, quantum resistant security architecture, and protocol level governance controls.

All bridged assets are managed and accessed using QMask, Quantova’s native wallet, and are subject to Quantova’s execution rules, fee model, and permission framework. The native asset QTOV is used for transaction fees and execution across the network.

This guide explains how to safely bridge assets into Quantova, what occurs during the wrapping process, and how to verify that your assets are available for use within the Quantova ecosystem.

Prerequisites Quantova specific

Before bridging assets to Quantova, ensure that you

Common mechanisms include

• Have a QMask wallet set up and secured
• Hold supported assets on an external network e.g. Ethereum, BSC, Tron, or other approved QVM networks
• Maintain sufficient balance of the source network’s native asset to cover external transaction fees
• Understand that bridged assets become Quantova network assets, governed by QVM rules

1. Select a Supported Source Network

Choose the external blockchain network from which you want to bridge assets. Quantova currently supports Ethereum, BSC, Tron, and approved QVM compatible networks.

Only assets originating from supported networks can be wrapped and represented on Quantova.

2. Access the Official Quantova Bridge

Navigate to the officially supported Quantova bridge interface. This ensures assets are wrapped using verified contracts aligned with Quantova’s security and compliance framework.

3. Connect Using QMask

Connect your QMask wallet to the bridge interface.

QMask serves as the authorization layer for asset wrapping, transaction confirmation, and permission control within Quantova.

4. Define Asset Type and Amount

Select the asset you wish to bridge and specify the amount.

The bridge will display the resulting Quantova wrapped asset and any applicable execution or network fees.

5. Authorize and Confirm the Bridge Transaction

Approve the transaction in QMask.

This step authorizes the locking of the asset on the source network and the minting of its Quantova native representation under QVM rules.

6. Wait for Finalization and Verification

The bridge will process the transaction and wait for sufficient confirmations on the source network.

Once finalized, the wrapped asset becomes available on the Quantova Network.

7. View the Asset in QMask

After completion, the bridged asset will appear in QMask as a Quantova network asset.

No additional network configuration is required QMask natively supports Quantova.

Frequently Asked Questions

What happens to my asset when it is bridged?

The original asset is locked on its source network, and a Quantova native representation is minted for use within the Quantova ecosystem.

Can I bridge assets back to their original network?

Yes. Bridged assets can be unwrapped and returned to their originating network using the Quantova bridge, subject to network conditions and finality requirements.

Do bridged assets follow Quantova rules?

Yes. Once bridged, assets are governed by QVM execution logic, Quantova fee mechanics, and protocol level security controls.

Why does Quantova restrict supported networks?

Network support is limited to ensure security, deterministic execution, and compliance with Quantova’s infrastructure and governance standards.