Developer & Integration Resources


Overview

Mynt (USDm) is designed for developers building the next generation of verifiable, private, and composable DeFi applications. Architected for modularity and chain-native performance, USDm exposes a suite of programmable components across Monad and MegaETH, along with standardized SDKs and hooks to support privacy-enhanced workflows via SP1 zkVM.

This section outlines the core infrastructure, tooling, and proof-based integration primitives available to builders seeking to embed USDm or wUSDm into wallets, DEXs, lending protocols, DAOs, or novel zk-native applications.


11.1 Core Contracts and Verifiers (Planned Addresses)

USDm and wUSDm will be governed by a set of modular smart contracts on both Monad and MegaETH, including:

  • USDm: ERC-20 mintable stablecoin, non-rebasing

  • wUSDm: zk-verifiable wrapped token tied to balance attestations

  • VaultManager: Asset-specific minting logic with isolated risk modules

  • ProofManager: SP1 verification entrypoint for submitted zk proofs

  • OracleAdapter: Aggregator module integrating feeds from Pyth and ChainSight

Note: Final contract addresses and full ABI schemas will be published alongside public deployment.


11.2 USDm Token Specification

Parameter
Value

Name

Mynt USD

Symbol

USDm

Standard

ERC-20

Decimals

18

Transfer Behavior

Fully composable and transferrable

Inflation Model

Non-inflationary

Privacy Layer

Optional (via wUSDm wrapping)

For applications requiring traceable USDm flows (e.g., open DEXs), the base ERC-20 token can be used directly. For applications requiring privacy, developers should use wUSDm in conjunction with SP1 proof interfaces.


11.3 SDKs and Tooling (Planned)

To facilitate integration, the USDm protocol will expose SDKs across the following layers:

  • Typescript SDK: Vault creation, mint/burn flows, wUSDm wrapping/unwrapping, proof packaging

  • SP1 Proof Kit: CLI + Rust bindings to compile, generate, and serialize zk proofs for wUSDm operations

  • On-chain JS Bindings: ABI-typed modules for interacting with VaultManager and ProofManager

  • Proof Verification Subgraph: Index of validated proof events and zk circuit hashes (planned)

These SDKs allow developers to:

  • Query user balances and vault status

  • Package SP1-compatible proofs from frontend or backend contexts

  • Submit proofs that can execute logic without revealing underlying wallet state


11.4 Integration Use Cases

A. DEXs

  • Standard Integration: Pair USDm in open pools (USDC, MON, ETH)

  • Private Pools: Accept wUSDm proofs as routing primitives in MEV-immune private AMMs

  • Oracle Routing: Use real-time oracles to detect off-peg arbitrage and simulate proof-based rebalance strategies

B. Lending Protocols

  • USDm as Borrowable Asset: Integrate USDm directly with open vaults

  • wUSDm Verifier Hook: Accept proof of balance attestations in lieu of transfer-based collateral

  • Zero-Knowledge Loan Repayment: Integrate zk-spend proofs for private repayment flows

C. Wallets & Frontends

  • Native USDm Support: Display minting, burning, vault health, and oracle pricing

  • Proof Generation UX: Embed SP1 CLI or SDK to enable in-wallet proof construction and submission

  • Gasless zk Attestations: Allow user to sign and submit proofs without direct interaction, via relayers

D. DAOs & Stable Reserves

  • Treasury Deployment: Use USDm as reserve asset or disbursement token

  • Private Contributor Payments: Use wUSDm proofs to execute confidential payments without exposing DAO-to-wallet relationships

  • zk DAO Modules: Build logic conditioned on off-chain proofs verified on-chain (e.g., bounty claims, grants, voting attestations)


11.5 Testnet & Deployment

  • Testnet Rollout: Full vault deployment on Monad testnet and MegaETH testnet

  • Sandboxed zk Toolkit: Local SP1 proof testing environment with live mock verifiers

  • Testnet Faucet: MON, LST, and test ETH tokens available via on-chain faucet endpoints

  • Public zk Dashboard: Live explorer for submitted proof hashes, outcomes, and event logs

  • Bug & Integration Reporting: GitHub Issues + Discord developer forum


11.6 Privacy-Enabled Development Workflow

To support private integrations, developers are encouraged to follow the modular zk flow:

  1. Wrap USDm → wUSDm (on-chain contract call)

  2. Generate zk Proof (using SP1 toolkit with desired circuit template)

  3. Submit Proof to ProofManager on Monad or MegaETH

  4. Trigger On-Chain Logic: Validated proofs can then unlock downstream logic (e.g., liquidity minting, private spend, DAO payments)

This enables composability without token transfers and allows USDm to act as a stateful primitive, not just a balance.


11.7 Contributing

Developers can contribute across three core verticals:

Area
Contribution Path

Protocol

Submit GitHub PRs for vault logic, verifiers, hooks

zk Circuits

Author SP1-compatible programs for novel proof cases

Frontends & UX

Build interfaces for USDm usage and zk interaction

Security researchers, zk circuit engineers, and protocol architects are all encouraged to participate. A formal contributor guide and governance onboarding framework will be released post-audit.


USDm is not just a stablecoin—it is a programmable financial substrate. With SP1-powered privacy and a verifiable proof-based design, developers can now build applications where value is proven, not moved.


Last updated