Polymarket Bot Range-Strategy Update
Budget: $250 – $750 USD
I already run a Python-based bot that places trades on Polymarket, but its current logic is too directional. I now want the core algorithm re-worked so it trades a defined price range instead of purely trend-following or mean-reversion signals.
What I will hand over
• The full repository (Python 3.x) with environment file, helper modules and the existing strategy class.
• Sample API keys and the mock-exchange mode I use for quick back-tests.
What I need back
• A refactored strategy module that identifies ranges, sets dynamic upper / lower bands and executes orders when price oscillates between them.
• Parameter hooks (e.g. band width %, minimum liquidity, time-in-range) exposed in a config file so I can tune the behaviour without touching code.
• Unit tests or a lightweight notebook proving the new logic against at least one historical market.
• Clear inline comments plus a short README outlining any new dependencies or setup steps.
Acceptance
The bot must compile, connect to Polymarket exactly as before and produce trade logs that show entries and exits only within the detected range boundaries for the test dataset I provide. I’ll consider the job done once those logs pass my manual review and the updated tests all return green.
If you’re fluent in Python, comfortable with exchange APIs/Web3 calls and enjoy quantitative tinkering, this should be a straightforward but fun tweak.
What I will hand over
• The full repository (Python 3.x) with environment file, helper modules and the existing strategy class.
• Sample API keys and the mock-exchange mode I use for quick back-tests.
What I need back
• A refactored strategy module that identifies ranges, sets dynamic upper / lower bands and executes orders when price oscillates between them.
• Parameter hooks (e.g. band width %, minimum liquidity, time-in-range) exposed in a config file so I can tune the behaviour without touching code.
• Unit tests or a lightweight notebook proving the new logic against at least one historical market.
• Clear inline comments plus a short README outlining any new dependencies or setup steps.
Acceptance
The bot must compile, connect to Polymarket exactly as before and produce trade logs that show entries and exits only within the detected range boundaries for the test dataset I provide. I’ll consider the job done once those logs pass my manual review and the updated tests all return green.
If you’re fluent in Python, comfortable with exchange APIs/Web3 calls and enjoy quantitative tinkering, this should be a straightforward but fun tweak.
Related categories:
C Programming
Python
Software Architecture
C++ Programming
Financial Analysis
API
Data Analysis
Backtesting