[PROPOSAL] Hummingbot V2.1 Gateway Integration for GMX V2 (Async Python)
Summary
I’m proposing to build a native GMX V2 connector for the Hummingbot V2.1 Gateway. The goal is simple: provide a solid, asynchronous Python integration so the community can run market making and arb strategies on GMX V2 without having to write their own custom wrappers.
Technical Approach
- Async-First: Everything is built on asyncio and httpx. No blocking calls. I’m focusing on keeping the latency as low as possible for order routing and price polling.
- State Persistence: I’m using a local SQLite engine to manage the state. This is a must-have for handling API timeouts or network issues—the bot needs to know its exact position and order status even if the connection drops.
- V2.1 Standard: The code follows the Hummingbot Gateway V2.1 spec. It’s modular, clean, and follows PEP8/Black standards, making it easy to maintain as GMX updates their contracts or APIs.
Why this matters for GMX
Right now, if you’re a Python dev wanting to trade on GMX V2, you usually end up writing a lot of “glue code” that’s hard to maintain. By adding GMX V2 to the Gateway V2.1 standard, we open the door for more algorithmic volume and professional quant tools to plug directly into GMX liquidity on Arbitrum.
Deliverables
- Full Python connector source code.
- Robust integration with GMX V2 low-latency data feeds.
- Documentation and setup guide for the community.
About Me
I’ve been working extensively with the V2.1 Gateway architecture and building execution tools on Arbitrum. I’m building this because I need a reliable, deterministic way to interact with GMX V2 myself, and I want to contribute that back to the ecosystem.
gmx-v2, integration, development, python, hummingbot, arbitrum, ecosystem-tooling