WAVS builders handbook
Task commands
The Taskfile.yml in the template composes commands from two sources:
- Project-specific taskfiles in
./taskfile/— build, deploy, and service tasks customized for the template - Shared base taskfiles from Lay3rLabs/wavs-taskfiles — common operator, docker, WASI, and core tasks reused across WAVS projects
Commands
Use task help (or task --list-all) to see all the commands:
task help
Here are the available task commands and their descriptions:
help show available taskssetup install initial dependenciesstart-all-local start all local services (anvil, IPFS, WARG, Jaeger, prometheus)deploy-full run complete WAVS deployment pipelinebuild:all build everything (Solidity + WASI components)build:forge build Solidity contractsbuild:wasi build WASI components (all or specific one) | WASI_BUILD_DIRwasi:exec execute the WAVS wasi component(s) | COMPONENT_FILENAME, INPUT_DATAdeploy:service deploy WAVS service from URL | SERVICE_URL, WAVS_ENDPOINTdeploy:ipfs upload service config to IPFS | SERVICE_FILEdeploy:component upload WASI component to WAVS endpoint | COMPONENT_FILENAME, WAVS_ENDPOINToperator:register register an operator with WAVS Service Manageroperator:update-signing-key update operator's signing key with WAVS Service Manageroperator:verify verify operator registration statusget-trigger-from-deploy get the trigger address from the script deployget-submit-from-deploy get the submit address from the script deployshow-result show the result | SERVICE_SUBMISSION_ADDR, TRIGGER_ID, RPC_URLtest run testslint:check check linting and formattinglint:fix fix linting and formatting issues
For more information on commands when using the template, visit the WAVS tutorial.
