Question 1

What is MGO?

Accepted Answer

MGO is the native token of Mango Network. Mango Network positions itself as a multi-VM omnichain infrastructure network that supports EVM and MoveVM. Multi-VM means that the network is designed for more than one smart-contract execution environment: EVM serves contracts compatible with the Ethereum Virtual Machine, while MoveVM serves contracts built with the Move language and its execution model. Native-token status does not by itself indicate that MGO carries any yield, governance, or distribution rights; such rights require separate formal rules.

Question 2

What practical uses does MGO have?

Accepted Answer

According to the Mango Network v2.0 whitepaper, in the OP-Mango architecture, MGO is used to pay Gas for batch-submitting Layer 2 transactions to Ethereum Layer 1. Batch submission aggregates multiple Layer 2 activities before submitting them to Layer 1, using Layer 1 to complete the related settlement or data-submission steps. This describes a specific fee use within that architecture. It does not mean that every type of Mango Network operation necessarily settles on Ethereum Layer 1 in the same way, nor can it be used to infer that all OP-Mango functions are currently available. The exact fees ultimately paid by users still depend on the actually deployed product, transaction path, and fee rules at the time.

Question 3

What does a multi-VM network mean for users?

Accepted Answer

EVM and MoveVM are two types of smart-contract execution environments. EVM supports contract execution methods commonly used in the Ethereum ecosystem; MoveVM is used to execute Move-language contracts and adopts a different programming and asset model. For users and developers, the significance of a multi-VM design is that the network attempts to enable applications in different execution environments to collaborate through cross-chain communication, rather than requiring every application to use the same virtual machine. However, interoperability does not mean that any contract, asset, or wallet is natively compatible: transferable assets, call paths, and support scope depend on deployed bridge and application implementations.

Question 4

What stages should be understood in omnichain interoperability?

Accepted Answer

Mango Network's “omnichain” positioning refers to cross-chain communication and multi-VM interoperability: applications may attempt to transmit information and coordinate operations across different execution environments or chains. An operation across environments usually adds steps such as message delivery, verification, or settlement compared with a local call on a single chain. Therefore, confirm separately whether the source transaction has completed, the cross-chain message has been processed, and the destination operation has succeeded. Sending from the source does not necessarily mean execution on the destination has completed.

Question 5

How should the difference between the website positioning and whitepaper architecture be understood?

Accepted Answer

The official website positions Mango Network as multi-VM omnichain infrastructure and provides explorer, validator, and ecosystem entry points; the whitepaper explains architectural designs such as Layer 1, multi-VM interoperability, and OP-Mango. These two types of materials serve different purposes: the former explains project positioning and entry points, while the latter explains design mechanisms. Therefore, when reading performance or architectural statements in the whitepaper, distinguish between design goals, technical approaches, and functions actually available in specific products. The entire contents of the whitepaper cannot be treated directly as evidence that every application, network function, or user path is currently live.

Question 6

What should be confirmed before using multi-VM or cross-chain functions?

Accepted Answer

Before using assets or cross-chain functions related to Mango Network, confirm whether the application being used supports the target network, target virtual machine, and target asset. MGO's native-token status does not mean it has the same form in every compatible environment or can be received directly by every address. The risk in cross-chain or cross-VM operations is that the path has multiple stages: choosing the wrong network or asset form may prevent the receiving side from recognizing it; while a message is still being processed, the destination side may not yet have an available balance. Follow the network, asset identifier, and transaction status shown by the application, rather than judging solely by name or ticker.

Mango Network (MGO) Price

Price of Mango Network (MGO) Today in USD