Docs

Forge documentation

Everything you need to build, publish, and understand Animica Forge. Short and practical.

How to build an app

Go to Build, describe your idea (5–1,000 characters), optionally pick a category or switch to the smart-contract lane, then hit build. Forge routes your prompt to the best generator and returns a working app you can preview instantly in a secure sandbox.

With no model configured, Forge uses fast built-in templates. Configure an OpenAI-compatible endpoint (Animica pool, Studio, or a local model) to generate freeform apps from any prompt.

How to publish

From the preview, edit the title, description, and category, then publish. You get a public page at /app/your-app with a live preview, source viewer, votes, views, and remix count. Publishing is free, anonymously or with a connected wallet.

How remixing works

Any app can be remixed. Click Remix to open the builder with the original loaded; describe your changes and generate a new version. The remix links back to its source, and the original’s remix count goes up when you publish.

Smart contracts

Switch the builder to the smart-contract lane to author an Animica contract — in the vm_py Python VM or Solidity for the EVM lane (chain 149). Forge statically checks your source and derives a simple ABI; it never executes contract code on the server.

On a contract’s page you can prepare a deployment to Animica testnet. Deployment is prepared and simulated in the MVP; live wallet-signed deployment connects in the next phase.

Wallet & free tier

Building, publishing, remixing, and voting are free forever. Connect the Animica browser extension to link your anim1… address as your creator identity — connecting is real; ANM payments are prepared but not yet live.

How Arena works

Animica Arena runs daily build challenges. Publish an app, submit its link to the active challenge, and gather votes. The leaderboard ranks by votes. Prize amounts are shown as placeholders — prize payout is not yet live.

Security & sandboxing

Generated apps never run in the main page. Each runs inside a sandboxed iframe with sandbox="allow-scripts" and no allow-same-origin, so it gets an isolated origin with no access to your data, cookies, or storage. The iframe also carries a strict CSP that blocks network requests and external scripts. Code size is capped (HTML/CSS 50 KB, JS 100 KB), metadata is escaped, voter IPs are hashed, and requests are rate-limited.

What’s mocked in MVP

  • App generation uses templates unless an LLM endpoint is configured.
  • ANM payments (tips, boosts) are mocked.
  • Compute settlement is not live yet.
  • Contract deployment is simulated and prepared for Animica testnet.
  • Generated apps are sandboxed and cannot use external scripts in the MVP.
  • Auth is minimal and can be upgraded (email / GitHub / wallet).

Future ANM integration

The ANM interfaces are wired end-to-end behind a mock service: tip intents, compute estimates, network status, and deployment intents all flow through the same methods a live implementation will use. When settlement is connected, tips, boosts, compute runs, contract deployment, and creator/provider rewards go live with no change to how you use Forge.

For protocol resources — wallet downloads, mainnet docs, snapshots, mining, node/operator guides, RPC and explorer — see animica.org.