Skip to main content
Use this page after Set Up Your Appchain. Pick a direction, prompt your AI agent, deploy, and verify real onchain behavior. Before you start, confirm:
  • Tools ready: weave, initiad, and minitiad are installed and in your PATH (Step 6).
  • Infrastructure live: your rollup and OPinit/Relayer bots are running (Step 8).
  • Gas Station keys imported: your mnemonic is available in local keyrings (Step 9).
  1. Complete Set Up Your Appchain.
  2. Choose between building your app from scratch or using a Blueprint for reference.
  3. Implement your app with your AI agent.
  4. Deploy and verify real onchain interactions.
  5. Complete Submission Requirements.

​
Part 1: Core Workflow

​
Funding Your Personal Wallet

Before you can interact with your appchain via a browser wallet (like Keplr, Leap, or MetaMask), you need to fund your personal address from your Gas Station.
  1. Copy your wallet address (init1...).
  2. Ask your AI agent to fund your wallet:
Prompt: Fund your personal wallet
Using the `initia-appchain-dev` skill, please fund my personal wallet <YOUR_WALLET_ADDRESS> with 1 INIT on L1 and 100 of my appchain's native tokens on L2.

​
Describe -> Build -> Test

  1. Describe the Goal: Tell the AI what you want to achieve and why.
  2. Build & Test: Let the AI write the code and unit tests.
    Prompt: Create and test the contract
    Using the `initia-appchain-dev` skill, please create a new <MOVE / EVM / WASM> contract project in a directory named <PROJECT_NAME>, implement the core logic for <APP_NAME>, and create/run unit tests that verify both success and failure paths.
  3. Deploy: Instruct the AI to deploy your contract/module to your appchain.
    Prompt: Deploy to your appchain
    Using the `initia-appchain-dev` skill, please build and deploy my contract/module from the <PROJECT_NAME> directory to my appchain using my Gas Station account. If this VM requires instantiate after deploy, run that too, then return the deployed address.
  4. On-Chain Verification: Ask the AI to verify your live deployment with interactions and state queries.
    Prompt: Smoke test live deployment
    Using the `initia-appchain-dev` skill, I want to smoke test my live <CONTRACT_NAME> on my appchain. Please execute 2-3 realistic user actions, then query state after each step and confirm the observed results match expected behavior.
Save these early: As you build, save your deployed contract address and a real L2 interaction transaction hash. You will need this information when completing .initia/submission.json.

​
Part 2: Choose Your Blueprint

To qualify for the hackathon prizes, your project must implement at least one supported Native Feature. These Blueprints provide implementation patterns you can adapt, or use as references while building your own concept.
Originality matters: Whether you build from scratch or adapt an example, judges will look for clear custom logic, UX, and product differentiation.

Blueprint 1: BlockForge Game (Auto-signing)

A high-frequency application where the blockchain handles logic silently in the background. Users approve a session once, then continue interacting without repeated wallet popups.

Blueprint 2: MiniBank (Interwoven Bridge)

An application that allows users to move assets between the broader Initia L1 and your appchain without leaving your interface.

Blueprint 3: MemoBoard (Initia Usernames)

An application that prioritizes human-readable identities, replacing complex hex addresses with personal usernames.

​
Part 3: Prepare Your Submission

Use this checklist to mirror the official Submission Requirements.
  • Rollup Chain ID: Include your appchain Chain ID.
  • Submission JSON: Create .initia/submission.json and complete all required fields exactly as defined in Submission Requirements.
  • Supporting Evidence: Ensure your JSON includes valid paths to your core logic file and native feature frontend file, plus a real L2 interaction transaction.
  • Demo Video URL: Include a 1-3 minute walkthrough video (Loom/YouTube, publicly accessible via URL).
  • README Summary: Add a short project overview and implementation details section for judges.

​
Part 4: Debugging & Troubleshooting

​
Debugging Workflow

Whether you are building from scratch or adapting an example, errors are inevitable.
  1. Open the Browser Console: Press F12 or Cmd+Option+J to see the exact error logs.
  2. Provide Project Context: Ensure your AI agent is open in your project root. This allows it to reference your package.json, your interwovenkit initialization, and your specific chain configuration.
  3. Ask your AI agent to fix the issue directly, then paste the exact console error below the question.
    Prompt: Fix the error in my codebase
    Please find and fix this error directly in my codebase, then tell me what changed.
[PASTE_CONSOLE_ERROR]

​
Official References

  • Official Docs: Visit docs.initia.xyz for architectural details and API references.
  • Initia Examples: Reference the initia-labs/examples repository for working code across all VMs (EVM, Move, Wasm).
  • Core Repositories: Explore initia-labs on GitHub to see the underlying implementation of the SDKs and CLI tools.
Mandatory: Review the Submission Requirements to ensure you are eligible for prizes.