Operator Binary

The Operator Binary serves as the execution engine linking Operators with YODL’s Settlement Relayer and on-chain contracts. It is responsible for quoting, accounting, and settlement operations, ensuring that all executions occur within verified parameters and remain fully traceable.
All communication between the Operator Binary and the Settlement Relayer is authenticated and policy-bound, enabling secure, deterministic execution across orderflow venues.
Setup Overview
Install the Operator Binary (provided after whitelisting).
Configure environment variables — RPC endpoints, private key path, API key, and monitored token pairs.
Connect to the Settlement Relayer API for real-time RFQ flow and settlement coordination. Configure the Operator Binary in the same region as the Settlement Relayer for low-latency performance.
Maintain continuous uptime and monitor logs, latency, and the Health Factor of active vaults.
Operator Binary Configuration Knobs
Configuration Knob
Purpose
Notes / Requirements
RPC & Node
Reads on-chain data from the Orchestrator to track vault balances and available vault liquidity (Curator capital).
Use reliable RPC endpoints (HTTPS/WebSocket). Latency impacts quoting performance.
Strategy Plugin Endpoint
Connects to the active strategy plug-in to fetch pair, price, and minimum trade size data.
May point to the default CoW Construction Strategy or any approved custom strategy endpoint.
Oracle Link (Mandatory for CoW Strategy)
Provides access to governance-whitelisted price oracles for quoting within the default strategy.
Required for operators opting into the default CoW strategy.
Environment Variable: Private Key
Authenticates Operator actions and signs outbound requests to the Settlement Relayer.
Must be stored securely. Never share or hardcode this key.
Last updated