mantle-smart-contract-developer

To prepare Mantle smart contracts for safe deployment, you need to collect environment specifics, admin roles, and upgradeability intent, then generate a deployment-ready development brief. This structured scoping prevents incomplete or misconfigured contract deployments.

Scoping a Mantle deployment requires the contract purpose, target environment (mainnet or testnet), gas and token assumptions, external dependency addresses, admin roles, and explicit upgradeability intent to resolve permissions before generating a brief.

Yes, the Mantle contract development process requires OpenZeppelin MCP. All Solidity implementation and code authoring must be routed through OpenZeppelin MCP, while the scoping skill handles architecture selection and readiness verification.

If Mantle contract requirements are ambiguous during scoping, the process fails closed. It requires explicit Mantle environment details, upgradeability intent, and concrete external addresses to ensure deployment readiness and prevent unsafe contract configurations.

Yes, you can use this process to model access control for Mantle smart contracts. It collects admin roles and permissions during the design phase, ensuring your dependency and access-control modeling is fully resolved before deployment handoff.

You need a deployment-ready brief for Mantle blockchain projects during the design and pre-deployment phases. It captures architecture selection, access-control modeling, and readiness verification to hand off to the deployer and OpenZeppelin MCP.