Summary: The proposal aims to introduce and deploy PRL, the upgraded version of the MIMO token, the governance token of the Parallel Protocol.
Context: In October 2024 we published a post in the governance forum, with the aim of discussing and exploring a potential upgrade of the MIMO token, the governance token of the Parallel. Following positive feedback from DAO members and a successful internal Proof-of-Concept we decided to develop the MIMO token upgrade.
Introduced in 2021 with the launch of the Parallel protocol, the MIMO token is the governance token that controls the protocol in all its aspects. However, many people confused Mimo Labs, the company that initially developed the Parallel protocol, with the Parallel protocol; partly due to the ticker of the governance token being MIMO. With the primary aim of consolidating the Parallel protocol brand, we propose to migrate the MIMO token to a new governance token.
Rationale:
Motivations: The proposal is motivated by several considerations, especially brand harmonization, in line with the upcoming soft visual rebranding; upgrade tokens capabilities, including permit & an unified secure bridging module; as well as increasing token attractivity in order to revitalize the protocol in correlation with upcoming new tokenomics.
The technical implementation can be found here: https://github.com/parallel-protocol/parallel-prl/tree/main
PRL Token: The new token will be called 'PRL'. It will be natively deployed on Ethereum (with crosschain features, detailed later) and will inherit OpenZeppelin's ERC20 standard and ERC20Permit. It will have a total supply of 1,000,000,000 tokens, fully minted at token deployment (and deposited in the PrincipalMigrationContract). The PRL total supply will be the same as the MIMO total supply, allowing a 1:1 conversion for users. Moreover, the token will be entirely immutable, with the impossibility of minting more tokens or pausing transfers.
Token specifications:
PRL Technical Architecture: Technical Architecture:
LayerZero Infrastructure: LayerZero is an immutable, censorship-resistant, and permissionless smart contract protocol that enables anyone to send, verify, and execute arbitrary messages on a supported blockchain. Using smart contracts deployed on each chain, in combination with Decentralized Verifier Networks (DVNs) and Executors, LayerZero enables different blockchains to seamlessly interact with one another. In LayerZero, message verification and execution are separated into two distinct phases, providing developers with more control over their application's security configuration and independent execution.
Decentralized Verifier Networks (DVNs): DVNs verify cross-chain messages. This permissionless role empowers any entity capable of verifying cross-chain data packets to join LayerZero as a DVN. Any native bridge, third-party bridge, middle chain, oracle, or other verification method may be used as a DVN, thereby avoiding vendor lock-in at the security level. As LayerZero has a modular design, application owners can combine DVNs to maximize verification for characteristics like security, cost, speed, or any parameter an application might want. In other words, LayerZero allows applications to configure any number and type of decentralized verifier networks (DVNs) to verify their cross-chain messages.
Permissionless Execution (executors): Any entity can run an Executor, as it is an entirely permissionless role. The Executor ensures the smooth execution of a message on the destination chain by offering gas abstraction to the end-user. Executors do this by quoting end-users on the source chain in the source chain gas token while executing the transaction automatically on the destination chain. Much like applications can select a DVN set, they can also configure their application to choose a certain Executor or group of Executors. Applications also have the ability to build and run their own executor (as they can for DVNs) or operate without an Executor and have end-users manually invoke ‘lzReceive’ via LayerZero Scan.
Bridging Module Specifications:
Bridging Module Implementation:
Audits: The PRL codebase, including the migration architecture and the bridging module have been extensively audited by 2 different audit companies:
MIMO -> PRL Migration: The total MIMO token supply is 1,000,000,000 tokens. As the PRL token will also have a supply of 1,000,000,000 tokens, we propose a 1:1 migration (1 MIMO -> 1 PRL). This means there will be no new token inflation, and no prejudice to current and future token holders. In order to not penalize any MIMO holders, we built the migration module without the possibility of setting a migration deadline, allowing MIMO token holders to migrate to the PRL token without any deadline. However, the MIMO -> PRL migration will be definitive, and it will be impossible to perform the reverse migration once it has been completed. The DAO will also be able to pause/unpause migration contracts on each chain.
MIMO tokens currently locked as vMIMO on Ethereum & Polygon PoS will be unlocked in order to let holders migrate to the PRL token. Following the multichain[.]org hack in 2023, holders of MIMO tokens on Fantom found themselves unable to bridge their tokens back to Ethereum. Thanks to the crosschain PRL migration architecture, MIMO blocked on Fantom will also be migrated to PRL on any chain, enabling holders to regain full possession of their tokens.
Ethereum Migration Workflow:
Chain A -> Ethereum Migration Workflow:
Chain A -> X Migration Workflow:
Means:
Technical implementation:
Voting Options:
Author(s): Cooper Labs