Testnet only (Arkiv Tiramisu). OpenTrigger 0.1 has not had an outside audit.
OpenTrigger

CLI

The arkiv-triggers command and every environment variable it reads.

Commands

CommandWhat it does
npx arkiv-triggersRun a worker configured from the environment, then ./.env
npx arkiv-triggers new-keyPrint a fresh wallet to use as WORKER_KEY, and its address
npx arkiv-triggers --helpShow the settings

Once installed, the same command is also arkiv-triggers-worker.

Environment

VariableRequiredSecretMeaning
WORKER_KEYYesYesThe worker's wallet key (0x + 64 hex). Must hold test GLM
ARKIV_ACCESS_KEYRecommendedYesArkiv access key. Without it the worker warns and uses the anonymous budget
WORKER_MODENoNoany (default) or own
TG_TOKENNoYesTelegram bot token: enables the Telegram action and the /start reply
OPERATORNoNoYour main wallet, to link the worker
OPERATOR_SIGWith OPERATORNoYour signature linking it
ARKIV_RPC_URLNoNoOverride the Tiramisu HTTPS endpoint
ARKIV_WS_URLNoNoOverride the Tiramisu WebSocket endpoint
PORTNoNoServe GET /healthz on this port

Values already in the environment win over .env.

Startup checks

The worker exits with a clear message when WORKER_KEY is missing or malformed, WORKER_MODE is not any or own, OPERATOR is not an address, only one of OPERATOR and OPERATOR_SIG is set, or the wallet has no GLM.

/healthz

200 while the worker's last processed block keeps moving; 503 once it has been stuck for 2 minutes. The body is JSON: ok, worker, version, rules, fired, failed, skipped, lastBlock, heartbeat.

Signals

SIGINT or SIGTERM finishes actions in flight and exits 0; a second signal exits at once.

On this page