EveryframeDocs
Open Studio ↗
Mining/Command reference

Command reference

text
everycli miner <command> [options]

Version 0.1.0. Requires Node.js 22.13+ (22.x). Global options apply to every command.

#Commands

CommandWhat it doesFlags
initImport a signed invitation and your private credentials into local state--invitation FILE, --secrets-file FILE
doctorRun the readiness checklist (credentials, permissions, invitation, coordinator access, cloud binding, TEE admission, availability)
statusLocal phase + exact cloud workload status + signed coordinator status
providersWhich provider keys are configured and permitted by your release; no key values printed
earningsServing fees by state: review-held, approved, disputed. Not payouts
deployCreate the one approved Phala confidential VM--max-hourly-usd N (required, 0 < N ≤ 100)
activateAfter accepted admission, encrypt and release your provider key into the enclave
resumeClear your own drain flag after fresh post-restart admission
updateInstall an operator-signed release after draining--release FILE
stopDrain, then request graceful shutdown of the saved VM (never deletes)--drain-only
startRestart the same stopped VM--max-hourly-usd N
reconcileRead-only check of an interrupted operation; never blindly resubmits

There is no delete command. Deleting a VM is a manual, deliberate action in the Phala console after the operator confirms there is no outstanding work.

#Global options

OptionMeaning
--state-dir DIRUse another private profile (mode 700). Also EVERYCLI_DIR. Default ~/.config/everycli.
--jsonMachine-readable output on read commands
--yesSkip the confirmation on mutating commands — only after you have read the cost/mutation warning
--help, -hHelp for the command
--versionPrint the CLI version

Unknown flags fail closed. A flag on the wrong command returns invalid_option; an unknown command returns unknown_command.

#Exit codes

CodeMeaning
0Success
2doctor not ready · status with a coordinator or cloud error · reconcile unresolved
1Any other error

Errors print a code and a message. Provider request/response bodies, keys and stack traces are deliberately omitted.

#Environment rules

The CLI refuses to run if any of these are set: NODE_OPTIONS, NODE_EXTRA_CA_CERTS, NODE_TLS_REJECT_UNAUTHORIZED, DEBUG, PHALA_CLOUD_API_PREFIX. There is no --coordinator, --insecure, policy override or simulation flag; the coordinator origin and verification key are pinned in the package.

#Files

PathContents
~/.config/everycli/Profile directory, mode 700
…/operation.lockExclusive lock while a mutating command runs; inspect its PID before removing it after a crash
…/journalOwner-only, fsync'd intents and outcomes for deploy, update, activation, start and stop

Credentials are stored with mode 600, unencrypted. Symlinked paths are rejected.

#Coordinator routes the CLI uses

RouteMethodNotes
/v1/miner/status?nonce=…GETBearer-scoped, coordinator-signed, bound to nonce/time/miner
/v1/miner/drainPOST{ "nonce": "48_HEX" }, 1 KB body limit
/v1/miner/resumePOSTSame shape; requires enabled miner, fresh attestation, matching compose

The worker image itself speaks /v1/challenge, /v1/attest and /v1/action; see How it works.