yieldomega-timecurve-bot

To set up the TimeCurve Python bot, configure your TimeCurve contract address and RPC URL via environment variables. You can then run CLI commands like inspect to verify connectivity and execute strategies against a local Anvil network or public RPC.

The TimeCurve bot ensures transaction safety through built-in dry-run options and secure private key handling. It performs safe transaction submission and includes optional one-shot funding gates to bootstrap development wallets when needed.

Yes, the TimeCurve bot supports public RPC endpoints to read chain state and optionally submit transactions. It applies to workflows using either a local Anvil dev network or public RPC connections for testing and operation.

The TimeCurve bot provides CLI commands for inspecting chain state, running bot strategies, and executing a deterministic local seed scenario. Use the inspect command to quickly verify your RPC connection and current configuration.

Anvil is not strictly required, as the TimeCurve bot can operate against public RPCs. However, using Anvil-based dev workflows enables deterministic local seed scenarios and optional Anvil funding to safely bootstrap your development wallets.

TimeCurve bot configuration loading failures often stem from missing or incorrect environment variables. Ensure your .env or .env.local file properly defines the TimeCurve contract address and RPC URL for on-config loading to succeed.