{"postId":"opengov:335","kind":"opengov","title":"HDX Liquidity Provision on Kraken","body":"This proposal aims to improve liquidity for **HDX/USD** and **HDX/EUR** on Kraken.\n\nKraken is one of the most relevant fiat gateways for HDX. However, a listing only creates value if users can trade with reasonable size, low slippage and reliable order book depth. Better Kraken liquidity makes HDX more accessible to external traders and improves Hydration’s visibility outside the on-chain ecosystem.\n\nCEX liquidity also matters beyond Kraken itself. Platforms like CoinGecko and CoinMarketCap score markets based on liquidity, volume, spread, order book depth and related market-quality metrics. Stronger Kraken liquidity can therefore improve both the actual trading experience and how HDX markets are perceived externally.\n\n## Background\n\nI have been providing HDX liquidity on Kraken for more than **9 months**. Without this liquidity, the Kraken HDX markets would likely have much wider spreads, often in the **10–20% range** and only a tiny fraction of the current order book depth.\n\n![without_lp.png](https://subsquare.infura-ipfs.io/ipfs/QmaKkt79CMTcDQ133Zc2DGZz4XkXA1VUvq7bcF4xXHmGGe)\n\nMy current LP impact:\n\n![current_lp.png](https://subsquare.infura-ipfs.io/ipfs/QmNhnRAbbhvdruhYRozq3fSKnTiS7nZPLkGTxKauFWdiBU)\n\nThat said, there is still significant room for improvement.\n\nThe main limitation today is not only inventory size, but inventory size under the constraint that the operation still needs to be at least slightly profitable after costs, including Hydration trading fees. With only my own capital, liquidity has to be managed defensively. Spreads cannot be pushed as low and visible depth cannot be made as strong, as they could be in an internalized Treasury-backed setup.\n\nWith Treasury-provided inventory, the liquidity function would be internalized for Hydration. The operation would no longer need to target the same margin a purely external market maker would require. It also would not need to calculate Kraken quotes as if Hydration trading fees must be recovered through wider spreads. Fees and execution costs would still be tracked for accounting and risk management, but they would no longer be treated as a required profit hurdle.\n\nCurrent Kraken HDX market activity also shows the problem. Even after the latest HDX upmove, Kraken volume remained low and did not meaningfully recover alongside price. This suggests that Kraken is currently not functioning as a strong organic demand channel for HDX.\n\nLow CEX volume is not neutral. It weakens external visibility, can become a delisting risk factor over time and hurts the chances of organic new exchange listings. New exchanges usually want to see existing market demand, liquid order books and credible trading activity. A thin Kraken market sends the opposite signal.\n\n![chart.png](https://subsquare.infura-ipfs.io/ipfs/QmReEz8Pp5waRqQjfwcm8hFF5hurWvNUxm1oYzigYHpeZD)\n\nThis proposal aims to address that by letting the Treasury provide inventory while keeping full ownership of it.\n\n## Request\n\nI request Treasury-owned inventory for active Kraken liquidity provision:\n\n- **8,000,000 HDX**\n- **19,500 HOLLAR**\n- **19,500 USDC**\n\nThis inventory remains **property of the Hydration Treasury** at all times. It is not compensation, a grant, or a transfer of ownership.\n\nThe inventory will be actively used for market making, so balances may vary over time depending on fills, rebalancing and market conditions. Parts of this inventory will be converted to EUR/EURC. Governance may request the remaining inventory back at any time.\n\n## Operation Fee\n\nI request an operation fee of **1,200 HOLLAR per month**.\n\nThe initial test period would run for **3 months**, resulting in a total operation fee of **3,600 HOLLAR**.\n\n## Strategy\n\nThe strategy is to provide active liquidity on Kraken, especially within a **±2% band** around the current market price.\n\nThe focus is on:\n\n- improving HDX/USD and HDX/EUR order book depth\n- quoting close to the mid-price\n- reducing spreads and slippage\n- maximizing visible liquidity inside the target band\n- attracting more external trading volume\n\n**The strategy aims to quote at a minimal viable spread. Because this proposal internalizes the liquidity function for Hydration, the operation does not need to target the same profit margin as an external market maker. It also does not need to price Hydration trading fees into the Kraken spread as a required cost recovery component. This allows tighter spreads, deeper visible liquidity and a stronger focus on market quality.**\n\n## Technical Setup\n\nI have continuously upgraded my market making stack over time and further improvements are planned. Latest key improvements include:\n\n- **Reactive risk controls**: the system watches Hydration mempool and DCA activity. Relevant pending swaps are dry-run before inclusion to estimate price impact, allowing Kraken quotes to be amended or cancelled before adverse on-chain flow lands.\n- **Buffered hedge execution**: fills can be accumulated, netted and executed through a buffer instead of immediately hedging every fill separately. This reduces unnecessary Hydration trades and price impact to some degree.\n- **Mutable hedge transactions**: Hydration hedge transactions support same-nonce replacement, best-block tracking, finality handling and reorg recovery. Pending hedges can be updated while still in the mempool where safe, including changes in size or even a full side flip if later fills reverse the net hedge requirement before inclusion.\n- **Tip bidding for urgent execution**: configurable tip bidding can be used for urgent hedge execution when fast inclusion is needed.\n- **Liquidity-first ladder placement**: the order ladder prioritizes the lowest viable spread while maximizing visible liquidity inside the target band. Orders are sized against executable hedge capacity, not only nominal balances.\n- **More efficient Kraken order handling**: amend and batch operations are used where possible, reducing API churn and avoiding unnecessary cancel-replace cycles.\n- **Paired capacity checks**: Kraken orders are limited by both Kraken-side balances and available Hydration hedge capacity, including open-order locks, pending hedges, fee reserves, safety margins and rebalance reservations.\n- **Improved fill and hedge accounting**: Kraken private WebSocket fills are treated as authoritative. The system deduplicates fills, can backfill missed trades, ignores unrelated account fills and tracks hedge exposure through an explicit ledger.\n- **Inventory rebalancing and recovery**: HDX and quote (USD) inventory rebalancing uses explicit planning, source-fund reservation, deposit confirmation, background execution and recovery journals.\n- **Monitoring, security, operator tooling**: the stack includes dry-run mode, readiness checks, status commands, structured logs, heartbeat reporting, secret redaction, supply chain attack detection, lockfile verification and broader automated test coverage.\n\nThese upgrades are intended to make the operation safer, more reactive and more efficient while reducing the risk of funds getting stuck in failed or ambiguous states.\n\n## Test Period\n\nThis proposal is limited to an initial **3-month test**.\n\nAfter the test period, the results should be reviewed based on:\n\n- HDX/USD and HDX/EUR volume\n- average spread\n- order book depth\n- liquidity available within the ±2% band\n- inventory changes\n- operational issues and risks\n\nGovernance can then decide whether to continue, modify, expand, or stop the program.\n\n## Risks\n\nThe main risks are:\n\n- Kraken & 🦒 custody risk\n- market-making losses\n- inventory imbalance\n- adverse selection during volatile markets\n- API, infrastructure, or execution issues\n\nThe limited 3-month duration keeps this as a controlled experiment.\n\n## Requested Decision\n\nI ask governance to approve:\n\n1. **8,000,000 HDX**, **19,500 HOLLAR** and **19,500 USDC** as Treasury-owned Kraken liquidity inventory\n2. **3,600 HOLLAR** as operation fee for the initial 3-month test period","bodyFormat":"markdown","tldr":"","labels":[],"linked":[],"author":{"account":{"accountId":"0xb2927ffd2bbb0a73a317ab830e2dccd5e30cb0231c3ce7224be0f233b330742f","address":"15393VqXBSpxYDXALvGxbaeZoHwfDmh3jgG2t2iGK9vSAx7K","emoji":"🦒","tag":null,"identity":{"display":"Giraffe","verified":true,"email":"","web":"","twitter":"@1xGiraffe"},"profile":{"name":"Giraffe","avatarVersion":2}},"legacyName":null},"authority":"subsquare","revision":0,"createdAt":"2026-05-14T23:20:18.000Z","editedAt":null,"lastActivityAt":"2026-05-21T13:15:48.000Z","commentsCount":4,"updatesCount":0,"upvotes":0,"threadKey":"opengov:335","source":{"name":"subsquare","id":"6a0658d9781cee3ac47a650d","cid":null,"removed":false},"bannerCid":null,"banner":null,"poll":null,"locked":false,"media":{},"hidden":false,"generation":"6690c444c3e1fdf2"}