nothing-ever-happens Polymarket Bot

The bot defaults to using PaperExchangeClient for safety. To enable real order transmission, you must satisfy two conditions:

1. Required Runtime Flags

You must set all three of the following environment variables:

• BOT_MODE=live
• LIVE_TRADING_ENABLED=true
• DRY_RUN=false

2. Required Secrets and Infrastructure

Once live mode is enabled, the following variables are also required:

• PRIVATE_KEY: For signing transactions.
• FUNDER_ADDRESS: Required for signature types 1 and 2.
• DATABASE_URL: For state persistence.
• POLYGON_RPC_URL: Required for proxy-wallet approvals and redemptions.

Run the unit and regression test suite using pytest.

python -m pytest -q

Execute the bot using the nothing_happens runtime via the following command. The dashboard will automatically bind to the $PORT or $DASHBOARD_PORT environment variable if provided.

python -m bot.main

To deploy the bot to Heroku, follow these steps to configure the environment and push the code.

1. Set Runtime and Secret Configs

Use the Heroku CLI to set the necessary environment variables for live trading:

# Set trading flags
heroku config:set BOT_MODE=live DRY_RUN=false LIVE_TRADING_ENABLED=true -a "$HEROKU_APP_NAME"

# Set secrets
heroku config:set PRIVATE_KEY=<key> FUNDER_ADDRESS=<addr> POLYGON_RPC_URL=<url> DATABASE_URL=<url> -a "$HEROKU_APP_NAME"

2. Deploy and Scale

Push your branch to Heroku and scale only the web dyno. The worker dyno should remain at 0 to prevent accidental execution.

git push heroku <branch>:main
heroku ps:scale web=1 worker=0 -a "$HEROKU_APP_NAME"

To set up the bot locally, install the required Python dependencies and initialize the configuration files from the provided examples.

pip install -r requirements.txt
cp config.example.json config.json
cp .env.example .env

When running in live mode (exchange_cfg.live_send_enabled is true), the runtime enforces several strict requirements:

1. Database Requirement: A DATABASE_URL must be provided. The bot uses this to initialize the trade ledger via init_db.
2. Durable Recovery: If live_send_enabled is true, the LiveRecoveryCoordinator must be enabled. If it is not enabled, the runtime will raise a RuntimeError.
3. Wallet Derivation: The wallet address is derived based on the signature_type:
   • If signature_type is 1 or 2, it uses exchange_cfg.funder_address.
   • If signature_type is 0, it derives the address from exchange_cfg.private_key using eth_account.
4. Redeemer Requirements: For the Redeemer to run, you must provide a POLYGON_RPC_URL and ensure the configuration includes a private_key, funder_address, and signature_type == 2.

The bot uses two separate files for configuration:

1. config.json: Used for non-secret runtime settings. These settings are located under the strategies.nothing_happens key. You can override the default config location by setting the CONFIG_PATH environment variable.
2. .env: Used for secrets and runtime flags.

config.json is intended to be kept local and should not be committed to version control.

# Example: Pointing to a custom config file
export CONFIG_PATH=/path/to/config.json

The bot is executed by calling the main() function in bot/main.py. This initializes the environment, loads configurations, sets up logging, patches HTTP timeouts, and starts the asynchronous supervisor loop. The supervisor manages several concurrent tasks including the strategy engine, recovery workers, redeemers, and an optional dashboard.

To run the bot, ensure your environment variables (like DATABASE_URL, PRIVATE_KEY, etc.) are configured, then execute the script.

python -m bot.main

The repository includes several scripts for managing deployed instances and inspecting data:

For Heroku-specific helpers (like ./alive.sh, ./logs.sh, ./kill.sh), ensure HEROKU_APP_NAME is exported in your shell.

The following environment variables are used by the bot/main.py entrypoint to configure the runtime behavior: