

Bitmaker
49 posts

@bitmakerfi
Web3 market maker | 6y exp | 50+ CEX/DEX | Exchange setup in 1 day | 24/7 ops, 99%+ uptime



Not many people know the story behind @origamitech_. This is the first post: where we came from. It all started 7 years ago, when my co-founder and I joined a centralized exchange trading desk. As recent graduates, we somehow ended up working on order book depth, market quality, accounting, and risk control around user actions. It was fun, but not a long chapter. After about a year, we decided to move on. We felt we understood where the edge was, and started running our own algos on centralized venues with our own capital. That was the real beginning of growth. I was writing code, he was helping across both technical work and management. In 2020, during DeFi summer, we became the top retail-volume account on @kucoincom - just two people doing billions in monthly volume on major venues. That same year, we launched @bitmakerfi, a retainer market maker built around one principle: stay small, but compete with anyone. We hired developers and started building out the business. For the first year, most of the engineering work was spent rewriting my original codebase to fit a new architecture. That became the first version of the protocol we internally called Typhoon. It was already better than what most retainer market makers had at the time, but it still wasn’t enough for us. It was too conventional: a handful of strategies, a set number of variables, a defined set of inputs. Strong, but limited. The model we kept coming back to was something closer to the WorldQuant external consultants idea: a unified framework where people can create their own algos, while the platform handles execution, connectivity, and data. In 2022, we redesigned the architecture from scratch and released our own language, which allowed us to build strategies directly from math, market data, and trading indicators. Latency improved, we found more edge, and the client base grew significantly over the following year. That period was productive. We released analytical tools, CEX-DEX systems, and arbitrage systems capable of handling up to 7 legs within one flow. In January 2024, I found @HyperliquidX and started trading there. Not because I particularly wanted futures, but because I liked the idea of a CLOB-based DEX. Soon after, I got in touch with Ruslan from @extendedapp - back when they were still early, still on testnet, and still called X10. I still think the rebrand was a great decision. Around that time, I also got @xulian_hl’s contact and texted him. He replied, and that became a turning point. I started thinking seriously about bringing our technology to users and connecting it to Hyperliquid. At that point there were no builder codes or anything similar, but within a month we had built the first interface. It was glitchy, API-key based, and full of bugs. I wasn’t proud of it, and we never released it publicly. That was around October–November 2024. After a few more months spent refining interfaces and fixing bugs, we finally launched Origami. At the time, I had postponed making perp DEXs the main focus, because the ecosystem still couldn’t support what we really wanted to build. For a while, API keys were the only realistic way to support trading. So we launched first with trading competitions - a format where users come to compete for prize pools funded by crypto projects. A month later, we launched liquidity mining competitions, giving projects a way to incentivize user liquidity provision. Since then, we’ve run more than 90 competitions and distributed over $200k in prize pools. A strong result - but still not the core dream. The bigger vision was always perp DEXs, and giving users the ability to create their own algos through Origami. By October, we had integrated with all existing builder programs. We didn’t build a massive user base there, and we understood the reasons clearly: > onboarding was too complex > UI/UX wasn’t good enough > strategy creation was still too difficult We tried simplifying things into lighter bot versions, but quickly understood that wasn’t our path. We know how to do this better. This huge interface update is the first step. The major things are on the line. If you read it, please leave a comment and thank you. Stay tuned.



















