Mantle Network Primer

Overview

This is a reference/onboarding skill for Mantle-specific concepts that are easy to misunderstand during development or user support. Explain stable Mantle concepts first, then use the reference for dated snapshots like chain settings, tooling links, and architecture notes. Avoid canned answers and label anything time-sensitive as a live-verify item.

Role

• Treat this skill as domain-specific onboarding and misconception prevention, not as an execution operator.
• Use it to clarify Mantle-specific concepts, developer assumptions, and live-verify boundaries.
• Hand off address lookup, transaction risk, portfolio inspection, and execution planning to the specialized Mantle skills.

Workflow

1. Classify the request as basics, differences, operations, or live_verify.
2. Load the matching section from references/mantle-network-basics.md:
   • basics -> core model and stable terminology (always include that gas is paid in MNT as a key fact, and mention L2 inclusion vs L1 settlement distinction)
   • differences -> Mantle-specific differences and developer hints
   • operations -> network details, onboarding tools, RPC reliability, and source-of-truth links
   • live_verify -> use the reference only to frame what must be checked live
3. Respond in two layers when useful:
   • stable concept summary
   • dated snapshot details labeled with the reference date when operational specifics matter
4. For time-sensitive questions (fees, block time, throughput, current ecosystem status, or latest architecture rollout details), state that values can change and request live verification from official docs or tools. Even for live-verify questions, always ground the response with the relevant stable concept (e.g., for a fee question, explain that gas is paid in MNT and what that means before flagging the live-verify need).
5. When asked what makes Mantle different, focus on stable developer-relevant differences:
   • gas is paid in MNT
   • L2 inclusion is not the same as L1-backed settlement/finality
   • public RPC endpoints are rate-limited
   • Mantle-specific chain settings and onboarding links matter

Response Format

When quoting any operational detail from the reference (RPC URLs, chain IDs, contract addresses, compiler versions, explorer links, architecture descriptions), always append the snapshot date inline. Example:

The mainnet RPC endpoint is https://rpc.mantle.xyz and the chain ID is 5000 (per reference snapshot of March 8, 2026).

When the response covers both stable concepts and dated details, use two clearly separated sections:

1. Stable concept — the part that does not change (e.g., "Gas on Mantle is paid in MNT, not ETH").
2. Snapshot details (March 8, 2026) — operational values that may change; label the section header with the date.

Response Rules

• Define key terms once: sequencer, settlement, finality, gas token.
• Distinguish transaction inclusion from final settlement.
• Use absolute dates for time-bound statements.
• Always label snapshot values with the reference date (March 8, 2026) when quoting them — never present operational details without the date.
• Do not answer "latest/current" questions from this file alone.
• Avoid financial advice and price predictions. Do not speculate on token price, ROI, or investment suitability.
• If confidence is low, say so directly and request a source check.

References

• references/mantle-network-basics.md