Worker Setup

Overview

AutoLoop workers are off-chain Node.js processes that monitor registered contracts and call progressLoop() when ready. They auto-detect contract types (Standard, Hybrid VRF, Full VRF) via ERC-165 and handle VRF proof generation automatically.

Quick Start

git clone https://github.com/LuckyMachines/autoloop-worker.git
cd autoloop-worker
npm install

Create .env from .env-example:

RPC_URL=https://mainnet.infura.io/v3/YOUR_KEY
PRIVATE_KEY=0x_YOUR_WORKER_KEY
NETWORK=mainnet
PORT=3000

Register and start:

npm run register-controller   # costs 0.001 ETH
npm start

Environment Variables

Per-network keys are also supported:

PRIVATE_KEY_MAINNET=0x...
RPC_URL_MAINNET=https://mainnet.infura.io/v3/YOUR_KEY
PRIVATE_KEY_SEPOLIA=0x...
RPC_URL_SEPOLIA=https://sepolia.infura.io/v3/YOUR_KEY

Config File

controller.config.json is optional when NETWORK env var is set:

{
  "network": "mainnet",
  "allowList": [],
  "blockList": []
}

• allowList — explicit contracts to monitor (empty = monitor all registered)
• blockList — contracts to skip

VRF Support

Workers auto-detect contract types and handle each mode:

Before a VRF/Hybrid contract accepts proofs, register the controller's public key on-chain:

vrfContract.registerControllerKey(controllerAddress, pkX, pkY);

Health Endpoint

Workers run an HTTP health server on PORT:

GET /health

{
  "status": "running",
  "uptime": 1234,
  "network": "mainnet",
  "blockNumber": 10374545,
  "loopsMonitored": 3,
  "lastCheck": "2026-03-12T09:07:14.004Z"
}

Cloud Deployment (Railway)

The worker ships with a Dockerfile and railway.toml:

docker build -t autoloop-worker .
docker run --env-file .env autoloop-worker

The entrypoint is npm run cloud-start — registers the controller and starts the worker. The Dockerfile includes a HEALTHCHECK that pings /health.

Scripts