sails-local-smoke
Sails Local Smoke
Goal
Validate the generated client path against a local node after gtest is already green.
Deploy Artifact And Tooling
- The deploy artifact is the
.opt.wasmfile (optimized WASM), not the plain.wasm. The.opt.wasmis produced bywasm-optduring the Sails build and is significantly smaller. Uploading the unoptimized.wasmto a node will often fail withCodeTooLarge. - Prefer
vara-walletfor deploying to a local node. It handles account management and program upload without requiring a Gear source checkout or Rust-specific tooling. - For Rust-native test harnesses that already use
gclient, theGearApi+GclientEnvpath remains valid as a secondary option.
Identity Rules
- Use local dev accounts or user-provided account addresses in
SS58form for standard Vara account flows; do not default to Ethereum0xaddresses for normal local-node work. - Record the real deployed
program idfrom the deploy step and pass that into the typed client. If the flow uses vouchers, issue one first and use the returned voucher ID. Do not invent either identifier. - Keep seed phrases and private keys out of committed scripts, docs, and examples. Use local keyrings, environment input, or interactive setup instead.
Inputs
More from gear-foundation/vara-skills
vara-skills
Use when a builder needs the top-level router for the provisional standard Gear/Vara Sails skill pack across Codex, Claude, or OpenClaw. Do not use for Vara.eth or ethexe work, non-Sails programs, or broad protocol research.
202sails-new-app
Use when a builder is starting a new standard Gear/Vara Sails app and needs the correct greenfield sequence before implementation. Do not use for edits to an established repo, Vara.eth or ethexe targets, or non-Sails templates.
2sails-dev-env
Use when a builder needs to prepare or repair a local macOS, Linux, or Windows machine for standard Gear/Vara Sails Rust development before building, testing, or running a local node. Do not use for live-network deployment, app-specific feature work, or Vara.eth/ethexe-only setup.
2vara-wallet
Use when an agent needs to interact with Vara Network on-chain — deploy programs, call Sails methods, manage wallets, transfer tokens, monitor events. Not for building Sails programs (use vara-skills for that).
2sails-gtest
Use when a builder needs the standard Gear/Vara Sails gtest loop for feature verification, debugging, or regression coverage. Do not use for live-network-only validation, deployment-first workflows, or non-Sails programs.
2task-decomposer
Use when approved spec and architecture artifacts must become an ordered implementation plan for Gear or Vara work. Do not use when the architecture is still unsettled or when the request is only asking for a high-level idea.
2