Polymarket BTC 15m Assistant

Follow these steps to set up the real-time console trading assistant for Polymarket 'Bitcoin Up or Down' 15-minute markets.

Prerequisites

• Node.js 18+
• npm

Installation Steps

1. Clone the repository:

   git clone https://github.com/FrondEnt/PolymarketBTC15mAssistant.git
   cd PolymarketBTC15mAssistant

2. Install dependencies:

   npm install

3. Run the assistant:

   npm start

To stop the assistant, press Ctrl + C in the terminal.

The assistant supports HTTP(S) and SOCKS5 proxies for both HTTP requests and WebSocket connections using standard environment variables.

Supported Variables

• HTTPS_PROXY / https_proxy
• HTTP_PROXY / http_proxy
• ALL_PROXY / all_proxy

Using Proxies with Authentication

If your proxy requires a username and password, use the following format:

• HTTP/HTTPS: http://USERNAME:PASSWORD@HOST:PORT
• SOCKS5: socks5://USERNAME:PASSWORD@HOST:PORT

Note: If your password contains special characters (like @ or :), you must URL-encode them. For example, p@ss:word becomes p%40ss%3Aword.

# PowerShell example with authentication
$env:HTTPS_PROXY = "http://user:p%40ss%3Aword@1.2.3.4:8080"
npm start

If the Polymarket WebSocket is unavailable, the assistant falls back to on-chain Chainlink prices on Polygon. It is highly recommended to provide working Polygon RPC URLs for stability.

The assistant uses environment variables to manage Polymarket market selection and connection settings.

If the console shows no Chainlink updates, it usually means the Polymarket WebSocket is unavailable and the fallback mechanism is being used.

Solution: Ensure you have at least one working Polygon RPC URL configured via POLYGON_RPC_URL or POLYGON_RPC_URLS to allow the assistant to fetch on-chain prices.

The startChainlinkPriceStream function determines which WebSocket endpoints to use by inspecting the CONFIG.chainlink object. You can provide a single URL or a list of fallback URLs.

Configuration Keys:

• CONFIG.chainlink.polygonWssUrl: A single WebSocket URL string.
• CONFIG.chainlink.polygonWssUrls: An array of WebSocket URL strings used for fallback/rotation.

If no valid URLs are found in the configuration, the stream will return a dummy object where getLast() always returns { price: null, updatedAt: null, source: "chainlink_ws" } and close() is a no-op.

The project supports configuring a global proxy for HTTP/HTTPS requests using standard environment variables. The system checks for proxy URLs in the following order of precedence based on the target URL protocol:

For HTTPS/WSS targets:

1. HTTPS_PROXY or https_proxy
2. ALL_PROXY or all_proxy

For HTTP/WS targets:

1. HTTP_PROXY or http_proxy
2. ALL_PROXY or all_proxy

If no specific protocol proxy is found, it falls back to ALL_PROXY.

The assistant can either target a specific market or automatically find the latest one in a series. This is controlled via the CONFIG object (imported from ./config.js).

• Pin a specific market: Set CONFIG.polymarket.marketSlug to the specific slug of the market you want to track.
• Auto-select latest: If marketSlug is not set, ensure CONFIG.polymarket.autoSelectLatest is true. The assistant will then use CONFIG.polymarket.seriesId to fetch the most recent live market in that series.

The countConsecutive function analyzes an array of Heiken Ashi candles to determine the length of the current trend (the most recent streak of same-colored candles).

It returns an object with:

• color: Either `

Use pickLatestLiveMarket(markets, nowMs) to find the most relevant market from a list.

Logic:

1. It first looks for live markets (where startTime <= nowMs < endDate). If multiple exist, it returns the one with the earliest endDate.
2. If no live markets are found, it returns the upcoming market with the earliest endDate.
3. Returns null if no valid markets are found.

const currentMarket = pickLatestLiveMarket(markets); // uses Date.now() by default