Skip to main content

Scaffold-EVVM

Battle-test EVVM services locally before you spend a wei of testnet or mainnet gas.

Scaffold-EVVM is the iteration loop for anyone shipping an EVVM service. Drop your .sol file, run one command, and you get:

  • A local EVVM stack — all six protocol contracts (Core, Staking, Estimator, NameService, Treasury, P2PSwap) deployed on Anvil or Hardhat Network.
  • Your service auto-deployed and wired in — addresses written to the frontend .env, ABI persisted, no manual plumbing.
  • A fully generated UI at /services/<your-service> — read panel, write panel with the right form per function role (admin / publicAction / publicPay), live event tail, EVVM dual-signature signing handled for you.
  • A block explorer at /evvmscan that decodes your service's calls and events as first-class citizens alongside the protocol contracts.
  • 23+ signature constructors for every EVVM operation so you can stress-test how your service interacts with payments, staking, names, and P2P swaps.

Under the hood, scaffold-evvm wires its frontend to the protocol through the evvm-js SDK — the same typed client (@evvm/evvm-js) you'd use to integrate EVVM into any other application. The auto-UI, signature constructors, and EVVMScan all build on it, so what you exercise locally is what you ship.

🛡️ Why this matters: every signature you generate against a service ABI you wrote yesterday is one fewer testnet deploy, one fewer testnet faucet round-trip, one fewer "wait, did I send the right struct?" thirty minutes after pushing. Failing fast locally is the whole point.

When to use Scaffold-EVVM​

You're a good fit if you want to:

  • Iterate on a new EVVM service — write the contract, drop it in services/, hit the auto-UI, see what breaks. Edit, rerun the wizard, repeat.
  • Demo a contract to a non-technical audience — the auto-UI is legible enough that they can drive it.
  • Test a contract end-to-end through a real UI before investing in a bespoke frontend.
  • Learn EVVM hands-on — send pays, register names, stake MATE, swap tokens, all from a UI built specifically to teach the protocol.
  • Contribute to EVVM core — run the full stack locally, modify any contract, redeploy in seconds.

What this section covers​

For EVVM protocol-level concepts (signatures, contracts, nonces) see the rest of evvm.info/docs. The canonical service-authoring guide lives at How to make an EVVM service — this section is the scaffold-evvm shorthand for that workflow.