MolePin Cross-Chain Protocol (MCCP)

🌐 Language: English · 한국어

A real-world journey from LayerZero V2 OFT deployment to designing a self-operated cross-chain protocol.

This repository documents the complete engineering process, the failures discovered, the decisions made, and the architecture that emerged.

---

What this is

This is not a marketing repo. It is the engineering trail of 28+ hours of multichain deployment work, documented exactly as it happened — including the mistakes, the surprises, and the pivot.

The trail covers:

1. Deploying the MolePin (MOL) token across BSC, Polygon, and Tron mainnet using LayerZero V2 OFT
2. Discovering through direct experiment that LayerZero's BSC ↔ Tron pathway is operationally broken for new OApps, despite documentation claiming support
3. Systematically comparing alternatives: Wormhole NTT, Chainlink CCIP CCT, Stargate, Defiway
4. Validating that no single existing protocol supports Tron + Solana + TON for custom token issuers
5. Designing MCCP (MolePin Cross-Chain Protocol) — a self-operated, LayerZero-inspired protocol with a variable fee model and an open block explorer

If you are evaluating cross-chain infrastructure for a token project, this trail will save you weeks.

---

Related repository

This work is the successor to molepin-v2-verification — the on-chain verification trail of the MolePin v2 omnichain LayerZero V2 OFT deployment across BSC, Polygon, and Tron.

That deployment is what surfaced the Tron pathway failure documented here in docs/04-the-tron-failure.md. MCCP is the architectural answer to that failure.

molepin-v2-verification    →    molepin-mccp (this repo)
"what we deployed"              "what we built when LayerZero couldn't serve us"

Read v2-verification first if you want the deployment context. Read this repo if you want the strategy, architecture, and self-operated protocol design that emerged from that work.

---

Table of contents

Part 1 — The deployment story

• docs/01-context-and-goal.md — What we set out to build and why
• docs/02-deployment-walkthrough.md — BSC, Polygon, Tron deployment step by step
• docs/03-peer-and-dvn-setup.md — LayerZero V2 peer mesh and DVN configuration

Part 2 — The discovery

• docs/04-the-tron-failure.md — How BSC↔Tron messages got stuck and what we learned
• docs/05-hypothesis-testing.md — Systematic experiments to isolate the cause
• docs/06-evidence-and-data.md — Transaction hashes, fee quotes, registry data

Part 3 — The comparison

• docs/07-protocol-comparison.md — LayerZero, Wormhole, CCIP, Stargate, Defiway side by side
• docs/08-fee-model-comparison.md — Real numbers from each protocol's APIs
• docs/09-why-no-single-protocol-fits.md — Market gap analysis

Part 4 — The pivot

• docs/10-mccp-architecture.md — Self-operated protocol design
• docs/11-fee-policy.md — Variable fee model
• docs/12-block-explorer-design.md — scan.molepin.com architecture
• docs/13-security-model.md — Multisig, validators, progressive decentralization
• docs/14-roadmap.md — Phase 1 through Phase 4

Part 5 — Appendices

• docs/A1-contract-addresses.md — All deployed addresses with verification links
• docs/A2-scripts-reference.md — Deployment and configuration scripts
• docs/A3-glossary.md — Terms used throughout this trail
• docs/A4-references.md — External sources and registry APIs
• docs/A5-changelog.md — Version history and planned updates

🇰🇷 Korean version

Full Korean translation maintained in parallel — see ko/README.md and ko/docs/.

---

TL;DR — What the trail proves

Stated as falsifiable claims, each backed by evidence in the docs:

1. LayerZero V2 EVM↔EVM works reliably. BSC → Polygon delivered in 58 seconds for $0.42 total cost (one successful transfer documented with txhash).

2. LayerZero V2 BSC↔Tron does not work reliably for new OApps. Two transfers stuck in INFLIGHT state for 5+ hours with LayerZero Labs DVN in WAITING status (two transactions documented).

3. Polygon→Tron quoted 760× the fee of BSC→Polygon for the same OApp after explicit DVN configuration, indicating effective refusal of the pathway by the default DVN setup.

4. Ethena USDe ($5B asset) operates successfully on TON via LayerZero OFT — confirmed via LayerZero's own metadata API, proving TON support is real for sufficiently large projects.

5. No production-ready protocol supports custom token integration to Tron + Solana + TON simultaneously. Documented per-protocol gaps.

6. A self-operated cross-chain protocol is technically feasible for any team with smart-contract and backend experience, with one Relayer covering >1000 messages/day comfortably.

---

Why this matters

Cross-chain documentation is dominated by protocol marketing. This repository is the opposite: an engineering log of what actually happens when you try to ship.

The same patterns will apply to other teams targeting Tron, TON, or Solana inclusion. We hope this saves you the 28 hours we spent finding out.

---

License

This repository is licensed under CC BY 4.0. You are free to share and adapt with attribution.

Smart-contract source code in sourcecode/ is licensed under MIT (see individual files).

---

Contact

• GitHub Issues: questions, reproductions, or corrections welcome
• Domain: molepin.com (main), scan.molepin.com (block explorer, planned)