# Toronet Smart Contract Deployment

> Deploy Solidity smart contracts to ToroNet using toronetdeploy. Use when the user wants ToroNet deployment commands, help configuring owner and constructor args, guidance on network selection, mainnet token requirements, or Foundry remappings needed before deployment.

- Skill: `toronet-guidl/toronet-smart-contract-deployment` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add toronet-guidl/toronet-smart-contract-deployment`
- Raw SKILL.md: https://api.skillmd.com/api/skills/toronet-guidl/toronet-smart-contract-deployment/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- License: MIT
- Author: toronet-guidl (https://skillmd.com/u/toronet-guidl)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/toronet-guidl/toronet-smart-contract-deployment

---


# toronet-smart-contract-deployment

## When to use

Use this skill when the user wants to:

- deploy a Solidity contract to ToroNet
- get the correct `toronetdeploy` command or library usage
- pass `--owner`, `--args`, or `--network`
- deploy from a Foundry project and configure remappings
- understand when `--token` is required
- troubleshoot ToroNet-specific deployment issues

Do not use this skill for writing the contract itself, frontend integration, or general SDK usage unless directly required to complete a ToroNet deployment task.

## Instructions

1. Treat `toronetdeploy` as the default ToroNet deployment path and support both CLI (`npx toronetdeploy`) and library usage (`deployContract`).
2. For CLI usage, make sure the user provides the Solidity file path, contract name, owner address, constructor arguments if needed, and target network.
3. For library usage, use the same fields as options and show CommonJS or ESM imports when requested.
4. Default the network to `testnet` unless the user explicitly asks for mainnet.
5. If the user is deploying to mainnet, mention that `--token` is required and is obtained from the ToroNet team.
6. If the contract comes from a Foundry project, make sure imports and remappings are properly configured in `foundry.toml` before deployment.
7. Prefer copyable commands or code samples.
8. If the user provides incomplete deployment details, preserve the ToroNet deployment pattern and show a realistic template with placeholders.
9. Keep the answer focused on deployment unless the user explicitly asks for contract design or integration help.

## Default workflow

1. Identify the contract file and contract name.
2. Confirm the owner address.
3. Determine whether constructor arguments are required and the target network.
4. Determine whether the user wants CLI or library usage.
5. Check whether the contract comes from a Foundry project; if so, remind the user to verify remappings in `foundry.toml`.
6. Produce the correct `toronetdeploy` command or `deployContract` usage and add only the ToroNet-specific notes needed for successful deployment.

## Checks

- file path and contract name are correct
- owner address is present
- constructor args are correctly formatted
- network is set correctly
- mainnet deployment includes `--token`
- Foundry imports/remappings are configured before deployment

See [the reference guide](references/REFERENCE.md) for the deployment workflow, command patterns, common checks, and ToroNet-specific deployment notes.

If the user is deploying from a Foundry project, also review:
assets/foundry.toml.example