MIP-35.2┃Deploy the paUSD Bridging Module

Summary: The proposal aims to deploy the paUSD bridging module using Tunnel, the Parallel Bridging Module.

Context Following the introduction of Tunnel, the Parallel Bridging Module, in the MIP-35┃Introducing Tunnel, the Parallel Bridging Module, we propose to deploy it for the paUSD token.

Rationale: We propose to deploy a limited version of the paUSD bridging module to start, then to increase the limits and the number of blockchains where the bridging module would be deployed in the future via another proposal.

We propose to deploy the paUSD bridging module on Ethereum and Polygon PoS with these parameters:

Ethereum:

• DVNs: (2 of 1 of 2)
  • Required: 2
    • LayerZero Labs
    • Polyhedra
  • Optionals: 1 of 2
    • Nethermind
    • Google Cloud
• Mint Limits:
  • Daily: 15,000.00
  • Global: 100,000.00
• Burn Limits:
  • Daily: 15,000.00
  • Global: 100,000.00
• Fees:
  • Rate: 0.00%
• Isolate Mode:
  • No

Polygon PoS:

• DVNs: (2 of 1 of 2)
  • Required: 2
    • LayerZero Labs
    • Polyhedra
  • Optionals: 1 of 2
    • Nethermind
    • Google Cloud
• Mint Limits:
  • Daily: 15,000.00
  • Global: 100,000.00
• Burn Limits:
  • Daily: 15,000.00
  • Global: 100,000.00
• Fees:
  • Rate: 0.00%
• Isolate Mode:
  • No

The approval of this proposal is conditioned on the approval of the MIP-35. This means that if this proposal is approved by the DAO but the MIP-35 is rejected by the DAO, this proposal will automatically be rejected.

Means:

• Human Resources: Multisig signers will need to sign transactions to execute the proposal.
• Treasury Resources: No treasury resources used.

Technical implementation: The technical implementation details are available on the forum post, due to Snapshot limitations.

Voting Options:

• Accept the deployment of the paUSD Bridging Module
• Against/Rework the proposal
• Abstain

Author(s): Cooper Labs