Smart Contracts

Purpose

Describes high-level architecture and requirements for MPOW smart contracts.

Components

• MPOW Token Contract

  • 0x097ac90a427234e9b4e78e4877d2aa3eadff0112
  • ERC-20 implementation.
  • Mint function restricted to designated minter (backend or controller contract).
  • Optional burn function.

• Liquidity Contracts (tbd)

  • Interact with DEX primitives for adding/removing liquidity.

• DAO / Governance Contracts (tbd)

  • Manage parameters such as ConversionFactor and allocation rules.

Requirements

• Use of audited, battle-tested libraries (e.g., OpenZeppelin).

• Clear access control:

  • Distinguish between owner/admin roles and DAO roles.
  • Avoid single points of failure.

• Upgradeability, if present, MUST be transparent and controlled by governance procedures.