I'm currently testing Hummingbot's connection with @EVEDEX , and it seems to work quite well, so I'm quickly writing a guide for anyone who wants to try it. Here's the simplest configuration method currently available: Step 1: In EVEDEX, create an API Key. Go to Profile → API Management. Create a new key and grant Read Trade permissions. Copy the API Key and Secret Key. Step 2: Open Hummingbot and type the command: connect evedex_perpetual Then paste the API Key and Secret Key. If it shows "Connection successful," the connection is complete. Step 3: Create a simple Market Making config file (e.g., BTC): bid_spread and ask_spread: 0.3 order_amount: start with 0.001 BTC order_refresh_time: 60 seconds Then run the command: start pure_market_making [filename] Notes when running: Test with very small volume first Keep leverage low (5x–10x) Gas loss is almost negligible, so test freely Market making still carries risks; don't let the bot run large volumes right from the start Currently, I'm still testing and haven't dared to use large volumes yet. Anyone trying it, please comment below and share your experience.

7 links i would save for a Polymarket execution stack: 1. github.com/duneanalytics/spe… — Dune Spellbook use: open crypto data models and SQL patterns edge: learn how real onchain dashboards are built 2. github.com/ccxt/ccxt — ccxt use: one interface for exchange data/trading APIs edge: cross-exchange data layer for bots 3. github.com/OpenBB-finance/Op… — OpenBB use: research terminal/data workflows edge: dashboard layer for market research 4. github.com/hummingbot/hummin… — Hummingbot use: market making / connector framework edge: market-making research stack 5. github.com/polakowo/vectorbt — vectorbt use: fast strategy research/backtesting in Python edge: test the idea before touching real capital 6. github.com/Polymarket/py-clo… — Polymarket py-clob-client use: CLOB orders, orderbook reads, bot execution plumbing edge: prediction-market execution layer 7. https://docs.polymarket.com/developers/CL… — Polymarket docs use: market data, CLOB concepts, API references edge: turn public market data into scanners the point is not to copy a bot. the point is to build a research loop: data → test → execute small → log every mistake. not financial advice.

@cardosofede you should confirm the hummingbot account on your bio. Leads go the wrong account.

I started a market making bot with Condor to test the @Backpack connector in Hummingbot. With only $1k in capital, it has generated $65 in P&L and filled 1.5% of total volume in the BP-USD pair. If you're starting with Hummingbot, I recommend Backpack given their low minimum order sizes and fees.

Hummingbot Condor 🚀🚀🚀

HummingbotでGRVTを動かすAIトレーディングボットの「完全ガイド」を公開しました😺 ・相関性の低い7アセットを監視するMALSS戦略 ・Docker＋Telegramでリモート操作できる実践的な構成 ・リスク管理（Triple Barrier）まで丁寧に解説 これからボットを作りたい人に超おすすめです！ note.com/noboru59631/n/n34f9… #Hummingbot #GRVT #AIトレーディング #自動売買 #MALSS

Hummingbot- GRVTで動くAIトレーディングボット完全ガイド｜noboru @noboru59631 note.com/noboru59631/n/n34f9…

Hell yeah! This Hummingbot EVEDEX integration is next level for the AI trading agents crew. Super clean setup too — API key, wallet connect, and you’re live with those advanced strats on perpetuals. Love seeing tools like this make self-custodial trading smoother and more powerful. Keep building fam, this is the future! LFG #DI88 #MARE88 #EVEDEX

😀 Jokes aside big fan of HummingBot. Go give them a try if you're into algo trading.

How Hummingbot Powers AI Trading Agents 🚀

Introducing Hummingbot Reporting, a new site that shows real-time trade volume generated across the crypto exchange landscape by running Hummingbot instances. Since Jan 2025, 105,000 unique instances have generated over $37 billion in trade volume. All data is aggregated and anonymized to prevent alpha leakage, and users can opt out of reporting. Check it out at reporting.hummingbot.org/

Cool, thanks for sharing! Just set up the EVEDEX perp connector on Hummingbot

거래 에이전트의 진짜 위험은 틀린 판단 자체보다, 그 판단이 그대로 주문으로 이어지는 구조에 있습니다. 크립토 거래소들은 AI 에이전트가 거래소 기능을 호출할 수 있는 인터페이스를 빠르게 내놓고 있습니다. Kraken은 AI- native CLI를, Binance는 Skills Hub를, Hyperliquid는 API wallet을, Hummingbot은 Condor라는 trading harness를 제시합니다. 하지만 공식 API나 wallet을 쓴다고 해서 안전 경계가 자동으로 생기는 것은 아닙니다. 에이전트가 잘못된 데이터를 보고 판단했을 때, 그 판단이 조회에서 멈추는지, 모의 거래에서 걸러지는지, 아니면 실제 주문까지 내려가는지를 따져봐야 합니다. [에이전트에게 거래소를 맡기기 전에]는 Kraken CLI, Binance Skills Hub, Hyperliquid API wallet, Hummingbot Condor를 4계층 × 5질문으로 비교합니다. 권한 절단, 어댑터 경계, 오래된 데이터 차단, 키 권한 범위, 재현 가능성을 기준으로 각 인터페이스가 어떤 부분을 막아주고, 어떤 부분을 사용자에게 남기는지 살펴봅니다. 에이전트에게 거래소를 맡기기 전에 어떤 경계를 확인해야 할지 아래 아티클에서 확인해보세요 👇 작성자 - 이민재(@abraxasnz13)

You can also do it with hummingbot, and not only codebase 50 cex and dex