dojo-deploy

Automate Dojo world deployment to Katana, Sepolia, and Starknet mainnet.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/steebchen/proof-of-war --skill dojo-deploy-steebchen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dojo-deploy
Source: https://github.com/steebchen/proof-of-war/tree/main/.agents/skills/dojo-deploy
Command: npx skills add https://github.com/steebchen/proof-of-war --skill dojo-deploy-steebchen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires katana, sozo, torii, jq, and includes scripts (resource) components.

What problem does it solve?

Automates the setup and deployment of Dojo worlds to a local Katana instance, Sepolia testnet, or Starknet mainnet, simplifying development workflows.

Core Features & Use Cases

  • Start Katana and configure a development environment for Dojo worlds.
  • Build, migrate, and verify deployments using sozo.
  • Manage world addresses and deployment profiles for local and remote networks.

Quick Start

Start Katana and deploy your world to a local development environment.

Frequently Asked Questions about dojo-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a Dojo world to a local Katana instance?

To deploy a Dojo world locally, start Katana to configure your development environment, then use sozo to build, migrate, and verify your contracts. The process automates local setup and address registration for testing.

Can I deploy Dojo worlds to Starknet Sepolia or mainnet?

Yes, you can deploy Dojo worlds to Sepolia testnet or Starknet mainnet. The deployment workflow manages environment profiling, contract compilation, migration, and world address registration across local and remote networks.

What tools are needed to migrate and verify Dojo contracts?

Migrating and verifying Dojo contracts requires katana for the local node, sozo for building and migration, torii for integration, and jq for parsing environment and deployment profile data during the workflow.

How does Torii integration work during Dojo world deployment?

Torii integration ensures verifiable deployments by registering world addresses and indexing contract events after migration. It connects the deployed Dojo world to the indexer, enabling queryable on-chain state across network profiles.

What's the best way to manage deployment profiles for Dojo worlds?

Manage deployment profiles by configuring environment variables for local Katana, Sepolia, and Starknet mainnet separately. The workflow applies sozo migration with profile-specific settings to track world addresses and ensure verifiable deployments.

Why does my Dojo migration fail when switching between local and testnet?

Dojo migration failures across networks often stem from mismatched environment profiles or unregistered world addresses. Ensure katana is running for local tests, and verify sozo and torii configurations match the target network before migrating.